Ho sostenuto un colloquio presso Truveta (Bellevue, WA)
Colloquio
Medium leetcode question and a sitdown discussion with a mid level software engineer. I'd suggest preparing for general DSA concepts, like arrays, hashmaps, BFS, DFS, linked lists, trees and REST APIs.
1
Altre recensioni di colloqui per Software Engineer presso Truveta
Ho presentato la mia candidatura online. Ho sostenuto un colloquio presso Truveta
Colloquio
Standard recruiter call followed by technical interview. Recruiter was nice, did a good job selling the company. For the technical, the question was leetcode easy. Process was on the slower side, more prompt follow ups by the recruiter would have been ideal.
Domande di colloquio [1]
Domanda 1
Leetcode easy style question - basically a linked list.
Ho presentato la mia candidatura online. Ho sostenuto un colloquio presso Truveta nel mese di ott 2025
Colloquio
The interview process was an initial recruiter call, then two one-hour technical interviews followed by a 30 minute culture fit interview with an executive. Each interview was scheduled more or less one week apart from another and you move on in the process if you pass the previous interview. The recruiting team was also very prompt in telling you whether you were moving forward in the process, usually within 1-2 days of the interview.
The two technical interviews were pretty easy and straightforward. The recruiter had told me that they don't do LeetCode style questions and its more like "real-world" problems. However, the questions that the interviewers asked me were basically medium leetcode questions. The recruiter also told me that they don't do system design as part of their interview loop.
First interview was overall fine/easy. Second interview was also straightforward and easy. The culture fit chat was probably the worst interview. Like I said, the recruiter told me that system design was not a part of the interview loops and you would think that "culture fit" chat means being asked behavioral questions -- you thought wrong! The interviewer started asking me very system design-esque questions like how I would design a system to process millions of patient data a day, what database I would use, how I would pre-process data, what information I would need to know about the data, etc. No amount prep would have prepared me for that interview lol because I wouldn't have known to expect that and I did not prep for system design. I felt like the interview process was overall fine up until that final interview which was a total crapshoot. Since it's a startup, they probably don't have a standardized process for interviewing and the interviewers do whatever. I felt like the interviewer in the final interview was trying to put me in the hot seat with these difficult questions that honestly shouldn't have been part of the interview. The recruiting team should do a better job of making sure the interviewers know what the interview should consist of and have them stick to it.
Domande di colloquio [3]
Domanda 1
Interview 1: the Valid Sudoku leetcode question, followed by some behavioral questions like:
- "Describe a time when you faced significant obstacle in meeting a key goal"
- "Tell me about a time you were under pressure to meet a deadline"
- "Tell me about a recent project/challenging project and what you learned from it"
Interview 2: Given a binary matrix of 0s and 1s, replace 0s with 1s if it not surrounded by 1s in all directions. Then he expanded the question to: if you have groups of zeroes, convert groups of 0s to 1s if not surrounded by 1s in all directions
- "Tell me about your recent work" and "What was challenging about it?" and "What would I do differently?"
- "What is something I want to learn or a goal I have in my next role"
- "What is something new you learned recently?"
Culture Fit interview: How would you design a system that could handle processing millions of patient data a day? What database would you use? What open-source tools would you use? How would you pre-process the data? How would you handle structured data and unstructured data differently? What level of (healthcare) domain knowledge do you think an engineer has to have in the this space?
- "Why Truveta? Why healthcare tech?"
- "Tell me about a time when you had conflict with a teammate and the debates went on and on for days with no end, how did you resolve that situation?"
- "What does culture mean to you?"
