Tessian logo

Tessian Backend Engineer Interview Questions
& Process

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

Based on 14 interview experiences · FREE TO READ

3.7 Rounds average
Average Typical difficulty
71.4% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Tessian.

Showing 3 of 14
Tessian logo
Tessian

Backend Engineer

Engineering · more than a year ago

Entry Average Neutral experience No offer 7 rounds
Interview process
Recruiter call Technical screen Technical screen Onsite Onsite Onsite Background check Offer
Interview formats
Coding Technical Behavioral System Design

So the whole process basically starts with resume shortlisting, then there's an online test. After that, there's a Codepair round and then 3 virtual 1:1 interviews all on the same day. The Codepair and virtual 1:1 rounds were usually about 45-60 minutes long. Since I have about 2+ years of experience, there was also one more round with a senior person from the org, which involved some informal discussions and questions about my past experiences. That round was about 30 minutes.

Confirmed questions5 questions
  • Tell me about your past experiences and answer some technical questions on DS Algo/Problem Solving in a Codepair round, where you need to implement and run the solution.
  • We asked one technical question and its extension.
  • Let's discuss your past experience and then tackle a somewhat real-world open-ended problem-solving question to see your thought process and how we can optimize it.
Tessian logo
Tessian

Backend Engineer

Engineering · more than a year ago

Mid Average Positive experience No offer 4 rounds
Interview process
Technical screen Technical screen Technical screen Recruiter call
Interview formats
Coding Technical Behavioral

Applied through Stackoverflow. Round 1 was a 2 hour Hackerrank test. Round 2 was a 1 hour Codepair interview with the Engineering Manager. Round 3 was a 2 hour Codepair interview with 2 Senior Software Engineers. Round 4 was a 1 hour Values Interview with the Head of Engineering. I thought it went well, but didn't get an offer. The HR said I was a bit slow on one problem and didn't explain my work enough, even though they didn't ask me to. So, pay attention to everything, it all counts.

Confirmed questions7 questions
  • What is the maximum result for the expression +-abc with given ranges for a, b, and c?
  • Calculate the co-occurrence of words between two sentences: sentence1: I have to eat and sentence2: I have to go to work.
  • Explain Multi Threading in Python in detail.
Tessian logo
Tessian

Backend Engineer

Engineering · more than a year ago

Mid Easy Negative experience No offer 4 rounds
Interview process
Take home Recruiter call Technical screen Onsite
Interview formats
Coding Technical System Design Behavioral

I had a Hackerrank challenge that took 90 mins, followed by a brief recruiter call about next steps. Then there was a 1 hour live coding pair round. After that, there was a 2 hour round covering algorithms, system design, and competency. The whole process could be improved. After the live pair coding, the recruiter told me I was good for the next round. But then, for over a week, the recruiter didn't respond about next steps or schedule calls. They also didn't reply to my 3-4 follow-up emails. After more than a week, the recruiter scheduled another round (just to schedule it, I guess) which I felt went okay. Immediately, within hours, I got a rejection email. My advice to the recruitment team: Don't waste time. If you find a better candidate, just say so. Don't schedule rounds unnecessarily. Communicate better. Don't disappear for over a week without replying to follow-ups.

Confirmed questions7 questions
  • For the Hackerrank challenge, the question was about prefix expression.
  • In the live coding round, we had to find the co-occurrence of words.
  • For the algorithms and competency round, I was asked to find and fix bugs in a code.

Tessian Backend Engineer Interview Questions

Quoted word for word from Tessian interview reports.

Implement the get_all_urls function to retrieve all reachable URLs from a given URL.

Read reports

Find counts of the cooccurrence in all the sentences in a paragraph.

Read reports

Given a preorder mathematical expression, convert it to inorder and evaluate it.

Read reports

How to get a random line from a very large file, ensuring equal probability for each line?

Read reports

What occurs when a URL is entered into a browser and the enter key is pressed?

Read report

What is the maximum result for the expression +-abc with given ranges for a, b, and c?

Read report

How would you find the co-occurrence of words within a line?

Read report

Describe step-by-step what happens when you type a URL in a browser, from HTTP requests to network calls.

Read report

Formats, difficulty and experience

Across all 14 Tessian interview reports.

Interview formats

Technical 34.1%
Coding 31.8%
Behavioral 29.5%
System Design 4.5%

Interview difficulty

Easy 7.1%
Average 92.9%
Difficult 0%

Candidate experience

Positive 71.4%
Neutral 14.3%
Negative 14.3%