Super.com Data Engineer Interview Questions
& Process

The interview process was pretty straightforward. It began with introductions and then moved into some medium-difficulty SQL questions. The interviewer seemed really impressed with my background and mentioned I should consider an offer from Super. Rankings day came, and I was only ranked for the position. A heads up, if you like a candidate, say so, but don't lead them on about an offer. Also, the talent acquisition team wasn't very responsive. I had an interview scheduled, but then got an interview for Super that conflicted. I let them know immediately, but never heard back, so I had to reschedule my other interview last minute.

This company's interview process execution was terrible. The recruitment team was awful, lacking initiative and a good sense of employee experience, and ghosting candidates was common. The process started with a confusing recruiter call, followed by a 45-minute interview with the hiring manager. The manager spoke for 20 minutes without a clear structure or interest in the candidate. Next was a live coding session with a junior team member. It started late, finished early, and the interviewer was rigid, not allowing alternative coding approaches even if they were more efficient. The coding questions were similar to easy/medium LeetCode problems but had ambiguous prompts. The interview was abruptly stopped because the code matched the script but the output didn't, despite the interviewer admitting the code was correct. It felt like the goal was to fail candidates rather than assess knowledge. Afterward, the recruiter ghosted me. It was a waste of time and energy.

really good experience, the interviewers are nice. coding assessment is not that hard, make sure there is enough communication between you and the interviewers. Other than that is mainly based on your experience and ask some question about your resume