After applying, I got an email with the details and then the process felt pretty streamlined. Before the interview, I was sent a study case, and when interview day came the people I spoke with were respectful throughout. The overall tone was pleasant, and I didn’t feel like there were any gotchas.
My interview flow was a simple two-step setup: a technical round and then a more personal round. For the technical part, I worked through a project-style question, and the coding portion was a very straightforward LeetCode-style problem. It felt easy enough that I could focus on communicating clearly instead of rushing. In the personal conversation, the aim felt more like fit than pressure.
3 months ago
Easy Positive San Jose, CA
I had a pretty low-stress, straightforward interview. The technical portion leaned heavily on basic PySpark and SQL syntax, and the rest of the time was a walkthrough of my resume and background. It didn’t feel like they were trying to grill me; it was more of a normal conversation.
The interviewers were friendly and the questions were basic. I remember feeling comfortable enough to think out loud without feeling put on the spot. The process didn’t drag or spiral into harder problem-solving, which made it easier to stay focused.
3 months ago
Average Negative Dallas, TX
Recruiter-wise, it started off great—I felt looked after and the recruiter felt genuinely awesome. But the actual interview experience turned sour fas…
4 months ago
Average Positive Philadelphia, PA
My process started with a quick outreach—first a short phone conversation where the recruiter reached out about a half-hour after I applied. After tha…
5 months ago
Difficult Negative Malvern, PA
After an initial HR call, my process shifted into a more intense stretch. I ended up with a long day of interviews that felt like it was running on mo…
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Interview Structure & Flow
The interview process typically consists of a recruiter screen followed by a technical round and a behavioral round, often structured as back-to-back sessions. Some candidates experienced variations like panel interviews or case studies, but the overall flow was generally organized and efficient.
Recruiter screenTechnical roundBehavioral round
Technical Assessment Focus
Candidates reported a mix of technical assessments, often including LeetCode-style coding problems, AWS fundamentals, and project-based questions. The emphasis was on practical engineering reasoning rather than obscure trivia, with some candidates feeling comfortable discussing their thought processes.
LeetCodeAWSPractical engineering
Behavioral Interviewing Style
Behavioral interviews were generally conversational and focused on fit, with many candidates using structured storytelling techniques like STAR. The tone was often friendly, with interviewers showing genuine interest in candidates' experiences and backgrounds.
STARConversationalFit assessment
Panel Interview Dynamics
Some candidates experienced panel interviews, which varied in effectiveness; while some felt supported, others reported disorganization or disengagement from interviewers, impacting their overall experience. The presence of multiple interviewers sometimes led to a lack of clarity in communication.
Panel interviewDisorganizationEngagement
Communication & Follow-Up
Candidates expressed mixed feelings about communication throughout the process, with some appreciating timely updates while others experienced delays or a lack of feedback post-interview. Ghosting or unclear follow-up left some candidates feeling frustrated.
CommunicationFeedbackGhosting
Overall Candidate Experience
The overall candidate experience was described as generally low-stress and respectful, with many candidates appreciating the supportive atmosphere. However, the lack of offers for several candidates led to reflections on the process, highlighting areas for improvement despite positive interactions.