Ramboll software engineer interviews, as one candidate describes them, mix an intro conversation, OOP, SQL and Java fundamentals, a small database-and-API project, and an HR behavioral round.
$128K
Avg. Base Comp
$150K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
The clearest account of a Ramboll software engineer interview describes a fundamentals-first process rather than a puzzle-heavy one. The candidate reports that the interviewers opened by explaining how Ramboll's teams divide responsibilities and what the role involves day to day. They then asked for a walk-through of past work, with conversational follow-ups on previous roles.
The technical questions centered on object-oriented programming, SQL and Java. The candidate describes them as medium difficulty and says they tested clean understanding rather than exotic algorithms. Expect to explain inheritance, encapsulation and similar ideas with concrete examples from your own code.
The same candidate also reports a practical round where they built a small project with a database and APIs. If you are preparing, practice designing a simple schema, writing a few API endpoints and explaining your structure out loud. A behavioral round with the HR team followed, focused on team and culture fit, and the candidate was given time to ask questions at the end.
A separate report, for a student frontend developer role in Copenhagen, describes an hour-long conversational first round followed by a take-home coding task. That candidate was told the interview was cancelled after submitting because other applicants had more experience with the team's framework. If you are applying for a frontend or student role, check which framework the team uses and say plainly where you have gaps. Confirm the deadlines early. Both reports ended without an offer, and the evidence is thin, so treat the format as indicative rather than fixed.
Synthesized from 5 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 Ramboll process.
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 Ramboll
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Top Three Salaries | |
| Closest SAT Scores | |
| Merge Sorted Lists | |
| Employee Salaries | |
| Prime to N | |
| Largest Salary by Department | |
| Top 3 Users | |
| Rolling Bank Transactions | |
| Top 5 Turnover Risk | |
| Raining in Seattle | |
| Bagging vs Boosting | |
| Find the Missing Number | |
| Size of Joins | |
| Retailer Data Warehouse | |
| Over-Budget Projects | |
| Maximum Profit | |
| Find the First Non-Repeating Character in a String | |
| P-value to a Layman | |
| Hurdles In Data Projects | |
| First Touch Attribution | |
| Employee Project Budgets | |
| The Brackets Problem | |
| Minimum Change | |
| Real-Time Transaction Streaming | |
| Repeated Category Purchase | |
| Get Top N Frequent Words | |
| SELECTive Wine Connoisseur | |
| Google Maps Improvement | |
| Find Duplicate Numbers in a List |
Synthesized from candidate reports. Individual experiences may vary.
A candidate for the software engineer role reports that the interviewers introduced themselves first. They explained Ramboll's workflow and how teams split responsibilities, then described what the job involves day to day. You may then be asked to introduce yourself and discuss past roles.
The software engineer candidate reports being asked to walk through their work experience, with follow-up questions on previous roles and responsibilities. They described the tone as conversational rather than interrogatory, so prepare clear, specific examples of what you built and your part in it.
One software engineer candidate reports technical rounds centered on object-oriented programming concepts such as inheritance and encapsulation, plus SQL questions and Java problems. They describe the difficulty as medium and focused on basics and methodical thinking rather than trick algorithms.
The same candidate reports a practical round in which they built a small project involving a database and APIs. It likely rewards simple schema design, sensible API endpoints and clear code structure. Frontend candidates may instead be given a take-home coding task, as one student applicant reports.
The software engineer candidate reports a standard behavioral round with the HR team, aimed at gauging fit with the team and company culture. They were also given time to ask their own questions at the end, so it helps to have a few prepared.
