Real, anonymous reports from people who interviewed for Software Engineer at Smart Consulting, newest first and distilled into what to expect across the loop.
I started with an HR conversation that felt pretty easygoing. They talked through what the role actually was, and we covered my background in a fairly introductory way—things like the technologies I’d worked with, my motivation, and what I expected from the process. The recruiter also explained the offer details early, and the overall vibe was relaxed and professional rather than intense.
I went through a developer interview that focused heavily on practical evaluation. They reviewed my CV, then moved into technical questions and a problem-solving portion with theoretical elements. I also got assessed on how I handle debugging and bugs, and we discussed my past experience and how I’d approached earlier projects.
The interview process typically begins with a relaxed HR conversation focused on the candidate's background, motivations, and basic role expectations, creating a comfortable atmosphere for discussion.
Candidates can expect a technical interview that varies based on client needs, often including practical evaluations and problem-solving elements, with an emphasis on communication and collaboration skills.
Throughout the process, candidates noted a lack of feedback and clarity regarding their performance and next steps, leading to feelings of uncertainty and frustration.
Interviews often prioritize assessing fit for the company culture and internal needs rather than deep technical evaluations, which may leave candidates feeling like they are part of a workflow rather than a genuine assessment.
Candidates frequently reported outcomes that did not result in job offers, with decisions feeling more procedural than personal, contributing to a sense of dissatisfaction with the overall experience.