Thornton Tomasetti logo
Thornton TomasettiSoftware Engineer
Updated · Reviewed by the Dataford team

Thornton Tomasetti Software Engineer interview questions & guide 2026

Every question Thornton Tomasetti interviewers actually ask, the frameworks that win the room, and the language hiring managers respond to.

4 rounds · ≈ 3-5 weeks
1
Initial Screening
2
Technical Discussions
3
Behavioral Assessments
4
Team Involvement

What is a Software Engineer at Thornton Tomasetti?

At Thornton Tomasetti, a Software Engineer occupies a vital intersection between cutting-edge computational technology and high-stakes structural engineering. You are not merely writing code; you are building the digital tools that allow our firm to design, analyze, and maintain some of the world’s most iconic and complex structures. Your work directly impacts the efficiency of our project delivery and the safety of the built environment.

This role requires a unique blend of technical precision and an appreciation for the physical world. You will collaborate with structural engineers, architects, and project managers to translate complex engineering challenges into scalable software solutions. Whether you are automating repetitive design tasks, developing custom plugins for industry-standard software, or architecting data-driven applications, your contributions will have a tangible, lasting impact on the firm’s ability to innovate and solve the "impossible" in engineering.

Common Interview Questions

The following questions are representative of the patterns observed in Thornton Tomasetti interview experiences. While the exact technical focus may shift depending on the specific team (e.g., Forensics, Structural, or Facade), these categories highlight the core competencies we evaluate.

Technical & Domain Knowledge

These questions assess your foundational engineering understanding and your ability to apply software concepts to structural problems.

  • How would you explain the concept of a diaphragm in structural analysis?
  • What is your proficiency with industry-standard design and analysis software?

Access the full Thornton Tomasetti Software Engineer prep plan

  • Every Software Engineer question, updated weekly
  • Model answers with full code walkthroughs
  • Recent, real interview reports
Get my prep plan
03 · Question bank

The questions most likely to come up

Sorted by relevance to this company
Your Strengths and WeaknessesEasy
Tests self-awareness and how you position yourself for success in an Account Executive role at Aqr.
Trade-offsSuccess CriteriaRisk Assessment
2D Moment Frame Diagrams and DetailingHard
Assesses your ability to connect analysis outputs to reinforcement detailing decisions.
Coding
Access the full Thornton Tomasetti Software Engineer prep plan
Everything you need to walk in ready.
Get my prep plan

Getting Ready for Your Interviews

Preparation for Thornton Tomasetti should be centered on demonstrating both your technical aptitude and your genuine interest in the intersection of engineering and technology. You will be evaluated on your ability to articulate your past work clearly and your potential to grow within our project-driven environment.

Role-Related Knowledge – We look for candidates who understand the "why" behind the code. Be prepared to discuss not just the languages you use, but how your software solutions solve real-world structural or design problems.

Problem-Solving Ability – You will be expected to walk us through your thought process. When faced with a technical challenge, structure your response to show how you decompose complex requirements into manageable, actionable steps.

Cultural Alignment – Our projects often require intense collaboration. We evaluate how you communicate with non-technical stakeholders and whether you show a proactive, team-oriented mindset.

Interview Process Overview

The interview process at Thornton Tomasetti is designed to be conversational and collaborative, though it can vary in rigor depending on the office location and the complexity of the specific role. Most candidates experience a mix of technical discussions and behavioral assessments that focus on your professional history and academic background. You should expect to meet with a variety of team members, ranging from peers to senior principals, as we believe in involving the entire team in the hiring process.

06 · The loop

The interview process, end to end

≈ 3-5 weeks · 4 rounds
1
Initial Screening

First contact often via phone or video call to assess candidate fit.

2
Technical Discussions

In-depth conversations with technical staff focusing on skills and problem-solving.

3
Behavioral Assessments

Evaluation of professional history and academic background through behavioral questions.

4
Team Involvement

Meetings with various team members, including peers and senior principals.

This timeline illustrates the typical progression from an initial screening—often via phone or video call—to more in-depth interviews with technical staff and leadership. Candidates should interpret this as a guide to manage their preparation energy: focus your initial efforts on your resume and past projects, and reserve your "deep dive" technical preparation for the later stages.

Deep Dive into Evaluation Areas

Technical Proficiency

This area evaluates your command of the tools and methodologies required to support our engineering workflows. We look for a balance between theoretical knowledge and practical application.

Be ready to go over:

  • Software Proficiency – Your familiarity with languages and tools used in structural modeling or automation.
  • Engineering Fundamentals – Basic understanding of structural analysis concepts that your software will influence.

Access the full Thornton Tomasetti Software Engineer prep plan

  • Every Software Engineer question, updated weekly
  • Model answers with full code walkthroughs
  • Recent, real interview reports
Get my prep plan
08 · Topic breakdown

What they actually test for

Topic distribution
All topics
Resume-Based Technical DiscussionBehavioral InterviewingTechnical Storytelling About ProjectsCommunication SkillsTechnical Q&A (General)

Key Responsibilities

As a Software Engineer, your day-to-day work centers on bridging the gap between computational power and structural reality. You will be responsible for developing and maintaining custom applications that facilitate the design and analysis process. This involves writing efficient, clean code that integrates with existing platforms to streamline the workflows of our structural engineers.

Collaboration is a core component of your responsibility. You will work alongside project teams to identify bottlenecks in the design process and propose software-based solutions. Whether you are helping a team automate the generation of structural reports or developing a tool to visualize complex data, your output is a direct service to the engineers who are designing the firm's projects. You will also participate in peer reviews and contribute to the firm’s internal technical knowledge base.

Role Requirements & Qualifications

A strong candidate for Thornton Tomasetti is someone who is not only technically capable but also curious about the built environment.

  • Must-have skills: Proficiency in programming languages relevant to engineering (e.g., Python, C#, or similar), strong analytical and problem-solving capabilities, and the ability to articulate complex technical ideas clearly.
  • Nice-to-have skills: Prior experience in structural engineering or the construction industry, familiarity with CAD/BIM software APIs, and a proven track record of automating complex workflows.
  • Experience level: We value both entry-level candidates who show a strong aptitude for learning and seasoned engineers who can bring fresh, scalable solutions to our established processes.

Frequently Asked Questions

Q: How long does the interview process typically take? A: While timelines vary by office and role, the process generally moves from a phone screen to one or two rounds of interviews over the course of a few weeks. We strive to maintain transparent communication throughout.

Q: Is there a formal coding test? A: Not always. Many of our interviews are conversational, focusing on your past projects and your ability to solve engineering-related problems, though some roles may include a brief technical or conceptual assessment.

Q: What is the best way to stand out during the interview? A: Come prepared with 2–3 specific stories about projects where your software skills directly improved an outcome. Demonstrating an interest in structural engineering or architecture—beyond just the code—will help you resonate with our team.

Q: What is the culture like at Thornton Tomasetti? A: We are a firm of experts who are passionate about our work. You will find an environment that is collaborative, professional, and deeply focused on innovation and project excellence.

Other General Tips

  • Show Your Work: Bring examples of your past projects, whether they are school-related or professional. Quantifying your impact—such as "I reduced processing time by 20%"—is highly effective.
  • Ask Insightful Questions: Use your time at the end of the interview to ask about the team’s current technical challenges or how they balance software development with project deadlines.
  • Know Your Audience: You will likely be interviewed by a mix of managers and engineers. Tailor your language to be accessible to those who may not be software experts.
  • Be Prepared for Follow-ups: If you don't hear back immediately, it is professional to send a polite follow-up email after a week or two, but maintain patience as our project cycles can be quite busy.

Summary & Next Steps

A career as a Software Engineer at Thornton Tomasetti offers the rare opportunity to apply your technical skills to some of the most significant engineering challenges in the world. By focusing your preparation on your past projects, your ability to communicate technical solutions, and your genuine interest in the structural engineering domain, you will be well-positioned to succeed in your interviews.

We encourage you to review your own experiences through the lens of the evaluation areas outlined here. Focused, deliberate preparation will allow you to present your best self to our team. For further insights and resources to refine your approach, continue exploring the guidance available on Dataford. We look forward to seeing the unique perspective you can bring to our firm.

14 · Compensation

What this role pays

44 reports
USUSD
Estimated total compHigh confidence · 44 data points
$0k-$0k
Median $91k / year
Base salary · 100%Stock (RSU) · 0%Cash bonus · 0%
25thEntry / smaller markets
$52k
50thTypical offer
$91k
90thTop performers / major metros
$130k
Breakdown by component
Base salary
100% of total
$52k$125k
$89k
median
Stock (RSU)
0% of total
$0$0
$0
median
Cash bonus
0% of total
$0$0
$0
median
Aggregated from 44 self-reported salaries via Glassdoor. Estimates only. Verify against your offer.

This module provides an overview of typical compensation ranges for our engineering roles. Please note that these figures are based on market data and should be used as a baseline for your own research; actual offers will depend on your specific experience, location, and the requirements of the role.

15 · The role

Inside the Software Engineer guide at Thornton Tomasetti

16 · More at this company

Other roles at Thornton Tomasetti

18 · FAQ

Thornton Tomasetti Software Engineer interview FAQ

Answered from real candidate and compensation data
How hard are Thornton Tomasetti Software Engineer interviews, and what does the difficulty level look like?
Candidates report the overall interview difficulty as average. That lines up with a process that mixes screening conversations, technical discussions, and behavioral assessments rather than being exclusively hard coding at every step. You should still prepare to clearly explain your past projects and walk through your problem solving.
What are the interview rounds for Thornton Tomasetti Software Engineer roles?
Thornton Tomasetti typically starts with an initial screening, often by phone or video call, to assess fit. After that, candidates go through technical discussions with technical staff, then behavioral assessments focused on professional history and academic background, and finally team involvement with peers and senior principals. The rigor can vary by office location and role complexity.
What technical topics get tested for Thornton Tomasetti Software Engineer interviews?
Expect a resume-based technical discussion and problem-solving questions, with an emphasis on explaining the thinking behind your solutions. The role also evaluates technical communication, behavioral fit and motivation, and general technical Q&A. For domain context, be ready to connect software concepts to structural engineering problems, and example topics include structural analysis concepts like a diaphragm and programmatic approaches to engineering calculations.
What behavioral questions should I prepare for Thornton Tomasetti Software Engineer interviews?
You will be assessed through behavioral interviewing that covers your past work experience, your specific role on projects, and how you handle professional challenges. The process also includes evaluating behavioral fit and motivation for the company, plus how you communicate in collaborative settings. Be ready for questions like “Tell us about your past work experience and the specific role you played in your team” and “Why are you interested in joining Thornton Tomasetti specifically?”
How much does Thornton Tomasetti pay for a Software Engineer, and what pay range should I expect?
Compensation information from candidate and job-posting reports shows a base minimum of $52k, and total compensation up to $129,607. Pay varies by level and location, so your final offer will depend on where you fit in the range.
What should I prioritize to prepare for Thornton Tomasetti Software Engineer interviews?
Plan to spend most of your time on your resume and past projects first, because the early loop includes initial screening and resume-based technical discussions. Later stages will likely require deeper technical preparation and you should be ready to walk through your thought process, decompose problems, and validate your approach. Given the team involvement with peers and senior principals, prioritize clear technical storytelling and communication with non-technical stakeholders.