Aecom software engineer candidates report an HR screen and conversational interviews that may include a LeetCode Easy problem, SQL questions, and discussion of background, motivation, and travel.
$113K
Avg. Base Comp
$125K
Avg. Total Comp
2-3 rounds
Typical Rounds
Not reported
Process Length
The software-specific reports for Aecom are few, and many other Aecom interview reports come from civil, structural or mechanical roles, so treat this as a modest picture. The most detailed software engineer account describes three rounds: an HR screen about salary expectations and career goals, then technical conversations built around a LeetCode Easy problem and basic SQL questions. That candidate said the interviewers cared about reasoning more than obscure edge cases, and they also asked about willingness to travel for projects.
A second candidate, interviewing for a software engineer role, described a face-to-face conversation of about twenty to thirty minutes. It covered why they wanted this stream of work, technical knowledge, details from their cover letter, salary expectations and career direction. They said the questions were not algorithmic, found the process somewhat disorganized, and wished they had brought more concrete project examples.
In practice, prepare to solve an easy coding problem aloud, refresh SQL fundamentals, and have two or three project stories ready that tie to anything you wrote in your application. Be ready to say clearly why Aecom and why this kind of work. Responsiveness varied between the two reports, so following up politely after interviews is reasonable.
Synthesized from 11 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Aecom process.
I interviewed at Aecom for a Software Engineer role in late 2024, and the process felt somewhat disorganized from start to finish. The hiring team wasn't particularly responsive between rounds, which made it hard to know what to expect next. When I finally got to the face-to-face interview, it lasted around twenty to thirty minutes and covered a mix of technical and situational questions. They asked me why I was interested in the role and this particular stream of work, then dug into my technical knowledge and the details I'd included in my cover letter. The conversation also touched on my salary expectations and where I saw my career heading in the next few years. The questions themselves were fairly straightforward — nothing overly complex or algorithmic — but they clearly wanted to understand both my technical foundation and my motivation for joining. I got the sense they were assessing whether I could articulate my knowledge clearly and think through practical applications, rather than testing me on coding or advanced problem-solving under time pressure. The overall vibe was professional but a bit rushed, and I didn't feel like I had much opportunity to ask clarifying questions or really showcase my problem-solving process with detailed examples. In the end, I didn't receive an offer, which was disappointing given how the conversation had felt in the moment. Looking back, I wish I'd prepared more concrete examples from past projects to demonstrate my experience more compellingly.
Prep tip from this candidate
Be ready to provide detailed, structured examples from your past work that connect directly to the technical knowledge you claim in your cover letter. The interviewers will ask follow-up questions based on what you've written, so make sure you can back it up with specific scenarios and outcomes.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Aecom
How would you as a consultant develop a strategy for a client's mission of building an affordable, self-sustaining kindergartens in a rural Turkish town?
| Question | |
|---|---|
| Statistically Significant Test | |
| Top Three Salaries | |
| 2nd Highest Salary | |
| Merge Sorted Lists | |
| Largest Salary by Department | |
| Top 5 Turnover Risk | |
| Prime to N | |
| Raining in Seattle | |
| Rolling Bank Transactions | |
| Bagging vs Boosting | |
| Top 3 Users | |
| Find the Missing Number | |
| The Brackets Problem | |
| Retailer Data Warehouse | |
| Find the First Non-Repeating Character in a String | |
| Size of Joins | |
| Hurdles In Data Projects | |
| Manager Team Sizes | |
| P-value to a Layman | |
| New Resumes | |
| Google Maps Improvement | |
| Paired Products | |
| Find Duplicate Numbers in a List | |
| Target Indices | |
| Resumable Fact Table Load | |
| Cyclic Detection | |
| Transformer Encoder Layer | |
| Sort Strings | |
| Binary Tree Conversion |
Synthesized from candidate reports. Individual experiences may vary.
One software candidate reports an initial HR conversation about salary expectations and what they wanted in their next role, and described the interviewer as friendly and approachable. Expect to state a salary range and explain your motivation for Aecom.
One software engineer candidate reports a LeetCode Easy problem plus a few SQL questions, with interviewers focused on reasoning rather than edge cases. Another software candidate described no algorithmic questions, so technical depth may vary by team and level. Practice explaining your approach aloud.
Candidates report discussion of past roles, studies and details from a cover letter, along with why they want this work and where they see their career going. One report mentions a face-to-face interview of roughly twenty to thirty minutes. Concrete examples of your own work appear to matter.
Reported communication differed. One software candidate describes clear, timely updates throughout, while another found the hiring team unresponsive between rounds. Following up politely on timing is sensible.
