Real, anonymous reports from people who interviewed for Software Engineer at Giant Eagle, newest first and distilled into what to expect across the loop.
I went through a pretty straightforward process with three interviews total. First I spoke with HR, and then I had two more conversations with people from the hiring team. The questions stayed pretty basic—mostly getting a sense of my past experience and how I’d describe what I’d done before.
My process ended up being a small, clearly structured run of three rounds. I started with an interview focused on what I’d worked on with a team manager, basically to map my experience to the kind of work the role involved. After that, I ran into a coding round, which was a more hands-on check than the earlier conversation. The final step leaned into behavioral questions, including how I thought about expectations and hypothetical scenarios.
The interview process typically consists of 2-3 rounds, starting with HR and followed by technical and behavioral interviews, focusing on candidate experience and fit rather than deep technical challenges.
Candidates can expect a coding or technical discussion that assesses practical skills, though the difficulty is generally moderate and not overly complex, aimed at understanding real project work.
Behavioral interviews often include situational questions to gauge how candidates handle hypothetical scenarios, with a focus on interpersonal skills and alignment with company values.
Candidates have reported mixed experiences with communication; while some found the process clear and timely, others experienced delays and a lack of follow-up after interviews.
The interview atmosphere is generally friendly and low-pressure, but some candidates noted instances of unprofessionalism or a lack of engagement from interviewers, affecting their overall impression.
Many candidates did not receive offers, and feedback on the outcome was often unclear or delayed, leading to frustration and uncertainty about their standing in the process.
