Triple Point Technology Interview Questions
& Process

The interview kicked off with an aptitude test that included a few programming questions, nothing too hard. Then came a psychometric test, which felt like it was about speed and accuracy, though I'm not sure why they included it. Round 3 was about problem-solving; they asked me to design a lift system to minimize waiting times, and they were more interested in the outcomes of different scenarios than a strict algorithm. After that, there was a group activity where we had to build a tower with straws and tape – it was different, but I found it kind of annoying and unnecessary. The final round involved puzzles and technical interviews. Surprisingly, no actual technical questions were asked up to that point. Instead, I was asked about optimizing Google Search and Maps or adding new features. It's tough to come up with ideas on the spot, as Google likely already considered most optimizations. The same goes for the lift problem; real-world applications usually use optimal algorithms. Ultimately, I think the interview experience heavily depends on the interviewers; some might ask technical questions, while others don't. Some of my friends did get asked about data structures like linked lists and arrays.

The first step was a phone chat with the marketing manager, mostly about my past work and general outlook. After that, I went to their office for a meeting with the head of marketing and the head of sales. We talked about my attitude and experience, and they really dug into my personality and life outside work. It made me feel comfortable being open and honest. They must have liked what they heard because they offered me the job.

HR called me and briefed me about the company and the selection process. The process involved an offline technical test, followed by an offline assignment. Then, there was an F2F technical round with a panel, and finally, a telephonic technical discussion.

The interview process was quite lengthy, involving numerous rounds that spanned nearly a full day. In total, there were about 7 to 8 stages. These included checks on communication skills, a behavioral assessment, a technical interview, and a final meeting with the VP of Engineering.