KMS Technology Interview Questions
& Process

I went through the first interview round for the Tester job at KMS. It was with a recruiter and mostly behavioral questions. They asked me to talk about myself, my studies, and why I applied. Then, they had me discuss my strengths like attention to detail and problem-solving, and weaknesses, mentioning how I can be too detail-oriented but I'm working on time management. The recruiter was nice and made me feel comfortable. It seemed like they wanted to see my motivation, how I communicate, and if I'd fit the company culture. No tech questions were asked. Waiting to hear back for the next round, which I expect will be more technical.

The hiring manager I spoke with was super nice and open-minded, which made me feel really comfortable. We had a great chat about the company's culture, values, and where they're headed. They were happy to answer all my questions thoroughly, making me feel like they really cared about me as a candidate. By the end, I was feeling really good and hopeful about the role. I learned a lot about the company's current projects and the chances I'd have to grow professionally. It was good to hear about possible career paths and how the company helps its employees develop. This whole experience has me excited about the possibility of joining the team and being part of such a supportive place to work.

The interview process was pretty standard. Started with an HR call, which was followed by a technical interview and a HackerRank test. The HR person was really great, super friendly and engaged. Then I had interviews with two senior developers. One of them was quite tough, kept pushing me on questions that I wasn't sure they even knew the answer to. They asked about arrow functions, and when I couldn't immediately recall the specifics, they asked for time to Google it. The other developer seemed more knowledgeable but was also pretty aggressive and made some sarcastic remarks. They brought up their smooth webpack upgrades, contrasting it with my struggles, which I attributed to project complexity and dependency issues, using font-icon and bootstrap as an example of the tangled mess. I was asked about a tough technical challenge, and I described optimizing a JavaScript tree-like object. While I explained how documentation allows for multiple solutions and that the system designer can usually pinpoint issues faster, it didn't seem to land well. The focus felt very much on finding someone who could solve any problem, regardless of team coordination or process. When I inquired about the tech stack and tools, the response was vague, just mentioning Java, JavaScript, PHP, etc., which made me wonder if they were uninformed or just unwilling to share details. Overall, I'm uncertain about the fit.

So the interview involved meeting a bunch of people from the KMS team, including some of the big bosses and folks I wouldn't normally be working with. It was pretty cool to chat with the execs and get a feel for what KMS is all about, their goals, and where they're headed. I also got to hang out with other KMS team members and hear about their jobs, why they like it there, and how my role would fit in. It definitely felt like a place where everyone works together and I could do well.