Real, first-hand reports from data candidates. Filter by company and role, then read the full round-by-round breakdown.
I got into the loop through what felt like a pretty standard early-stage setup, and then things quickly turned into interviews that were mostly about fundamentals and how I thought out loud.
My interview journey for a Google SWE II (L3) style loop started with the Google Hiring Assessment.
I started with a Zoom interview, and then about a day or two later I was flown out for an in-person superday.
Recruiter-wise, this felt pretty smooth and fast.
My experience for lateral Software Engineer focused on a very clearly staged path.
I went through an experienced-hire Custom Software Engineer loop that felt very task-driven from the start.
After I finished the recruiter stage, I ended up doing an OA that felt very coding-heavy but with a clear split between a standard DSA prompt and a separate repository/debugging task.
My Amazon SDE Intern application moved into an online assessment fairly quickly, and it was paced like a timed coding gauntlet.
My process started with an online assessment for the Deloitte analyst track.
After a recruiter call, the process moved quickly into a multi-step format with technical depth.
I started with a quick first round that lasted about 20 minutes with an analyst.
My process started with an on-campus interview that felt tightly structured into three rounds.
I started with a recruiter reach-out that outlined the overall Apple SWE process and asked about my availability for the recruiter screening.
I applied for a Software Engineer Intern role on ServiceNow’s Developer Productivity team, and the whole virtual process stretched from around October to December 2024.
My process started with a phone interview, and then I had a second interview in person.
I applied and got sent an online assessment that centered on behavioral traits and two LeetCode-style coding questions.
After clearing the initial screening, I moved into an online assessment and then into an interview loop style setup.
My process started with an online assessment and then moved into a set of technical interviews that were both longer and more structured than I expected.
After I cleared the initial step, I ended up in several technical interview rounds where the questions pushed past basic implementations.
I started with applying and then got an OA.
My interview journey felt unusual mainly because it stretched my emotions more than the format itself.
I went through a Bar Raiser style round for an SDE-2 role at Kotak Mahindra Bank where the focus was very clearly on DSA and LLD.
My application moved into an OA that looked more like a work-sim and debugging challenge than a simple coding test.
My Tekion experience started with a very practical online test and then moved into a discussion of how my solution worked.
I went through the early scheduling and waiting parts more than the interviews themselves.
The most striking part of my Amazon SDE-1 process was how long I’d been trying before I finally got momentum.
I didn’t end up seeing much signal from my interview experience—I remember it being described as easy and frankly not something that was worth a lot of practice.
I applied cold for an Adobe Software Engineer Intern position and got pulled into a virtual loop scheduled for November 2024.
My first round was centered on JavaScript and React, and it felt very targeted from the start.
