Confidential Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 6 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Confidential.
Confidential
Product Engineer
Entry Average Positive experience Decline offer 4 rounds
Interview process
Recruiter call Technical screen Onsite Background check Offer
Interview formats
Technical Case Behavioral
The interview process was pretty structured and went smoothly. First, there was a recruiter screening, then a technical round where they asked about SQL, product metrics, and data case studies. After that, I had a product thinking round with questions about user behavior and feature adoption scenarios. The last round was behavioral questions and talking with the hiring manager about working with other teams. It was engaging and gave me a good feel for the job.
Confirmed questions5 questions
- If you were to launch a feature like "Dark Mode," what product metric would you prioritize tracking?
- Can you explain how to calculate 7-day retention using SQL?
- What scenario-based questions about user behavior and feature adoption were asked in the product thinking round?
Confidential
Engineer
Entry Average Positive experience No offer 4 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite
Interview formats
Coding Behavioral System Design Technical
good interview, some coding questions, some behavioral questions, overall good process, i would interview there again, it was a pleasant experience. Coding questions were focused on a variety of things, there was some system design, some data science/algo stuff, and then a mix of other leetcode style questions.
Confirmed questions1 question
- Given an array of integers nums and an integer target, return the indices of the two numbers such that they add up to target. You may assume that each input would have exactly one solution, and you may not use the same element twice. You can return the answer in any order. Input: nums = [2, 7, 11, 15], target = 9 Output: [0, 1] Explanation: Because nums[0] + nums[1] == 9, we return [0, 1].
Confidential
Engineer
Entry Average Neutral experience No offer 3 rounds
Interview process
Recruiter call Technical screen Background check Offer
Interview formats
Coding Technical Behavioral
first round is screening, then a technical discussion where you do coding and review code, and then a discussion with HR. If you pass the HR discussion, they will call you with an offer. The technical discussion involves development coding, and once you write the code you have to explain it and do a code review with examples.
Confirmed questions2 questions
- Do you have any experience with development coding?
- Do you have any experience with testing?
Confidential Engineer Interview Questions
Quoted word for word from Confidential interview reports.
“Given an array of integers nums and an integer target, return the indices of the two numbers such that they add up to target. You may assume that each input would have exactly one solution, and you may not use the same element twice. You can return the answer in any order. Input: nums = [2, 7, 11, 15], target = 9 Output: [0, 1] Explanation: Because nums[0] + nums[1] == 9, we return [0, 1].”
Read reports →“Can you explain how to calculate 7-day retention using SQL?”
Read reports →“If you were to launch a feature like "Dark Mode," what product metric would you prioritize tracking?”
Read reports →“What are your plans for the next few years?”
Read reports →“Would you be willing to put in extra hours when required?”
Read report →“What scenario-based questions about user behavior and feature adoption were asked in the product thinking round?”
Read report →“Do you have any experience with development coding?”
Read report →“What behavioral questions were asked?”
Read report →“Do you have any experience with testing?”
Read report →Formats, difficulty and experience
Across all 6 Confidential interview reports.