My interview process felt like a scenario-heavy grind, and the structure kept pushing me to think through troubleshooting instead of just reciting knowledge. I went through multiple rounds that each felt “very good,” but the questions consistently came as realistic situations—scenario-based prompts, plus troubleshooting discussions.
At some point, I was specifically asked about working on the Google Cloud platform, and the conversations were centered on how I’d handle real-time issues and how I’d reason through what to fix and why. Even when the questions were framed as scenarios, the goal still felt like understanding my decision-making under uncertainty, not just getting to a single correct answer.
7 months ago
Average Positive Mumbai
My process moved through three clear rounds. After a call from HR where they scheduled things and aligned on basics, I got a technical screen where the conversation centered on backend and core problem-solving—data structures, algorithms, database concepts, and system design fundamentals. I ended up talking through past projects as well, especially the architectural decisions and what tradeoffs I’d made while solving real backend challenges.
The next step was HR-focused and leaned heavily into communication and fit. They asked about motivation for joining, long-term aspirations, strengths and areas to improve, and how I handled teamwork in a fast-paced environment.
7 months ago
Average Positive India
My journey followed a clean three-round structure. First came an HR briefing and screening to cover the basics and my background. Then I met a hiring …
11 months ago
Average Positive India
My process started through campus placements and it moved fast through several distinct formats. There was an online aptitude component as part of the…
> 1 year
Easy Positive Pune
My journey started with a fairly straightforward test that covered English and mental ability, and it set the tone for the rest of the process. After …
