Real, anonymous reports from people who interviewed for Software Engineer at Kimley-Horn, newest first and distilled into what to expect across the loop.
Get your personalized Kimley-Horn Software Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
After I applied, I got a phone call screening within about a week, and then the technical interview happened the following week. Once the technical round was done, I was invited to a panel discussion.
The timeline felt straightforward at first, but the experience turned frustrating quickly. After the panel discussion, I was ghosted before I ultimately received anything like a decision. Eventually I did get an offer, but I ended up rejecting it.
> 1 year
Average Positive Dallas, TX
My interviews leaned heavily toward resume and fit, not problem-solving. The process started with a phone interview, and then I moved into another interview round where I met with a larger group of people. The overall format was multiple conversations with different team members, but the repeated theme was still “tell us who you are” rather than deep technical content.
Across those rounds, the questions stayed fairly generic: my resume, my involvement, and what industries I was most interested in. Even when there was time to talk engineering, it was framed through background and where I felt I’d best fit, not through technical scenarios. It felt like they were trying to gauge how I communicated and how my interests lined up with what the team was building.
> 1 year
Easy Negative Orange, CA
I went through three rounds: a phone call with HR, then virtual interviews with hiring managers, and finally an in-person interview. The scheduling an…
> 1 year
Average Neutral Texas City, TX
I joined a group-style video call on Zoom where the questions were mostly centered on my education and previous experience. They asked about my educat…
> 1 year
Average Positive Richmond, VA
My interview felt unusually lightweight. I didn’t go through a long gauntlet of technical screens—there were just straightforward conversations, and t…
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 includes a recruiter call followed by a technical interview and then a series of discussions with multiple team members, often structured in sections to assess fit and background rather than deep technical skills. Candidates noted that the organization and flow of the interviews contributed to a more relaxed atmosphere.
StructuredMultiple interviewersTeam fit
Focus on Background & Fit
Interviews heavily emphasize understanding candidates' backgrounds, experiences, and motivations, often through behavioral questions rather than technical grilling. This approach aims to gauge how well candidates align with the company's culture and values.
BehavioralCultural fitMotivations
Technical Assessment
While some interviews include a technical component, it is generally less intense than in other companies, focusing more on practical applications related to candidates' past experiences rather than complex problem-solving. Candidates reported a mix of technical and personal questions throughout the process.
Overall, candidates described the interview atmosphere as friendly and low-pressure, with interviewers showing genuine interest in their stories and experiences. This positive environment contributed to a sense of comfort during the process.
FriendlyLow-pressureComfortable
Communication & Follow-Through
Candidates experienced mixed communication regarding follow-up and outcomes, with some reporting delays or lack of responses after interviews. This inconsistency in communication left some feeling frustrated despite positive interview experiences.
Follow-throughCommunication issuesFrustration
Timeline & Scheduling
The interview timeline can vary, with some candidates experiencing quick responses while others faced long waits and scheduling challenges. This inconsistency affected overall candidate satisfaction and perception of the process.