Real, anonymous reports from people who interviewed for Software Engineer at Kiewit, newest first and distilled into what to expect across the loop.
I went through a longer, leader-heavy process for the Software Engineer role, feeling the difficulty was high and the timeline stretched to the very end.
I interviewed for the Software Engineer role with an average-to-easy difficulty overall, and the process felt more like structured fit-and-safety conversations than technical evaluation, typically unfolding over a few rounds.
The interview process typically begins with a recruiter or HR screening, focusing on basic background questions, motivations for applying, and logistical considerations like relocation. Candidates should prepare to clearly articulate their interest in Kiewit and their relevant experience.
Subsequent interviews often emphasize behavioral and fit questions, assessing how candidates align with Kiewit's culture and values, particularly around safety and teamwork. Candidates should be ready to discuss their past experiences and how they relate to the role.
While some candidates reported minimal technical depth, there may still be light technical discussions or basic programming questions. It's advisable to brush up on fundamental concepts and be prepared to discuss relevant technical experiences.
The interview process can involve multiple rounds, often including conversations with senior leadership or project managers, which may add to the overall length and complexity. Candidates should be prepared for a layered evaluation that values persistence.
Candidates may experience variability in communication and follow-up throughout the process, with some reporting delays or lack of clarity on next steps. It's important to proactively seek updates and clarify any uncertainties during the process.
Outcomes can vary significantly, with some candidates receiving offers while others do not, often influenced by factors like fit, communication, or practical constraints (e.g., relocation). Candidates should manage expectations and be prepared for potential non-offers.
