Thornton Tomasetti logo
Thornton TomasettiSoftware Engineer
Updated Feb 1, 2026

Thornton Tomasetti Software Engineer Interview Experiences 2026

Real, anonymous reports from people who interviewed for Software Engineer at Thornton Tomasetti, newest first and distilled into what to expect across the loop.

Get your personalized Thornton Tomasetti Software Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
Build my free plan
Hot & recentNewest first
7 months ago
Average Neutral San Francisco, CA

After applying online, I moved into a phone conversation where the goal was simple: understand my background, work history, and motivation for joining. That call was led by a Senior Engineer and felt like it was really meant to connect my experience to the team and the role, not to trick me.

About a week later, I had a technical screen that ran remotely. The questions were grounded in what I’d studied and what I’d done before—more of a check on my understanding than a formal coding-style assessment. It still required me to be clear about my knowledge, but the atmosphere stayed conversational and I didn’t feel blindsided.
11 months ago
Easy Positive United States

I applied online and the process moved fairly quickly. The first conversation was with someone from the team (a Senior Engineer or other interviewer, depending on the round) where we talked through my background and what I was interested in, and how my experience connected to the role. A couple of days or a week later I had a more formal interview, either in person at their London office or remotely, and it felt intentionally conversational rather than like a test.

During the interview, the focus stayed on my resume and academic path. I went line-by-line through my work history and what I’d studied, and I talked about my internship experience and the kind of role I was applying for. Several times, we also reviewed my understanding of structural engineering and related work—why I’d chosen it, what I’d worked on, and what skills I had from school or prior projects. There was no heavy live technical testing in the versions I experienced; it was mostly discussion, with questions that probed my knowledge and motivation more than anything else.

Unlock every Software Engineer interview experience

Real Software Engineer interview experiences
  • Difficulty, sentiment and outcomes
  • New reports added every week
See all experiences
Share your interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.

What to expect

Distilled from the reports

Initial Screening

The interview process typically begins with a phone conversation focused on the candidate's background, work history, and motivation for the role, creating a relaxed atmosphere rather than a high-pressure test.

Phone screenBackground checkMotivation

Technical Assessment

Candidates may experience a technical screen that emphasizes understanding and discussion of engineering concepts rather than high-pressure coding tests, with questions often rooted in their academic and project experience.

Conceptual understandingTechnical questionsEngineering fundamentals

Behavioral and Fit Interviews

Interviews often include discussions about the candidate's experiences, motivations, and fit for the team, with a focus on clarity and alignment with the company's work culture.

BehavioralCultural fitExperience alignment

On-site Experience

On-site interviews may involve a mix of technical discussions and informal interactions with team members, providing insight into the work environment while assessing the candidate's reasoning and problem-solving skills.

On-siteTeam interactionProblem-solving

Communication and Professionalism

Candidates have reported varying experiences with communication throughout the process, with some experiencing smooth interactions while others faced delays and unprofessional behavior from recruiters.

CommunicationProfessionalismRecruiter experience

Overall Difficulty and Outcome

The overall difficulty of the interviews can vary, with some candidates finding the process straightforward and others feeling challenged by the technical depth, impacting their final impressions and outcomes.

Difficulty levelInterview outcomeCandidate experience