Real, anonymous reports from people who interviewed for Software Engineer at Calsoft, newest first and distilled into what to expect across the loop.
I interviewed for Software Engineer in an overall easy-to-light track where the questions stayed close to role basics, including DSA/coding and a final non-technical discussion.
I interviewed for the Software Engineer role and found the process centered on frontend fundamentals over a short, multi-round loop.
Candidates typically face multiple technical rounds focusing on coding, data structures, and sometimes specific technologies like Java, Angular, or SQL. The difficulty can vary, with some candidates describing the rounds as manageable while others found them challenging, particularly around core concepts.
An initial online assessment often serves as the first gate, testing candidates on coding and sometimes multiple-choice questions. Performance on this assessment can significantly influence progression to subsequent rounds.
After technical evaluations, candidates typically engage in managerial and HR rounds that focus on fit, project discussions, and sometimes salary negotiations. The subjective nature of these rounds can impact the final decision.
Several candidates noted issues with communication and transparency throughout the interview process, including delays in feedback and unclear next steps, which negatively affected their experience.
Candidates reported varying outcomes, with many not receiving offers despite performing well in technical rounds. The selection criteria appeared to be influenced by both technical proficiency and subjective evaluations during managerial discussions.
Interviews often emphasized specific technologies relevant to the role, such as Java for backend positions or Angular for frontend roles, indicating a need for candidates to be well-versed in the technologies they will be working with.
