Digital OnUs Interview Questions
& Process

There were three interviews: a personal one, a technical one, and a live coding technical one. The first two interviews were pretty easy, with theoretical questions in the first technical interview. For the second interview, the interviewer never turned on their camera, and when I asked questions, they seemed absent or distracted, and their instructions weren't clear. When I asked for clarification, it seemed like the interviewer was doing something else or didn't understand what I was talking about. The interviewer confused the playground output with the terminal output and thought my result was wrong because they confused '/n' with me dividing by N. I don't know the level of the person who interviewed me. They sent me a pre-offer and really pushed me to sign it. During the process, the recruiter was very attentive and sent messages to my phone to speed things up. They kept me waiting for a few days just to reject me by email. Recruiters will insist on making you feel like you're already in, even without an offer in hand, which is risky since I had to quit my current job and give them a start date.

There were 4 interviews. The first was with HR to go over the details and expectations of the position. The second was an evaluation of technical skills and experience as a full stack developer with JavaScript and Python. The third was with a manager to clarify company doubts and offer useful feedback on my experience. The fourth was with the client and their technical team to validate my skills on the project stack and communicate expectations. Finally, my hiring was approved, followed by a process with the client and different company areas to help me adapt.

Going for a job interview always makes me a bit nervous. I try my best to prepare – I go over my resume, think about possible questions, and even practice answering them out loud. Even so, when the moment comes, my heart beats faster. When I'm called in, I try to smile confidently, even if I'm nervous inside. I sit down, make eye contact with the interviewer, and take a deep breath. As the questions come up, I start to relax. I talk about my career path, my experiences, and what I've learned along the way. I aim to be honest, but also to show my best side – without sounding too rehearsed. Sometimes, a question catches me off guard. My mind races to find the right answer, and I try not to show my anxiety on my face. Other times, the conversation flows so well that I almost forget I'm in an interview. When it ends, I'm always left with that strange feeling: did I do well? Did they like me? At the same time, I feel a sense of relief for having gone through it. Regardless of the outcome, each interview teaches me something new – about myself, about how I communicate, and about what I'm really looking for.

The interview process was a really nice and fast experience. First, a recruiter from talent acquisition reached out. We chatted about the role, my experience, and career aspirations before moving to the first technical interview. The company's technical interviewers are actually the people doing the work, so you can gauge their technical skill early on. By the third interview, I had a solid understanding of the company culture and the team's mindset. Initially, I wasn't sure about changing jobs, but after my final interview, I was very eager to join the company!