
Sysdig Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 26 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Sysdig.
Software Engineer
This was a really weird interview. For a staff engineer, they expected me to know super specific details about tools like Redux state management. I feel like a staff engineer should be able to pick the right tool for the job, not necessarily know every single detail about every single one. What if someone prefers Jotai or something else?
- Can you explain what Redux is, and how you would update immutable state within it?
- What's the most significant feature you've released recently?
Software Engineer
It was a 4-step process: first a live coding session, then a system design and debugging round, followed by an architecture and distributed systems discussion, and finally a screening by a VP. What was good: the whole process was quick, with interviews spaced out one or two per week. The interviewers for the first two steps were open to giving feedback at the end, without any HR filtering. I'd rather get direct technical feedback than have an HR person relay it. What could have been better: the initial recruiter call was unpleasant; the person seemed disengaged despite reaching out to me. Another recruiter contacted me later and repeatedly asked about my visa status, even after I clarified I didn't need assistance. Steps 2 and 3 felt very similar, both involving system design problems with overlapping concepts. The interviewer for step 3 didn't provide feedback, unlike the others, which would have been helpful even if it was negative.
- A coding question that was a graph problem with domain specific context
Software Developer
I applied for a senior software developer role requiring C++ skills. There were five interviews in total. In each interview, the interviewer asked about my past experiences, and also posed technical and behavioral questions. Each round was about an hour long. All interviewers worked to make me feel at ease and shared company insights. It was a really positive experience. The whole process wrapped up in two weeks, and I got an offer the day after the final interview. The interview process really influenced my decision to accept the offer because, over those two weeks, I became convinced that the people at Sysdig are technically very strong, which is always good, and they form a really cohesive team. I'm confident I made the right choice.
- Could you describe how you would implement a semaphore in C++?
Sysdig Software Engineer Interview Questions
Quoted word for word from Sysdig interview reports.
“What's the difference between a Goroutine and an OS thread?”
Read reports →“Given a set of numbers where repetitions are allowed, how many pairs sum up to a target value?”
Read reports →“Solve a variation of the 2 sum problem.”
Read reports →“How would you find a specific substring within a very large binary file that cannot fit into memory and doesn't contain ASCII text?”
Read reports →“Explain the differences between fork, exec, and execv.”
Read report →“How do you generate random integers from 0 to n when your only tools are random 1s and 0s?”
Read report →“Write code to parse string data, sort it by specific fields, and then print the results.”
Read report →“What is the IP-based ACL algorithm and can you explain it?”
Read report →“Can you explain the difference between an abstract class and an interface?”
Read report →Formats, difficulty and experience
Across all 26 Sysdig interview reports.