
Teikametrics Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 6 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Teikametrics.
Software Engineer
The interview process has 3-5 rounds depending on the role, but for a Software Engineer, expect around 3 rounds. First, a take-home coding assignment. Then, an in-person coding round that lasts for 1 hour. After that, a Manager Round where you discuss the role and responsibilities. Finally, an HR round.
- Take home assignment: Code a quiz app. Use TS for FrontEnd Engineer role.
- In-person coding round: Answer Algo and DS questions, around 2 questions in an hour.
- Manager Round: Discuss roles, responsibilities, and functions.
Software Engineer
So the interview was like in 3 parts. First there was this initial screen which was basically a chat about the role and my background, pretty chill. Then I had two more interviews that were kind of a mix of technical and behavioral. The first of these had a behavioral part with the manager, then a Python coding task – it was a data processing thing, not too hard. The second tech interview started with some talk about system design concepts, like high-level, no drawing stuff. Also got asked about Python and database design. Then there was an SQL skills test. Lastly, I talked to the product manager for a behavioral interview.
- Python and SQL coding assessment.
- Python and SQL coding assessment.
Software Engineer
So I had a phone interview with the CTO, and then I went in for three on-site interviews. The first part was a technical assignment, then I had lunch with some engineers, and then went back for the other two parts. The interviewer told me they weren't going to continue with me after the first part, and I could go home. I get why they did it, they didn't want to waste time, and I appreciate that. But I'm posting this hoping someone sees it and changes the process. It's a terrible way to treat candidates. As someone who interviews people now, I know they were trying to be respectful of my time, but it made me feel horrible, like they were saying 'you suck so much we don't want to bother with the other interviews.' Maybe it's okay if they tell candidates beforehand that they'll decide after the first interview whether to proceed. Just don't surprise people by kicking them out a third of the way through when they prepared for days and took a vacation day. For what it's worth, I didn't bomb the interview or offend anyone, at least I don't think so. My solution compiled and was close, even if not 100% correct.
- After they told me I could leave, they asked if I had any feedback for them.
Teikametrics Software Engineer Interview Questions
Quoted word for word from Teikametrics interview reports.
“Python and SQL coding assessment.”
Read reports →“After they told me I could leave, they asked if I had any feedback for them.”
Read reports →“In-person coding round: Answer Algo and DS questions, around 2 questions in an hour.”
Read reports →“Manager Round: Discuss roles, responsibilities, and functions.”
Read reports →“Take home assignment: Code a quiz app. Use TS for FrontEnd Engineer role.”
Read report →“HR Round: Discuss policies and salary negotiations.”
Read report →“Can you design one of the company's internal services?”
Read report →“What system design questions did you solve?”
Read report →“Could you tell me about the projects you are presently engaged with?”
Read report →Formats, difficulty and experience
Across all 6 Teikametrics interview reports.