Cedar Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 14 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Cedar.
Cedar
Software Engineer
Staff Difficult Positive experience No offer 5 rounds
Interview process
Recruiter call Technical screen Phone screen Onsite Background check
Interview formats
Behavioral Technical Coding
I had a 15-minute call with a recruiter, then a 90-minute live coding interview, followed by a 45-minute chat with the hiring manager. The virtual onsite was 6 hours over two days. There was supposed to be one more 30-minute call with engineering leadership. I was really impressed with how the whole process went. Everyone was super transparent and professional. They prepped me really well for each interview, telling me exactly what to expect and giving me a heads up on the topic and what they'd ask. It was a bummer they didn't move forward after I felt so good about it and got so far.
Confirmed questions1 question
- Can you provide a detailed example of a project you led from 0 to 1 or helped scale from 1 to N that had a significant organizational impact?
Cedar
Software Engineer
Senior Average Negative experience No offer 3 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Technical Behavioral
Recruiter reached out, I applied for SDE3 and a technical assessment. Then they switched me to an SDE2 role on a different team for the hiring manager round, no explanation given. The HM told me about the final round format, and then another recruiter rejected me a few days later. It was a really disorganized process overall.
Confirmed questions1 question
- How would you calculate metrics using OOP principles within a billing process?
Cedar
Software Engineer
Mid Average Neutral experience No offer 2 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Technical Coding
A recruiter contacted me on Hired. We had a screening call where we discussed my background and the role. Then, I had a one-hour technical interview with a live CoderPad session. It was conducted by a DevOps engineer not on the team I applied to, which was a bit strange, but another software engineer from the team was there to answer specific questions about the role. The CoderPad problem was LeetCode 121, Best Time to Buy and Sell Stock, with some modifications during the interview. I finished all but the last modification. I got another offer and withdrew before hearing back, but the process was supposed to continue with a 4.5-hour virtual on-site.
Confirmed questions1 question
- How would you create an algorithm to determine the optimal time to buy and sell a stock, referencing LeetCode 121?
Cedar Software Engineer Interview Questions
Quoted word for word from Cedar interview reports.
“What is the optimal method for informing patients about their bills?”
Read reports →“Given a healthcare billing company with datasets for patient bills, patient payments, and notification methods (email, text, phone call), how would you create a Python function to identify the most effective notification method?”
Read reports →“How would you create an algorithm to determine the optimal time to buy and sell a stock, referencing LeetCode 121?”
Read reports →“Given some input data that needs processing, please provide the results.”
Read reports →“How would you calculate metrics using OOP principles within a billing process?”
Read report →“Could you define some success criteria and calculate them?”
Read report →“How would you design a simple web application?”
Read report →“What technical and cultural fit questions were asked?”
Read report →“Can you provide a detailed example of a project you led from 0 to 1 or helped scale from 1 to N that had a significant organizational impact?”
Read report →Formats, difficulty and experience
Across all 14 Cedar interview reports.