Real, anonymous reports from people who interviewed for Software Engineer at upstox, newest first and distilled into what to expect across the loop.
I had a pretty straightforward process that felt organized from the start. After the recruiter call, I got scheduled quickly and, about a week later, I joined a coding interview. The question was a LeetCode-style medium problem focused on graphs, specifically BFS, and the interviewer was genuinely kind and helpful when I got stuck.
My process for the Android SDE 2 role centered on fitment more than deep technical problem-solving. It was a single 30-minute fitment conversation where the discussion stayed on Android fundamentals and my background. The interviewer joined late, and we still did a formal introduction before getting into what ultimately mattered to them.
Candidates generally experienced a structured interview process that included multiple rounds, typically starting with a recruiter call, followed by technical interviews and an HR round. However, inconsistencies in the flow were noted, with some candidates facing unexpected rejections after progressing through several stages.
Technical rounds varied widely in focus, with some candidates facing coding challenges on algorithms and data structures, while others dealt with broader topics like architecture, system design, and specific technologies like React and Django. The difficulty level was often described as average, but experiences ranged from supportive interviewers to those who were disengaged.
Several candidates reported that discussions often centered on cultural fit and motivation rather than deep technical assessments, especially in initial rounds. This emphasis on alignment with company values was noted as a significant aspect of the interview experience.
Communication throughout the interview process was mixed, with some candidates receiving timely updates and constructive feedback, while others experienced delays and harsh interactions, particularly regarding rejections. The lack of clear communication led to frustration for some candidates.
Candidates described the overall difficulty of interviews as average, but expectations varied significantly, with some feeling unprepared for the types of questions asked, particularly if they deviated from their stated expertise. This inconsistency contributed to a sense of unfairness in evaluations.
Interviews covered a wide range of technical knowledge areas, including specific programming languages, data structures, algorithms, and software architecture principles. Candidates noted that questions sometimes reflected outdated knowledge or personal biases of interviewers, impacting the assessment process.