Truveris logo

Truveris Software Engineer Interview Questions
& Process

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

Based on 5 interview experiences · FREE TO READ

2.8 Rounds average
Average Typical difficulty
100% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Truveris.

Showing 3 of 5
Truveris logo
Truveris

Software Engineer

Engineering · more than a year ago

Entry Easy Positive experience Decline offer 2 rounds
Interview process
Recruiter call Technical screen
Interview formats
Behavioral Technical Coding

So, I had a basic phone interview and then an in-person tech screening that lasted a few hours. The first call was mostly introductions and then they asked a high-level programming question to see how I handled object-oriented programming and class structures.

Confirmed questions6 questions
  • What are your long-term career aspirations?
  • Could you provide a brief overview of yourself?
  • Can you describe how you would set up class relationships using OOP principles?
Truveris logo
Truveris

Software Developer

Engineering

Mid Average Positive experience Accept offer 3 rounds
Interview process
Technical screen Take home Onsite
Interview formats
Technical Coding Behavioral

The interview process was pretty standard for a dev role. Since I got referred, I think I skipped the first recruiter call. It began with an onsite interview and a short coding challenge. The interview itself was mainly about getting to know me and seeing if I'm a decent person to work with. The coding challenge was self-paced. They provided the data description and gave me a few minutes to look it over, then asked for my time estimate. Afterwards, I was left alone with a laptop to finish. The task involved parsing a CSV file, and I could use any language or tools, with internet access allowed. Using Python was a plus since Truveris is a Python shop. I met with the CTO, lead dev, and a couple of other team members, and again, it was mostly a get-to-know-you session. If the onsite went well, I was given a second coding challenge. This involved logging into a provided server with a Postgres DB already set up. It was designed to check my command-line and SQL skills. I had to analyze the database and write a moderately complex SQL query, then replicate that query in Python (using SQLAlchemy was a bonus). This challenge was also self-paced. After that, the interview was pretty much done; it was either a yes or a no.

Confirmed questions1 question
  • What are the advantages and disadvantages of database query caching versus client-side filtering?
Truveris logo
Truveris

Software Engineer

Engineering

Entry Average Positive experience No offer 2 rounds
Interview process
Recruiter call Technical screen Take home
Interview formats
Coding Technical

I applied in Nov 2020. The HR screen was professional and a tech phone review was quickly set up. The one hour review had 3 questions. The first was a language-specific question that was not easy. Then a coding test was done on CoderPad using Python 3. The interviewer expected test cases too.

Confirmed questions3 questions
  • Could you write a decorator that accepts parameters, possibly using functools?
  • What's the least number of coins needed to make a certain amount, considering both greedy and dynamic programming approaches?
  • How would you find anagram words?

Truveris Software Engineer Interview Questions

Quoted word for word from Truveris interview reports.

What's the least number of coins needed to make a certain amount, considering both greedy and dynamic programming approaches?

Read reports

Could you write a decorator that accepts parameters, possibly using functools?

Read reports

What are the advantages and disadvantages of database query caching versus client-side filtering?

Read report

Can you describe how you would set up class relationships using OOP principles?

Read report

Formats, difficulty and experience

Across all 5 Truveris interview reports.

Interview formats

Technical 35.7%
Coding 28.6%
Behavioral 28.6%
Other 7.1%

Interview difficulty

Easy 20%
Average 80%
Difficult 0%

Candidate experience

Positive 100%