Structural Engineer Interview Questions (2026) and How to Answer
By FindAJobAI team Updated How we wrote this page
Structural engineer interviews mix behavioral questions about past projects with technical checks on load paths, material behavior and the design codes you work to, plus scenario questions on what you'd do when a design clashes with a budget or a site condition changes mid-build. Expect at least one question on software you've used, such as ETABS, SAP2000, Tekla or Revit.
Interviewers want to see sound judgment under uncertainty, comfort with the numbers, and the ability to explain a technical decision to someone who isn't an engineer.
Below: 30 questions with what each one really asks and an answer outline, full sample answers to the 10 most asked, red flags to avoid and a 7-day plan.
Answering with STAR
Tell each story in four steps: the situation in a sentence, your task, the actions you took (most of the answer) and the result, with a number if you have one. Aim for about two minutes; the outlines show what to include, the details must be yours.
Behavioural questions (1–10)
How you've handled real situations. Answer each with one true story, in STAR order.
1.Tell me about a design you had to revise after a client or architect pushback.
What they're really asking: Can you hold a safe design while still working with other disciplines?
Answer outline (STAR)
- SituationAn architect wanted a longer cantilever than the first scheme allowed.
- TaskFind a structural solution that kept the architectural intent.
- ActionModeled two alternative framing options, checked deflection and cost, and presented both with trade-offs.
- ResultThe option chosen, and how the relationship with the architect held up.
Full sample answer (fictional example)
On a mixed-use project, the architect wanted a 24-foot cantilever at the corner to open up the lobby, more than our first scheme allowed without a very deep transfer beam. I modeled two alternatives: a steel transfer girder with a hung column above, and a deeper concrete band beam hidden in the ceiling cavity. I checked deflection, vibration and cost for both, then presented them side by side with a rough budget impact. The architect preferred the steel option since it kept the ceiling height they wanted. We detailed it together over two more rounds, and it held up through construction with no rework.
2.Tell me about a time you found an error in your own calculations.
What they're really asking: Do you catch mistakes before they reach a drawing, and own them when you don't?
Answer outline (STAR)
- SituationA load case you'd missed, found during a routine check before issue.
- TaskCorrect it without delaying the drawing set.
- ActionReran the model with the missing case, checked members against the governing combination, and flagged the change.
- ResultThe members that needed resizing, and the review step you added afterward.
Full sample answer (fictional example)
While finishing a warehouse frame design, I was doing a final review before issue and noticed I'd left out a wind uplift case on the roof purlins. I reran the model with the full set of combinations and found three purlin lines that no longer passed under the governing uplift case. I resized those members, checked the connection capacity again, and flagged the change clearly in the revision notes so the detailer wouldn't miss it. I also added a load-case checklist to my personal review process, which I still use before any issue.
3.Describe a project where you worked closely with contractors on-site.
What they're really asking: Can you adapt a design to real site conditions without compromising safety?
Answer outline (STAR)
- SituationUnexpected ground conditions found during excavation.
- TaskKeep the foundation design workable and on schedule.
- ActionReviewed the geotechnical report on-site, revised the footing design, and confirmed it with the geotechnical engineer.
- ResultThe revised foundation, and the days saved versus a full redesign.
Full sample answer (fictional example)
On a school addition, the excavation hit soil much softer than the geotechnical report had assumed for one corner of the footprint. I went to site with the geotechnical engineer, reviewed the exposed conditions, and we agreed to widen two footings and add a grade beam to redistribute load rather than deepen to bedrock, which would have meant a much longer delay. I revised the foundation plan within two days and confirmed the bearing capacity with updated test data. The project stayed close to schedule, and the contractor appreciated getting a workable answer quickly instead of a stop-work order.
4.Tell me about a time you disagreed with a senior engineer's decision.
What they're really asking: Will you raise a safety or design concern even when it's awkward?
Answer outline (STAR)
- SituationA connection detail you believed was under-designed for the load case.
- TaskGet the detail checked without undermining the senior engineer.
- ActionRan an independent check, brought the numbers rather than an opinion, and discussed it privately first.
- ResultThe detail that was revised, and the checking step added to the process.
Full sample answer (fictional example)
On a four-story office building, a senior engineer detailed a beam-to-column connection that I thought was under-designed for the wind load case. I didn't want to challenge him in front of the team, so I ran my own check overnight and walked into his office the next morning with the numbers rather than an opinion. He rechecked the load path with me and agreed the connection needed an extra row of bolts and a stiffer plate. We revised the detail before it went out for fabrication. Afterward he added an independent check of every lateral connection to our review checklist, and we have used it ever since.
5.Tell me about delivering a structural design under a tight deadline.
What they're really asking: Can you move fast without cutting corners on safety?
Answer outline (STAR)
- SituationA tender deadline that left little time for full detailing.
- TaskDeliver a design that was safe and biddable in time.
- ActionPrioritized the governing elements, used conservative assumptions for the rest, and flagged items for post-award refinement.
- ResultThe design submitted, and the refinements made once the project was awarded.
6.Tell me about a time you had to explain a technical decision to a non-engineer.
What they're really asking: Can you translate engineering reasoning for clients or owners without talking down to them?
Answer outline (STAR)
- SituationA client questioning why a transfer beam added cost to their renovation.
- TaskGet them to understand and accept the necessity of the beam.
- ActionUsed a simple diagram showing the load path and what would happen without it.
- ResultThe client approved the beam, and asked for the same explanation style on later changes.
7.Tell me about a project that didn't go the way you planned.
What they're really asking: Can you recover from a setback and learn from it rather than just move on?
Answer outline (STAR)
- SituationA foundation redesign triggered by a late geotechnical report.
- TaskAbsorb the change without derailing the schedule.
- ActionReworked the footing sizes over a weekend, communicated the delay honestly, and sequenced the rework around critical-path items.
- ResultThe schedule impact held to a few days, and the process changed for future projects.
8.Describe a time you mentored a junior engineer or an intern.
What they're really asking: Do you invest in developing others, not just getting your own work done?
Answer outline (STAR)
- SituationAn intern who struggled to connect textbook theory to real calculations.
- TaskGet them contributing real, checkable work.
- ActionPaired them on a small beam design, walked through the code clauses together, and reviewed every submission.
- ResultThey were doing independent member checks within two months.
9.Tell me about a time you had to push back on a schedule you felt was unrealistic.
What they're really asking: Will you flag a risk to the schedule rather than silently absorb it?
Answer outline (STAR)
- SituationA design phase compressed to leave no time for proper peer checking.
- TaskProtect the quality of the checking process.
- ActionLaid out what checking would and wouldn't get done at the proposed pace, with the risk attached.
- ResultThe schedule was adjusted, and the checking process stayed intact.
10.Tell me about collaborating with an MEP or geotechnical engineer on a tricky coordination issue.
What they're really asking: Can you resolve a cross-discipline clash productively?
Answer outline (STAR)
- SituationDuctwork routing that clashed with a transfer beam's depth.
- TaskFind a solution that worked for both disciplines.
- ActionProposed a shallower beam with a wider flange and checked it against deflection limits.
- ResultThe clash was resolved without raising the ceiling height, and the relationship stayed collaborative.
Technical and role-skill questions (11–22)
Can you do the work itself? Think out loud and name the trade-offs.
11.Walk me through how a load travels from a roof down to the foundation.
What they're really asking: Can you reason through a load path clearly, the core skill of the job.
Answer outline
- The roof load goes to purlins, then rafters or trusses, then beams or girders.
- From there it passes to columns or walls, then to footings, then to the bearing soil.
Full sample answer (fictional example)
I think of it as a chain where every link has to carry the load from the one above it. Roof loads land on purlins, which span to rafters or trusses, which bear on beams or girders. Those beams transfer load into columns or load-bearing walls, which carry it down to footings, and the footings spread it out enough that the soil can support it without excessive settlement. At each transfer point I check two things: that the receiving member has capacity for the load, and that the connection between them can actually transfer that force without failing first.
12.What's the difference between dead load, live load and lateral load, and why does it matter?
What they're really asking: Basic load classification that underlies every design check.
Answer outline
- Dead load is the structure's own permanent weight and fixed elements.
- Live load is variable occupancy or use load, such as people or furniture.
13.A beam is deflecting more than expected on-site. How do you investigate?
What they're really asking: Can you diagnose a real structural problem methodically, not just in theory.
Answer outline
- Check the as-built span, support conditions and actual loading against the design assumptions.
- Verify the material and section used match the specification, including any substitutions.
Full sample answer (fictional example)
I'd start by confirming the as-built conditions match the design: actual span, support type and whether the load on it matches what was assumed. Then I'd check if the specified section and material were actually what was installed, since substitutions happen more often than people admit. I'd also look for construction issues, like a support that's settling, a missing shim, or the beam accidentally acting as continuous over a support it wasn't designed for. Only after ruling those out would I revisit the design calculation itself, since in my experience the cause is usually in the field, not the model.
14.How do you decide between steel, concrete and timber for a given structure?
What they're really asking: Do you weigh engineering, cost and constructability together, not just preference?
Answer outline
- Consider span requirements, fire rating, speed of construction and site access.
- Weigh lifetime cost, including maintenance and future flexibility, not just the initial price.
Full sample answer (fictional example)
I weigh span and loading requirements first, since that narrows the options quickly. Then I look at fire rating requirements, since timber often needs more protection and concrete handles it naturally. Construction speed matters too: steel erects fast with a skilled crew, concrete needs cure time but less specialized labor in some markets. I also factor in what's actually available and well-supported locally, since a technically ideal material is no good if the regional supply chain or trade skill isn't there. Lifetime cost, including maintenance, often ends up deciding close calls.
15.How do you check a connection design, such as a bolted steel connection?
What they're really asking: Connections are where many real failures start; do you treat them with real rigor?
Answer outline
- Confirm the governing load case and whether the connection is shear, moment or a combination.
- Check bolt capacity, plate bearing, weld size and block shear against the code.
- Confirm the detail is practical to fabricate and erect, not just numerically adequate.
16.What design codes do you work to, and how do you stay current with changes?
What they're really asking: Code literacy and the habit of keeping it current, since codes change.
Answer outline
- Name the governing codes for the jurisdictions you've worked in, such as ASCE 7, ACI 318 or AISC 360.
- Follow code committee updates and attend continuing education on major revisions.
- Check which edition a project is contracted to before assuming the latest applies.
17.How do you approach a seismic or wind design for a new building?
What they're really asking: Lateral system design is often the hardest and most consequential part of the job.
Answer outline
- Determine the governing lateral force from the code based on location, height and occupancy.
- Choose a lateral system, such as moment frames, braced frames or shear walls, suited to the layout.
- Check the building's irregularities, since they can trigger stricter analysis requirements.
18.How do you calculate the governing load combination for a given member?
What they're really asking: Load combination logic is central to every design check you run.
Answer outline
- List the applicable factored combinations from the code for dead, live, wind and seismic loads.
- Run each combination and identify which produces the highest demand on the member.
- Check that unusual combinations, such as uplift cases, aren't overlooked.
19.What's the difference between serviceability and strength limit states, and why check both?
What they're really asking: Many designs fail on comfort or appearance, not actual collapse risk.
Answer outline
- Strength limit states check against failure, such as yielding or buckling.
- Serviceability limit states check deflection, vibration and cracking that affect use and comfort.
20.How do you model a structure in software like ETABS or SAP2000 without just trusting the output?
What they're really asking: Software fluency matters less than knowing when its output is wrong.
Answer outline
- Build a simplified hand-check for a few key members before trusting the full model.
- Confirm boundary conditions, load application and member releases match your intent.
- Sanity-check reactions and deflections against rough hand calculations.
21.What causes buckling in a steel column, and how do you guard against it?
What they're really asking: Stability failure is a core structural concept, separate from pure strength.
Answer outline
- Buckling is a sudden loss of stability under compression, often before the material yields.
- Slenderness ratio, unbraced length and end conditions all affect the buckling capacity.
- Guard against it with bracing, stiffer sections or shorter unbraced lengths.
22.How do you approach the design of a transfer structure or long-span element?
What they're really asking: Long spans and transfers concentrate risk and deserve extra scrutiny.
Answer outline
- Identify all the loads being collected and the path they need to reach.
- Check deflection, vibration and connection capacity more conservatively than a typical member.
- Consider constructability, since these elements are often heavy and awkward to erect.
Take-home or live exercise: tips
Structural interviews sometimes include a design problem on paper or a whiteboard, such as sizing a simple beam or sketching a load path for a given layout.
- State your assumptions out loud before calculating anything, since interviewers are checking your reasoning as much as the answer.
- Sketch the load path first, then attach numbers; a clear diagram often matters more than a perfect final figure.
- Round sensibly and say so, rather than chasing false precision on a whiteboard problem.
- If you're unsure of an exact code value, state the assumption and move on rather than stalling.
Situational questions (23–30)
Scenarios that test judgement: say what you'd do first, and why.
23.You discover a sign error in a calculation after the drawings have been issued for construction. What do you do?
What they're really asking: Do you act immediately on a safety-relevant error, even when it's embarrassing?
Answer outline
- Assess the real impact on affected members before raising the alarm.
- Notify your lead and the client immediately if there's any safety implication.
- Issue a correction and document what changed and why.
Full sample answer (fictional example)
I'd first work out exactly which members are affected and whether the error changes a pass to a fail, since that determines urgency. If there's any safety implication, I'd notify my lead and the client immediately rather than waiting for a convenient moment. I'd issue a correction with a clear revision note explaining what changed and why, so the contractor isn't confused about what to build. Afterward I'd look at how the error got through review and add a specific check, like a sign convention note, so the same mistake doesn't recur on the next project.
24.A contractor proposes a cheaper alternative to a specified material or method. How do you respond?
What they're really asking: Can you evaluate a value-engineering request on its merits, not just say no?
Answer outline
- Check whether the alternative meets the same performance and code requirements.
- Run the numbers to confirm capacity, durability and constructability are equivalent.
- Approve, reject or counter-propose with the reasoning documented either way.
Full sample answer (fictional example)
I treat it as a genuine evaluation, not an automatic no. I check whether the proposed alternative meets the same strength, durability and code requirements as the original spec, which sometimes means running new calculations rather than just comparing data sheets. If it checks out, I approve it and document the substitution clearly in the record. If it falls short in some way, I'll often counter-propose a modified version that gets the contractor some of the savings without giving up performance. Either way, the reasoning goes in writing so there's no ambiguity later.
25.You're asked to sign off on a design you haven't had time to fully check. What do you do?
What they're really asking: Will you protect your license and the public's safety under schedule pressure?
Answer outline
- Explain clearly what level of check has and hasn't been completed.
- Ask for the time needed, or scope the sign-off to what's actually been verified.
- Never sign something you can't stand behind, regardless of the pressure.
26.Mid-construction, the client asks to add a floor to the building. How do you respond?
What they're really asking: Can you assess a major scope change without just saying it's impossible?
Answer outline
- Check whether the existing foundation and lateral system have capacity for the addition.
- Scope the analysis needed and give a realistic estimate of time and cost.
Full sample answer (fictional example)
My first step would be checking whether the existing foundation and lateral system have any reserve capacity, since that determines whether this is realistic at all. I'd run a quick capacity check on the governing columns, footings and shear walls before giving any real answer. If there's a path, I'd scope out what needs reinforcing, like footing underpinning or added bracing, and give an honest estimate of time and cost. If the structure genuinely can't take it without rebuilding the foundation, I'd say so clearly rather than let the client assume it's just a drafting change.
27.You're reviewing a peer's calculations and find a significant error close to a deadline. What do you do?
What they're really asking: Will you raise a serious error even when timing makes it unwelcome?
Answer outline
- Confirm the error is real and understand its actual impact before raising it.
- Tell them directly and privately first, with the specific numbers.
28.A client wants to reduce the structural budget by cutting the peer review step. How do you respond?
What they're really asking: Can you defend a quality step that doesn't show up as a visible deliverable?
Answer outline
- Explain concretely what the peer review step catches that a single pass doesn't.
- Offer a reduced-scope review targeted at the highest-risk elements as a middle ground.
- Be clear about what risk remains if the step is dropped entirely.
29.Weather delays push the concrete pour into a cold snap. What do you check?
What they're really asking: Do you understand how construction conditions affect material performance?
Answer outline
- Check the specified concrete mix and curing requirements against cold-weather limits.
- Confirm the contractor's cold-weather protection plan, such as heated enclosures or blankets.
- Adjust strength testing or stripping times if curing will be slower than normal.
30.You're asked to design to a budget that seems too low for the span required. What do you do?
What they're really asking: Can you push back on an unrealistic constraint with evidence rather than just complying?
Answer outline
- Run a rough design to see how far the budget actually is from what's needed.
- Present the gap with options: reduce span, change system, or adjust budget.
- Avoid quietly under-designing to fit the number.
Red flags to avoid in your answers
Each one is quick to fix before the day.
Treating software output as correct without any hand-check.
Describe the simplified hand calculations you run to sanity-check a model before trusting it.
Being unable to explain a design decision without jargon.
Practice explaining one project's key decision in plain language, as if to a client.
Downplaying a safety-relevant error instead of flagging it quickly.
Walk through how you've raised and corrected an error, including who you told and when.
No clear answer on which codes or editions you actually use.
Know the governing codes for your recent projects, including the edition, before the interview.
How to prepare for a structural engineer interview in 7 days
An hour or two a day is enough; the order matters more than the length.
Day 1: Load-path refresh
Sketch the full load path for three different structure types from roof to foundation, from memory.
Day 2: Code and combinations review
Go through the governing load combinations in the codes you use most, and the clauses you reference often.
Day 3: Software sanity-check drill
Pick a past model and rebuild a simplified hand-check for two of its key members.
Day 4: Connection detailing practice
Sketch and size a bolted or welded connection for a given shear load, from scratch.
Day 5: Project walkthrough prep
Prepare a five-minute walkthrough of one project: the governing load case, the decision made, and the outcome.
Day 6: Mock scenario run
Talk through answers to three situational questions out loud, focused on judgment calls, not just the technical fix.
Day 7: Board practice
Practice sizing a simple beam or sketching a load path on paper under a timer, then rest.
Questions to ask the interviewer
Pick two or three; the answers tell you whether you want the job.
- Which codes and jurisdictions does the team design to most often?
- What software and modelling standards does the team use day to day?
- How are calculations and drawings checked before they're issued?
- How much client and contractor contact does this role involve?
- What's a recent project where the structural design had to change mid-build?
Preparation tips
- Review load-path and lateral-system fundamentals the night before; most technical questions start there.
- Bring one project you can walk through in detail: the brief, the governing load case, and the outcome.
- Know which codes the firm's projects typically use, and the edition if you can find it.
- Be ready to sketch a connection or a load path on paper or a whiteboard.
Prepare the general questions too: tell me about yourself, why do you want to work here? and why are you leaving? Afterwards, send a thank-you email; when the offer comes, negotiate the salary.
How we wrote this page
The FindAJobAI team wrote the questions, outlines and sample answers for structural engineer interviews. The people, employers and numbers in the samples are invented: copy the structure, and use details from your own work.
Once we track enough live structural engineer job ads, this page also shows the skills they ask for most, counted the same way as our in-demand skills report.
Last reviewed on November 1, 2026.