Tessella logo

Tessella Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 63 interview experiences · FREE TO READ

2.3 Rounds average
Average Typical difficulty
54% Positive experience

Which role are you interviewing for?

7 roles · 63 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Tessella.

Showing 4 of 63
Tessella logo
Tessella

Programmer Analyst

Engineering · a year ago

Entry Average Positive experience Accept offer 2 rounds
Interview process
Recruiter call Technical screen Presentation Onsite
Interview formats
Behavioral Technical Coding Presentation

The first interview was a phone call that lasted about an hour. We talked about my interest in the role and some basic coding questions. It felt pretty relaxed, more like a chat. The second interview was a full day at the Abingdon office, starting at 9 AM and wrapping up around 4 PM. A big part of the day involved a programming task I worked on, with breaks for presentations and lunch. I also had to give a short presentation on a topic of my choice to show my presentation skills. Lunch was at a pub with a staff member, and I got to see a presentation about what the company does. The day ended with me presenting the coding task I completed. The coding task itself wasn't too hard, though working with the internet for it was a new experience for me.

Confirmed questions3 questions
  • Could you explain polymorphism?
  • Which programming languages are you familiar with?
  • What are your salary expectations?
Tessella logo
Tessella

Data Scientist/Software Developer

Engineering · more than a year ago

Entry Average Negative experience No offer 2 rounds
Interview process
Recruiter call Technical screen Onsite Presentation Background check
Interview formats
Coding Behavioral Technical Presentation

The first interview was fine, we talked about my experience and interest in the role. The second interview was a full day, from 9 am to 3 pm. It started with a coding exercise, a password generator problem to test coding skills. Then I spoke with various staff members, some for small talk and others to discuss my projects. After lunch, my coding exercise was reviewed. Following that, I gave a presentation on a prepared topic to a senior staff member, and then had final talks. It was a good experience, though a bit long. I didn't receive feedback after being informed I was unsuccessful, which felt disrespectful given the preparation time.

Confirmed questions5 questions
  • What programming languages are you familiar with?
  • Tell me about your experience and why you're interested in this role.
  • Can you create a password generator?
Tessella logo
Tessella

Data Scientist

Analytics · more than a year ago

Entry Average Positive experience Accept offer 3 rounds
Interview process
Recruiter call Take home Technical screen
Interview formats
Behavioral Technical Coding

The interview in Italy had 3 parts. It started with a phone call where they asked about my interest, some project info, etc. Then there was a technical test that I had 4 hours to complete. They gave me unbalanced, not totally clean data and asked me to do classification, and they provided info about the data and classes. Finally, they called me again to go over my results and code and asked some follow-up why and how questions.

Confirmed questions4 questions
  • Regarding missing data, what was the percentage and how did you address it?
  • What approach did you take to handle the unbalanced data, and why did you select that method?
  • Could you elaborate on your feature selection process?
Tessella logo
Tessella

Data Scientist/Software Engineer

Engineering · more than a year ago

Mid Easy Neutral experience Decline offer 7 rounds
Interview process
Recruiter call Technical screen Take home Presentation Group Background check Offer
Interview formats
Technical Coding System Design Presentation Behavioral

It was a pretty standard interview process, starting with a 30-minute phone screen and then a full day of interviews. The phone screen involved talking about my background and some basic C++ programming questions, like the difference between vectors and arrays and how pointers function. The interviewer mostly used that time to explain the role and the company. The in-person interviews were at their main office in Abingdon. The day included a 30-minute math/data science interview that wasn't too difficult, followed by a programming assignment. The assignment was long and focused on architecture design, specifically classes and inheritance, and didn't require algorithm knowledge. It used old C++98 and an 8-year-old version of gcc. The rest of the day involved lunch with a senior project manager, a short presentation I had prepared, a demo of one of their projects, and a quick HR chat. There were hardly any questions about cultural fit. I had to complete a personality test and send it back, which I didn't do, and it apparently didn't impact my application, raising questions about unnecessary bureaucracy. I left feeling like I hadn't really been interviewed, meaning I couldn't showcase my strengths. Since it's a software engineering role, there was no face-to-face coding interview. The entire process from applying to getting an offer took over four months, with long waits between stages. I eventually turned down the offer for a better package elsewhere with a better feel for the work and office. Tessella clearly puts effort into recruiting, but their compensation doesn't reflect a strong interest in keeping good people.

Confirmed questions2 questions
  • Can you explain the difference between C++ vectors and arrays?
  • Could you describe how a pointer operates in C++?

Tessella Interview Questions

Quoted word for word from Tessella interview reports.

Can you explain the difference between C++ vectors and arrays?

Read reports

Could you explain the workings of the Java garbage collector?

Read reports

Can you describe an algorithm that effectively finds the global fitting minimum without getting trapped in local minima?

Read reports

Explain the differences and use cases for inheritance versus composition/aggregation.

Read report

What are the computational aspects and potential challenges of regression analysis?

Read report

How do you ensure your code is robust against bad data?

Read report

Can you elaborate on keywords related to dynamic polymorphism?

Read report

Formats, difficulty and experience

Across all 63 Tessella interview reports.

Interview formats

Behavioral 33.7%
Technical 27.4%
Coding 18.3%
Presentation 17.1%
Group 1.7%

Interview difficulty

Easy 23.8%
Average 60.3%
Difficult 15.9%

Candidate experience

Positive 54%
Negative 19%
Neutral 27%

Reports by job function

Engineering 45
Analytics 16
Marketing 1
Sales 1