Real, anonymous reports from people who interviewed for Software Engineer at Bolt, newest first and distilled into what to expect across the loop.
After an HR chat that felt friendly, I moved into technical interviews and the vibe shifted fast. One interviewer asked me to explain the difference between HTTP and HTTPS, and it honestly felt like a very dated “gotcha” for a company at Bolt’s scale. The person I met in that round came across like a machine—no real engagement or emotion—just perfectly delivered answers to questions and not much back-and-forth.
The process started with an HR conversation about my background and then shifted into an online assessment that was supposed to reflect algorithmic design, but it didn’t really feel that way. I ran into two problems—one involving a REST API scenario for a medical-themed domain and another focused on databases. One of them ended up being much easier than expected, even hinging on something straightforward like a join.
The interview process typically begins with an HR conversation, followed by multiple technical rounds that can include coding, system design, and behavioral assessments. The overall timeline can stretch over several weeks, leading to a prolonged experience for candidates.
Candidates can expect a mix of live coding challenges and system design interviews, often focusing on web fundamentals, APIs, and algorithmic problems. The coding tasks may vary in complexity, requiring candidates to demonstrate both problem-solving skills and an understanding of system architecture.
Towards the end of the interview process, candidates typically engage in behavioral interviews that assess cultural fit and personal motivation. These rounds can vary in quality, with some interviewers being more engaging than others.
Candidates often report a lack of meaningful feedback after interviews, with many receiving generic rejection messages. This can lead to frustration and a sense of wasted effort, as candidates seek clarity on their performance.
The overall atmosphere of the interviews can feel performative, with some candidates noting a lack of genuine engagement from interviewers. This may affect how candidates perceive the evaluation process and their fit for the role.
Candidates should prepare for specific technical topics, including web security, HTTP methods, and algorithmic problem-solving. Familiarity with modern coding practices and tools may also be beneficial, as some interviewers prefer traditional coding methods.
