Nothing Something Interview Questions
& Process

You start by applying online, through a referral, or maybe even walking in. Then, an HR person checks your resume for all the important stuff like skills and experience. They might give you a quick call to confirm if you're available, what you're looking for salary-wise, and how soon you can join. If it's a tech job, there might be an online test with questions on aptitude, coding, or technical topics. For other companies, it could be case studies or personality tests. Next up are the technical interviews, usually one or two rounds. Here they'll quiz you on your programming, problem-solving, database skills, system design, or specific knowledge for the role, like networking. If it's not a tech role, they'll ask about your subject knowledge, tools you know, and projects. Sometimes there's a managerial or case study round. This is to see how you think and handle problems. A manager might also want to see if you're a good fit for the team and how you deal with challenges. For consulting or data jobs, you might get a case study. Finally, there's the HR interview. This is all about your personality, how you communicate, if you'd fit into the company culture, and what motivates you. They'll ask about you, why you want this job, your strengths and weaknesses, salary expectations, and if you're okay with relocating or working shifts. If everything goes well, you get an offer letter with all the details. Then comes the background check and submitting your documents before you start.

They asked some questions about my resume, then some behavioral questions, and also some managerial and technical questions. They asked some questions about my resume, then some behavioral questions, and also some managerial and technical questions.

First off, the recruiting team's welcome was warm and friendly. They made a relaxed and friendly vibe that helped ease any initial tension. They quickly put me at ease and walked me through how the interview would go, which cleared up any uncertainty I might have had. The interview itself flowed logically, with a mix of technical and behavioral questions. The interviewers were really knowledgeable and skilled in their field, making for a stimulating and constructive discussion. They gave me the chance to talk in detail about my past experience and technical skills, letting me highlight my Data Engineer abilities.

I had a 45-minute Skype interview that covered behavioral questions, C++ and Python specifics like threading and optimization, and basic C++ OOP. After that, there was another 45-minute technical Skype interview with a lead software engineer, which was similar but focused more on debugging and build tools, plus some behavioral questions. The final stage was an onsite interview that lasted 5 hours. The first onsite round was with a software engineer, discussing my background and debugging methods, specifically how I'd debug software. I only knew GDB and backtracing, and it felt like they were looking for a more professional approach I wasn't familiar with. The second onsite round was with another software engineer and involved 2 coding problems: finding the longest sublist in a cyclic list and counting character occurrences in a string alphabetically. I explained using a map for the character count, but struggled with displaying it. For the cyclic list, my initial idea of using nodes and longest increasing subsequence was rejected. The third onsite round was with a principal software engineer and included advanced questions on C++, Python, robotics motion planning, malloc vs new, deadlock, forward vs move, GIL, memory management, and exception handling.