
Tremendous Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 11 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Tremendous.
Software Engineer
It kicked off with a recruiter chat, which was nice. After that, there was another technical screen with a straightforward, non-Leetcode question. Then came the take-home part, which was also the final interview. For that, I had to design a solution to a technical problem and then code it out over several stages during the 'virtual onsite'. The whole thing was pretty standard, and I liked that it wasn't full of those typical Leetcode-style puzzles. However, the take-home question itself wasn't great. They said it was about seeing how I solve problems and design technical solutions, but it really felt like they wanted a very specific answer that I was supposed to come up with on my own. It does let you show your thinking, but in the end, it seems like they just want you to reach the same conclusions they did, which felt a bit off.
- Could you implement a fuzzy search/ranking algorithm using Ruby?
- How would you modify an existing internal application to support multiple teams or tenants?
- Design and implement a multi-phase solution for a given technical problem.
Software Engineer
The whole process dragged on for 2 months. It felt like the interviewers weren't really into it at any point, and when I didn't make it, they didn't give any useful feedback. Turns out I had bombed an earlier stage, but they let me finish all the interviews anyway before telling me I'd failed way back when.
- How would you convert a single-tenant system into a multi-tenant one?
Software Engineer
After applying online at Tremendous, I was a bit apprehensive because of the mixed reviews about the software engineering interview process here. Nevertheless, the company seemed interesting, so I decided to proceed. The process is exactly as others have described: - Recruiter call - Technical screen - Take-home test with a written assignment - System design discussion on the assignment - Two timed tests (interviewers only showed up at the start and end) - Interview with someone from the exec team The entire process spanned about three weeks. I received timely updates about the next steps, which kept the process smooth. In contrast to some of the previous software engineer reviews, I found the process to mimic actual day-to-day work. If you're expecting generic leet-code style interviews, then you're going to have a bad time. In my opinion, they seem to value autonomy and asynchronous communication, and the process works to find a fit for their working style. If you are looking to work at a place like that, you should definitely give Tremendous a shot.
- How would you convert a single-tenant system into a multi-tenant one?
- Describe how to fetch data from an external API and implement frontend-specific features.
Tremendous Software Engineer Interview Questions
Quoted word for word from Tremendous interview reports.
“How would you modify a system's architecture to transition from single-tenancy to multi-tenancy?”
Read reports →“How would you convert a single-tenant system into a multi-tenant one?”
Read reports →“Could you implement a fuzzy search/ranking algorithm using Ruby?”
Read reports →“Describe how to fetch data from an external API and implement frontend-specific features.”
Read reports →“Have you ever changed your mind about something you used to believe or think?”
Read report →“How would you sort an array of strings, considering various scenarios?”
Read report →“How would you refactor this code?”
Read report →“Could you draft a technical overview concerning the migration from a single-tenant to a multi-tenant architecture?”
Read report →“Design and implement a multi-phase solution for a given technical problem.”
Read report →Formats, difficulty and experience
Across all 11 Tremendous interview reports.