Tredence Interview Questions
& Process

Round 1 was a technical interview. They started by asking me to go through my resume. Then, I was asked some basic questions about database schema and tables, and also about the databases in my projects. After that, I was given medium SQL queries to solve, and the data was provided for me to paste into Excel. The round ended with the interviewer explaining the difference between a data engineer and a data scientist and asking me how ETL relates to that explanation. Round 2 was also a technical interview. I explained my projects, and the interviewer mostly asked questions about them. We also had a general conversation where he told me about himself, asked about me, and how I managed to find the time to build projects. Round 3 was an HR interview and only lasted for 10 minutes. The interviewer asked me why I was interested in tredance and what my goals are. He also told me about the on-boarding process.

The interview process was a mess. Scheduling was chaotic; one round got rescheduled after I was already in the meeting, then moved up. I agreed to a final round late in the evening, but the interviewer was rude and rushed. Then, they called saying they wanted to do a third round again. I already had another offer and my joining date was close. I asked to move it up, but they declined, asked about my offer, and couldn't match the compensation. By the time they wanted to interview me, I had already started a new job. It was a terrible experience due to poor communication, constant rescheduling, lack of professionalism, and not meeting salary expectations.

It seemed odd that a less experienced person was interviewing a more senior candidate for the same job. It makes you wonder how someone with less experience could properly evaluate a senior person. Also, they didn't even bother to tell me the outcome. They were in a big hurry to set up the interview, but then radio silence after it was done. This kind of unprofessionalism makes the company look bad and suggests bigger problems. Better to avoid.

We started with a technical round focusing on core Java and OOPs concepts like Inheritance, Polymorphism, Abstraction, and Encapsulation, plus SOLID principles, exception handling, Java 8+ features, and collections. Some coding questions were asked to test problem-solving and data structures. The next round dug into advanced Java, frameworks, and system design, covering Spring Boot, RESTful APIs, JPA/Hibernate, microservices, design patterns, scalability, performance, and database/system design for scalable solutions. The final technical round was about multithreading, performance tuning (JVM, GC, profiling), and basic cloud/DevOps stuff like AWS, Git, and Docker.