Tango Interview Questions
& Process

The interview had 3 stages: first, an HR screening call. Second, an Excel take-home test, which I passed even though Excel wasn't in the job description. I thought the next step would be a hiring manager call, but instead, HR messaged me on WhatsApp asking for another take-home test, this time with SQL. I did that and waited. After a week, I messaged HR on WhatsApp to follow up and was told I didn't pass. I asked for technical feedback to learn from my mistakes, but they ignored my message. Then, I got basically the same rejection email, but from a different HR person. I asked them for feedback too, but got no response. It's frustrating how long it takes to review assignments, respond to candidates, and give basic technical feedback after multiple tests.

I had a weird and frustrating interview with Tango. First, I had a short interview with the team lead and heard about a home assignment. But a week later, I got rejected. Some weeks after, the recruiter contacted me again for the same home assignment for a new job. After I finished and sent it, the recruiter called and said my task was good, but they decided to hire juniors instead. I get that hiring can change, but it's not transparent or respectful of my time. It's a bummer to spend a lot of effort on a task and get this outcome. I hope this feedback helps them improve.

The interview process was really smooth and organized. From the first call to the last interview, everything was communicated well and scheduled fast. The recruiter and hiring managers were nice, upfront, and asked good questions, making it feel more like a chat than an interview. They also gave a lot of info about the job, what they expect, and the company vibe, so we could both see if it was a good fit. It felt really welcoming, professional, and put-together, a comfortable but still challenging process.

The interview process started with a call with a recruiter, followed by a short tech screening. Then, there was a technical interview. Regarding the last part, it wasn't inherently difficult, but it was hard to grasp what the interviewers were looking for. I do technical interviews regularly, and in my opinion, this interview wasn't well-structured. It felt like random tricky questions, more like Kotlin puzzles than a real interview. Finally, there was a system design segment where I had to explain how I'd implement a custom view that handles its own data retrieval and is distributed as a library. I was rejected a few days later, which didn't bother me much given the questionable business area and the requirement for 4 days in the office.