Tenna interview questions

The interview process included an initial recruiter screen, followed by a one-hour take-home technical assessment. The assessment consisted of a mix of JavaScript trivia-style questions and two coding feature exercises. After that, I had a one-hour interview with a team lead, which included an additional 20-minute technical assessment. The final round was a one-hour interview with the VP, which also included another technical assessment. The final assessment felt meaningfully different from the earlier stages. Rather than building on the prior assessment or evaluating clearly defined role-related skills, the VP presented problems based on technical challenges the company had previously solved internally. The expectation seemed to be that the candidate would reason their way back toward the same architectural or implementation decisions the company had already chosen, without much prior context. Overall, the process felt heavier and less transparent than expected. There were multiple technical evaluations across the process, and the final round introduced a much more difficult and company-specific problem-solving format than the earlier steps suggested. After approximately a week and a half of waiting following the final interview, I received a generic rejection email from a no-reply address. Given the number of interview rounds and assessments involved, more specific feedback or a more personal closing communication would have been appreciated.

Job role was about 5 different positions mashed into one, expecting multiple years of full competency in all, with only entry-level pay offered. The questions ranged from "What coding languages do you know" to "What is your familiarity with video editing" and very hyper specific questions about my current team.