Nearform Software Engineer Interview Questions
& Process

So the interview involved an initial HR chat, followed by a 1-hour coding challenge where you had to use AI for most of it (5 out of 7 tasks), and then a final chat with the tech director. What's wild is how much they're leaning into AI now. In the coding part, you're basically supposed to use AI for almost everything, only doing a small bit yourself. But it felt like they cared more about how fast you could get stuff done with AI, not if the code was actually good. Being able to check and fix AI code didn't seem to matter as much as just churning out output quickly. This makes me wonder about how they handle code quality and if it's even maintainable long-term. Apparently, the project is for a big McKinsey client, and they're hiring a lot of devs in Italy, expecting some travel. This big hiring push and how they deliver work makes it seem like they're just trying to get bodies in seats fast, rather than building solid teams. It also makes you question why these roles aren't closer to the client, maybe it's just about saving money. Overall, it felt pretty impersonal and all about getting maximum output fast. There was barely any focus on the human side of engineering, teamwork, or actually caring about the craft. It felt like developers are expected to be AI operators, not real engineers. Cons: * Really prioritized speed over correctness * Barely any focus on code quality or thinking critically * Very delivery-focused approach * Didn't pay much attention to the human side of engineering

First, there was a relaxed chat with HR to go over your background and why you're interested. Then, a technical chat focusing on the main framework/language for the role (React.js, Node.js, or Python, depending on what you're going for); don't expect typical algorithm/data structure stuff like LeetCode, they'll ask about practical, everyday tasks. Finally, a meeting with the manager of the team you'd join, mainly to discuss the project and see if it's a good fit for your skills.

I was contacted by a recruiter. We had a brief 30-minute call discussing the company and my work history. After that, there was a technical screen which involved a coding question, lasting about 35-40 minutes. It had two parts: an easier first part and a harder second part. I went over the time limit on the second part. Even though I figured out the solution within 10 minutes after the interview ended and sent it to the interviewer, I wasn't successful. The reason given for my failure was not completing the task within the allocated time.