Coda logo

Coda Software Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 15 interview experiences · FREE TO READ

3.5 Rounds average
Average Typical difficulty
66.7% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Coda.

Showing 3 of 15
Coda logo
Coda

Software Engineer

Engineering · a year ago

Senior Easy Negative experience No offer 2 rounds
Interview process
Recruiter call Technical screen
Interview formats
Technical Coding

Overall, Coda Payments left me questioning their culture and hiring. They might have interesting jobs, but the lack of transparency, unprepared interviewers, and exclusionary process make it hard to recommend. Candidates should research well before talking to them. The salary ranges were low compared to the market. There was a lack of transparency about the role and expectations. Interviewers seemed unprepared and disengaged. It was unusual that the process only involved engineering managers, potentially showing a lack of trust between managers and ICs, raising concerns about gatekeeping. The managers were defensive and narrowly focused on their internal view, making it hard to discuss business problems broadly. They seemed disinterested in learning about candidates and dismissive. They kept asserting the company's merits instead of talking. My interactions and external reviews suggest potential internal issues, management problems, politics, and lack of inclusivity. Red flags: seemed like they were gathering market data via compensation questions, and the recruitment team seemed to prioritize image over candidate experience. Avoid this company, better jobs exist.

Confirmed questions2 questions
  • Can you describe how you would implement a load balancer using Java?
  • For a LeetCode easy algorithm, can you use pseudo-code and discuss complexity and potential improvements?
Coda logo
Coda

Technical Lead

Engineering · a year ago

Lead Average Positive experience Accept offer 3 rounds
Interview process
Recruiter call Take home Technical screen Offer
Interview formats
Coding Technical

First, a recruiter reached out. Then, I received a take-home assignment, which was a coding exercise in Java. I had to submit it via GitHub within 7 days. After that, there was an interview split into two parts. The first part involved discussing my submitted solution and answering follow-up questions. The second part focused on technical questions, primarily related to Java, including topics like memory management, concurrency, and data structures such as HashMap and Set. Finally, I received an offer.

Confirmed questions1 question
  • Can you explain the workings of Java's garbage collector?
Coda logo
Coda

Senior Staff Software Engineer

Engineering

Staff Average Negative experience Decline offer 5 rounds
Interview process
Recruiter call Technical screen Take home Onsite Background check Offer
Interview formats
Behavioral Technical Coding

The interview process started with an HR call to discuss expectations and the role. This was followed by a round with two developers, and then a meeting with the Product Manager. After these initial stages, a take-home test was assigned, and subsequently, a discussion about the solution to the take-home test was held with the team. Following these steps, the company requested three references for feedback. The entire process spanned four weeks, culminating in a final discussion regarding an offer. During the HR discussion, the offer presented was significantly below expectations and even lower than my current compensation, which felt disrespectful, insulting, and unprofessional. Furthermore, the role offered was 'Software Developer,' not the 'Senior Software Developer' position I applied for. Instead of rejecting candidates who don't meet the mark, undervaluing them and offering a junior position is inappropriate. Individuals should not be undervalued as it can impact their confidence. The HR department lacked the courtesy to reply to emails. Even the CTO reached out, mentioning he heard an offer was forthcoming from Coda and inquired about my needs. Despite informing him of the situation, he never responded. While I understand he might be busy, contacting candidates before an offer is accepted in such circumstances is not ideal. The technical team and Product Manager were excellent, and I appreciate them for showing me the company's true culture beforehand.

Confirmed questions4 questions
  • Could you discuss concepts related to High availability?
  • Can you explain your understanding of Scalability?
  • What are your thoughts on threading?

Coda Software Engineer Interview Questions

Quoted word for word from Coda interview reports.

What is the product of every other integer in a given array?

Read reports

What are your recommendations for network security on Android?

Read report

Can you explain the workings of Java's garbage collector?

Read report

How would you design a parking garage, starting with a single parking lot?

Read report

Can you design a round robin application that also includes an echo server?

Read report

Formats, difficulty and experience

Across all 15 Coda interview reports.

Interview formats

Coding 40%
Technical 37.5%
Behavioral 12.5%
Presentation 5%
Other 2.5%

Interview difficulty

Easy 26.7%
Average 73.3%
Difficult 0%

Candidate experience

Negative 26.7%
Positive 66.7%
Neutral 6.7%