HDR · Software Engineer
Updated · 2026-10-02

HDR Software Engineer
Interview Guide

THE 60-SECOND BRIEF

As a Software Engineer at HDR, you play a critical role in bridging physical infrastructure and digital innovation. HDR is an employee-owned architecture, engineering, and consulting firm that delivers complex, large-scale civil, environmental, and structural projects globally. Software engineers inside this engineering-centric environment build domain-specific software tools, internal project automation platforms, spatial data processing pipelines, and data integration platforms that power multi-disciplinary engineering projects. Your work directly impacts project delivery speed, structural modeling accuracy, and cross-team collaboration across disciplines ranging from transportation and water systems to data centers and urban planning.

This guide is scoped to a Software Engineer candidate at HDR.

HDR candidates report 4 rounds over 3-5 weeks. The stages below are what candidates describe, not a published process.

CFD (Computational Fluid Dynamics)ANSYS FluentThermofluids

22 min read

Browse Software Engineer questions

See the practice prompts

20Practice promptsAcross five skill areas

As a Software Engineer at HDR, you play a critical role in bridging physical infrastructure and digital innovation. HDR is an employee-owned architecture, engineering, and consulting firm that delivers complex, large-scale civil, environmental, and structural projects globally. Software engineers inside this engineering-centric environment build domain-specific software tools, internal project automation platforms, spatial data processing pipelines, and data integration platforms that power multi-disciplinary engineering projects. Your work directly impacts project delivery speed, structural modeling accuracy, and cross-team collaboration across disciplines ranging from transportation and water systems to data centers and urban planning. Engineers at HDR depend on internal applications to process complex spatial datasets, automate drafting and modeling workflows, and integrate third-party engineering systems. Building reliable, maintainable software within this domain requires balancing solid computational foundations with a practical understanding of how real-world engineering workflows operate. Candidates applying for software engineering roles at HDR should expect an environment where technical skills are evaluated alongside communication ability, team collaboration, and real-world problem-solving.

01

Online Application

reported

Submit your application online to express interest in the Software Engineer position.

What to demonstrate

  • Submit your application online to express interest in the Software Engineer position
  • Depth in CFD (Computational Fluid Dynamics)

How to prepare

  • Answer aloud and timed: Walk us through a complex project on your resume from start to finish.
  • Answer aloud and timed: Describe a technical challenge you encountered in a past project and how you resolved it.
HDR Software Engineer candidate reports ↗
02

Initial Screening Call

reported

A call with a recruiter or department manager to confirm basic details and logistics.

What to demonstrate

  • A call with a recruiter or department manager to confirm basic details and logistics
  • Depth in CFD (Computational Fluid Dynamics)

How to prepare

  • Be able to walk your CV end to end in two minutes, and say why this company specifically.
  • Have your salary expectations, notice period and location constraints ready, and ask for the rest of the loop in writing.
HDR Software Engineer candidate reports ↗
03

Panel Interview

reported

A virtual or in-person interview with a panel of 2 to 4 team members discussing your resume and past projects.

What to demonstrate

  • A virtual or in-person interview with a panel of 2 to 4 team members discussing your resume and past projects
  • Depth in CFD (Computational Fluid Dynamics)

How to prepare

  • Answer aloud and timed: How have you applied your academic coursework or specialized technical training to practical engineering problems?
  • Answer aloud and timed: How do you approach structuring code or scripts to automate repetitive engineering or data processing tasks?
HDR Software Engineer candidate reports ↗
04

Office Visit

reported

An invitation to visit the local HDR office, tour the space, and meet potential teammates.

What to demonstrate

  • An invitation to visit the local HDR office, tour the space, and meet potential teammates
  • Depth in CFD (Computational Fluid Dynamics)

How to prepare

  • Answer aloud and timed: What experience do you have working with CAD tools, spatial data, or domain-specific computational software?
  • Answer aloud and timed: How do you ensure code quality, accuracy, and maintainability when building software used by cross-disciplinary teams?
HDR Software Engineer candidate reports ↗

PracHub editorial advice for the preparation topics above.

01

Highlight Practical Deliverables

Focus your answers on tangible outcomes. Explain what software tools you built, how they were used, and the measurable impact they had on project performance or efficiency.

02

Prepare Questions for the Panel

Show active interest in HDR's project portfolio. Ask interviewers about current internal software initiatives, team structures, and how technology adoption is managed within their specific office.

03

Dress Professionally for Interviews

Even for informal or virtual panel sessions, dressing in professional business attire sets a positive, respectful tone that aligns well with HDR’s corporate environment.

Choose a category, try a prompt, then open its approach, worked solution or follow-up when you need it.

14 technical prompts0 include a worked solution

Archive a resource graph without breaking live references or recursing

medium
graph traversaltopological ordertenant isolation

Resources reference other resources within a tenant; for the largest tenant the reference table holds up to 2,000,000 nodes and 8,000,000 edges. Archiving a resource must archive everything reachable from it that nothing outside the set still references, refuse when a live external referrer exists, and terminate when references form cycles, which they legitimately do. Produce the archive order and the refusal list, targeting O(V+E). Say what stops the traversal crossing a tenant boundary, and why recursion is the wrong control structure at this size.

Approach
  1. Load the subgraph with the tenant predicate on both endpoints of the edge, not only on the side you started from. Scoping the left table alone is the classic cross-tenant leak: one mis-entered edge then pulls another tenant's resources into the traversal and, worse, into the archive.
  2. Traverse iteratively with an explicit stack. A 2,000,000-node graph can hold a chain deep enough to exhaust a native stack in the low tens of thousands of frames, and that failure is a process crash rather than an error you can return.
  3. Treat cycles as data rather than corruption: compute strongly connected components with Tarjan in O(V+E) using its own explicit stack, then condense. The condensation is a DAG, so a topological order over it gives the archive order, and every member of a component archives in one transaction because no order within a cycle is valid.
  4. Decide refusals with reverse edges. A candidate is archivable only if every in-edge originates inside the candidate set, so build the transpose or count in-degrees restricted to the visited set, and emit each blocked resource with the id of the external referrer, which is the only part of the answer an operator can act on.
Follow-up
  • The graph is read in one query and the archive writes a minute later. What can change in between, and how do you make the write safe?
  • The candidate set is 400,000 resources. Is that one transaction, and if not, what does a half-finished archive look like to a reader?

Merge partitioned event streams into one ordered feed with bounded lateness

hard
k-way mergewatermarksout-of-order streams

The read-model service consumes 64 log partitions carrying about 4,000 events per second in total. Each partition is ordered within itself, but partitions drift by up to 30 seconds, and the activity feed must present a tenant's events in occurred_at order. Produce the merge. State its complexity, the buffer it requires in events and in bytes, what happens when one partition is idle, and what you do with an event that arrives after you have already emitted its position. Payloads average 1 KB.

Approach
  1. Merge with a min-heap over the 64 partition heads keyed on (occurred_at, event_id): O(log P) per event and O(n log P) overall. The tie-break on event_id is what makes the output deterministic when two partitions carry the same millisecond, which matters because the feed is paginated and a non-deterministic order reorders pages under the reader.
  2. Emitting the heap head is only correct once every partition has produced everything up to that timestamp, so the emit condition is a watermark: the minimum across partitions of the highest occurred_at seen, less the allowed lateness. Events are held until the watermark passes them, which is what turns individually ordered streams into a jointly ordered one.
  3. Size the buffer from the lateness rather than guessing: 4,000 events per second times 30 seconds is 120,000 buffered events, and at 1 KB each about 120 MB of heap. That number is the real price of the ordering guarantee and belongs in front of whoever asked for it.
  4. Handle the idle partition explicitly, because it fails the feed rather than corrupting it: a partition with no traffic never advances its own maximum, so the watermark freezes and output stops entirely. Either every partition emits a periodic idle marker carrying the broker's current time, or the watermark falls back to wall clock for a partition silent beyond a threshold.
Follow-up
  • The lateness budget is raised to five minutes. What is the new buffer, and what besides memory changes?
  • The consumer restarts. Where does it resume from, and what does the feed look like for the first 30 seconds?

Find overlapping job attempts and peak concurrency from lease records

medium
sweep lineintervalsleases

A day of job_run history yields about 50,000,000 attempt records: (job_run_id, job_type, attempt, started_at, finished_at which is NULL when the worker died, lease_expires_at). Leases expire on a clock, so a job that outran its lease ran twice. Produce (a) every job_run_id whose attempts overlapped in wall-clock time and (b) the peak number of simultaneously running attempts per job_type with the minute it occurred. Target O(n log n). State how you treat a NULL finished_at and what clock skew does to your answer.

Approach
  1. Define the interval before sorting anything: an attempt occupies [started_at, COALESCE(finished_at, lease_expires_at)). finished_at is observed and lease_expires_at is only a promise, so every attempt without a finish contributes an estimate and the whole result is a lower bound on overlap rather than an exact count.
  2. For peak concurrency, sweep: emit 2n endpoints, sort by (timestamp, kind) with ends ordered before starts at equal timestamps, then walk the sequence maintaining a counter per job_type and record each type's maximum with its timestamp. O(n log n) dominated by the sort, O(n) space, or O(1) extra if the sort is external and the walk streams.
  3. For overlap detection, do not compare attempts pairwise. A single global sort by (job_run_id, started_at) gives both the grouping and the order; within a group, keep the maximum end seen so far and report an overlap exactly when the next start is less than that running maximum, which is one linear pass after the sort.
  4. Half-open intervals matter and are easy to get wrong: with closed intervals an attempt ending at the same millisecond another begins reads as concurrency two, and across 50,000,000 records that artefact swamps the real signal.
Follow-up
  • A handler is not idempotent and you have found 400 overlapping jobs. Which of them actually caused damage, and what would you query to find out?
  • Peak concurrency for one job_type is 4 against a configured cap of 4. Is the cap working, or is the data hiding attempts that never started?

Built from the rounds and topics HDR candidates report.

Small steps. Visible outcomes.0 / 7 completed
ONE WEEK · YOUR PACE

Prepare, practise & reflect

One practical outcome each day. Spend longer where you need it.

0 / 7 done
01Map the HDR loop
  • Write out the reported sequence: Online Application, Initial Screening Call, Panel Interview, Office Visit.
  • For each round, write one sentence on what it is judging, from the description above, and mark the one you are least ready for.

Deliverable: A one-page map of the 4 reported rounds, with the weakest marked.

02Work CFD (Computational Fluid Dynamics)
  • Spend the session on CFD (Computational Fluid Dynamics), which HDR candidates report being tested on.
  • Write one worked example in CFD (Computational Fluid Dynamics) and time yourself on it.

Deliverable: One timed worked example in CFD (Computational Fluid Dynamics).

03Work ANSYS Fluent
  • Spend the session on ANSYS Fluent, which HDR candidates report being tested on.
  • Write one worked example in ANSYS Fluent and time yourself on it.

Deliverable: One timed worked example in ANSYS Fluent.

04Work Thermofluids
  • Spend the session on Thermofluids, which HDR candidates report being tested on.
  • Write one worked example in Thermofluids and time yourself on it.

Deliverable: One timed worked example in Thermofluids.

05Answer out loud: Resume & Past Technical Projects
  • Answer aloud, timed: Walk us through a complex project on your resume from start to finish.
  • Answer aloud, timed: Describe a technical challenge you encountered in a past project and how you resolved it.

Deliverable: Spoken answers to 2 reported Resume & Past Technical Projects question(s), under time.

06Answer out loud: Domain Knowledge & Technical Skills
  • Answer aloud, timed: How do you approach structuring code or scripts to automate repetitive engineering or data processing tasks?
  • Answer aloud, timed: What experience do you have working with CAD tools, spatial data, or domain-specific computational software?

Deliverable: Spoken answers to 2 reported Domain Knowledge & Technical Skills question(s), under time.

07Answer out loud: Behavioral & Team Collaboration
  • Answer aloud, timed: Tell us about yourself, your background, and why you want to work for HDR.
  • Answer aloud, timed: Describe a situation where you had to collaborate with a cross-functional team or non-technical stakeholders. How did you align on expectations?

Deliverable: Spoken answers to 2 reported Behavioral & Team Collaboration question(s), under time.

Expand any day for tasks and deliverables. Your progress is saved on this device.

Behavioural rounds judge the decision you made and what it cost.

Can you share an example of a time when you delivered an exceptional technical result that directly benefitted

medium
Resume & Past Technical Projects

Can you share an example of a time when you delivered an exceptional technical result that directly benefitted your team or company?

Approach
  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. Name the disagreement and how you resolved it with evidence.
Follow-up
  • What would you do differently if you ran that again?
  • How did you know your change caused the improvement?

Tell us about yourself, your background, and why you want to work for HDR.

medium
Behavioral & Team Collaboration

Tell us about yourself, your background, and why you want to work for HDR.

Approach
  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. Name the disagreement and how you resolved it with evidence.
Follow-up
  • What would you do differently if you ran that again?
  • How did you know your change caused the improvement?

Describe a situation where you had to collaborate with a cross-functional team or non-technical stakeholders.

medium
Behavioral & Team Collaboration

Describe a situation where you had to collaborate with a cross-functional team or non-technical stakeholders. How did you align on expectations?

Approach
  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. Name the disagreement and how you resolved it with evidence.
Follow-up
  • What would you do differently if you ran that again?
  • How did you know your change caused the improvement?

How do you manage competing priorities when working on multiple project deliverables with tight deadlines?

medium
Behavioral & Team Collaboration

How do you manage competing priorities when working on multiple project deliverables with tight deadlines?

Approach
  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. Name the disagreement and how you resolved it with evidence.
Follow-up
  • What would you do differently if you ran that again?
  • How did you know your change caused the improvement?

Tell us about a time you experienced friction or a disagreement within a project team and how you navigated it

medium
Behavioral & Team Collaboration

Tell us about a time you experienced friction or a disagreement within a project team and how you navigated it professionally.

Approach
  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. Name the disagreement and how you resolved it with evidence.
Follow-up
  • What would you do differently if you ran that again?
  • How did you know your change caused the improvement?

What type of work environment or team dynamic allows you to perform at your best?

medium
Behavioral & Team Collaboration

What type of work environment or team dynamic allows you to perform at your best?

Approach
  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. Name the disagreement and how you resolved it with evidence.
Follow-up
  • What would you do differently if you ran that again?
  • How did you know your change caused the improvement?
  • 01

    Can you share an example of a time when you delivered an exceptional technical result that directly benefitted your team or company?

  • 02

    Tell us about yourself, your background, and why you want to work for HDR.

  • 03

    Describe a situation where you had to collaborate with a cross-functional team or non-technical stakeholders. How did you align on expectations?

  • 04

    How do you manage competing priorities when working on multiple project deliverables with tight deadlines?

PracHub preparation framework ↗
How technical are the software engineer interviews at HDR?

Interviews at HDR focus more on practical software engineering experience, past projects, code quality, and problem-solving than on competitive algorithm puzzles. Expect detailed conversations about your resume, technology choices, and project execution rather than abstract whiteboarding.

HDR Software Engineer candidate reports ↗
What is the company culture like at HDR?

HDR is an employee-owned company, which fosters a collaborative, team-oriented, and supportive work environment. The culture emphasizes long-term employee growth, stability, professional development, and mutual success.

HDR Software Engineer candidate reports ↗
How long does the hiring process typically take?

The timeline varies by location and team demand. While fast-track candidates may complete the process in a few weeks, typical timelines range from 3 to 6 weeks from application submission to final offer decision.

HDR Software Engineer candidate reports ↗
Will I meet the team I am going to work with during the interview process?

Yes. HDR’s interview loop heavily involves potential team members. You will frequently meet with peer engineers, department managers, and cross-functional staff through panel interviews or office visits.

HDR Software Engineer candidate reports ↗
Are interview expenses covered if travel is required?

For roles requiring in-person interviews or site visits at distant office locations, HDR typically covers travel, meal, and lodging expenses arranged during the interview process.

HDR Software Engineer candidate reports ↗
What topics does HDR test in interviews?

HDR interviews most often cover Stakeholder Management, Communication Skills, Team Collaboration, Project Management, and CFD (Computational Fluid Dynamics). The exact emphasis depends on the specific role you apply for.

HDR Software Engineer candidate reports ↗
Sources & methodology 3 sources ↗

No official company page is cited. Rounds and questions come from candidate reports and PracHub editorial material; each source shows the date it was read.