Real, anonymous reports from people who interviewed for Software Engineer at UST, newest first and distilled into what to expect across the loop.
I went through a mostly straightforward, recruiter-led sequence with light-to-moderate coding and resume-based discussion over about a day or two.
I had an assessment-heavy path with coding/aptitude filters first, and then short technical or debate-style rounds where expectations about approach mattered.
The interview process typically begins with a recruiter-led phone conversation that covers your background and may lack detailed information about the role or client. This step is informal and serves as a preliminary filter.
Candidates often undergo aptitude tests and coding assessments early in the process, which serve as a gate before moving to technical discussions. These tests can include basic problem-solving and communication evaluations.
Technical rounds generally focus on foundational coding skills, data structures, and algorithms, with some candidates facing deeper scenario-based questions, particularly around databases and specific programming languages like Python and Java.
Many interviews include a deep dive into candidates' projects, where they are expected to explain their work and the technologies used, often followed by technical questions related to their projects.
Final rounds often consist of HR discussions that assess fit, communication skills, and career aspirations, sometimes combined with behavioral questions. Candidates should be prepared to discuss compensation and role expectations.
Candidates report a range of experiences from average to difficult, with many not receiving offers despite feeling they performed well. The variability in interview styles and expectations can impact outcomes significantly.