Skip to contentSkip to footer

Staff Software Engineer Interview Questions

Salaries
Interviews

2,555 staff software engineer interview questions shared by candidates

First technical screen was a randomly selected Leetcode or Codility style problem done via zoom with Coderpad. Second technical screen followed the same format. (Yes, they test you twice.) They will describe these sessions as "collaborative" like everyone else but don't let that fool you: the collaboration part is just you thinking out loud, if you ever get stuck, points will likely be deducted. In other words: it's not actually "collaborative," but you didn't actually think it would be right? Second interview in my case was more conversational. I did ask about who the likely competitors were and what the positioning was. Third interview was also more conversational and we seemed to talk more about the interviewer, his reasons for joining, his role, etc. None of these conversational sessions seemed to be structured in any particular way so how they intend to score someone from these is a mystery. Fourth interview was the system design screen and we designed a system to process batches of transactions and then streams of transactions. Which is a lot to design in about 30-45 minutes if you include discussion. Because the last session was at the end of the day, we ended up chatting for at least 15m longer than the session. There was no indication (in my mind) that any of these sessions didn't go well; I interview a lot of candidates in my current job and I can tell when an interview just falls off the tracks. While I did solve both of the technical screens, during optimization of the second one I did start to get stuck with some of the Javascript syntax (I normally work in Go but find it easier to work in Javascript for tech screens). That's where this fake "collaboration" concept will get you.
avatar

Staff Software Engineer

Interviewed at Orum.io

3.2★
Sep 1, 2021

First technical screen was a randomly selected Leetcode or Codility style problem done via zoom with Coderpad. Second technical screen followed the same format. (Yes, they test you twice.) They will describe these sessions as "collaborative" like everyone else but don't let that fool you: the collaboration part is just you thinking out loud, if you ever get stuck, points will likely be deducted. In other words: it's not actually "collaborative," but you didn't actually think it would be right? Second interview in my case was more conversational. I did ask about who the likely competitors were and what the positioning was. Third interview was also more conversational and we seemed to talk more about the interviewer, his reasons for joining, his role, etc. None of these conversational sessions seemed to be structured in any particular way so how they intend to score someone from these is a mystery. Fourth interview was the system design screen and we designed a system to process batches of transactions and then streams of transactions. Which is a lot to design in about 30-45 minutes if you include discussion. Because the last session was at the end of the day, we ended up chatting for at least 15m longer than the session. There was no indication (in my mind) that any of these sessions didn't go well; I interview a lot of candidates in my current job and I can tell when an interview just falls off the tracks. While I did solve both of the technical screens, during optimization of the second one I did start to get stuck with some of the Javascript syntax (I normally work in Go but find it easier to work in Javascript for tech screens). That's where this fake "collaboration" concept will get you.

Project Manager round included my approach towards solving problems, the way I handle remote work, conflict resolutions. Engineering Leadership Interview was fun, went into the internals of my past projects, my mentorship skills, how I review PRs, how I keep myself updated with latest trends. There were few questions related to my tech stack expertise.
avatar

Staff Software Engineer

Interviewed at Service Management Group

3.5★
May 3, 2024

Project Manager round included my approach towards solving problems, the way I handle remote work, conflict resolutions. Engineering Leadership Interview was fun, went into the internals of my past projects, my mentorship skills, how I review PRs, how I keep myself updated with latest trends. There were few questions related to my tech stack expertise.

Viewing 1331 - 1340 interview questions

Glassdoor has 2,555 interview questions and reports from Staff software engineer interviews. Prepare for your interview. Get hired. Love your job.