Went quite well. They ended up extending an offer to me. I felt the interview questions and experience was balanced and fair. But I ended up rejecting it, as benefits from another company was a lot better. Would consider again in the future.
very friendly interview process, was difficult to grasp the problem at first but once you see the pattern it becomes more and more straightforward. they are very supportive throughout it.
I applied online. I interviewed at Stealth Startup (San Francisco, CA) in May 2026
Interview
The process was clear, practical, and well-structured. I appreciated that it focused less on trivia or LeetCode-style questions and more on how I think through real engineering problems.
The pre-work was short and useful for getting into the right context. The work sample felt representative of actual platform engineering work: reading existing code, making tradeoffs, improving reliability, and communicating decisions clearly. The final Slack interview was also a strong format because it tested written communication, async collaboration, product judgment, and technical reasoning without unnecessary pressure.
Overall, the process gave me a good sense of the team’s engineering culture: pragmatic, systems-oriented, and focused on real-world judgment. It felt respectful of candidates’ time while still being deep enough to evaluate senior-level engineering ability.
My only small suggestion would be to share a little more upfront about what “good” looks like in the work sample, not in terms of exact solution, but in terms of whether the team values completeness, tradeoff discussion, operational thinking, or code polish most.
Overall, very positive experience. The process made the company more attractive to me.
Interview questions [1]
Question 1
“One question that stuck with me was essentially: *‘How do you make good engineering decisions when there isn’t a clearly correct answer?’*
A lot of the interview revolved around tradeoffs — reliability vs complexity, operational burden vs flexibility, shipping speed vs long-term maintainability. It felt much more like discussing real production systems with teammates than trying to pass a test.”