EBANX Software Engineer Interview Questions
& Process

It was a very human process divided into 4 stages: contact with the recruiter, then an asynchronous technical challenge, after correction of the challenge we moved on to a technical interview and finally a conversation with the area Manager. The whole process has some company professional involved and lasts an average of 5 weeks. The last conversation is very important to be sure about what you aim for your career.

The EBANX hiring process is really well-defined. It starts with a screening, then a practical test, followed by an interview with a recruiter, then a technical interview, and finally a chat with the managers. I made it through every step, but in the end, they said my profile was a better fit for an intermediate (pleno) level, and there were no openings for that. The recruitment team was fast and professional, getting back to me quickly and keeping me updated throughout. My only suggestion would be to maybe not require both the practical test and the technical interview. Doing both can be super tiring, especially if you're interviewing with other companies too, and then you have this long theoretical discussion. Offering a choice between the practical test and the technical interview could make things smoother and save everyone time, plus avoid silly mistakes from being exhausted. Making it more flexible could lead to a better and more productive interview experience for everyone.

The selection process stages are very clear and simple. I applied through the company website, and soon after received an email from HR detailing the stages: Resume Analysis, Technical Test, HR Interview, Technical Interview, and Manager Interview. The technical test is quite basic, so depending on your seniority, it's worth putting in some effort because it will be discussed in the technical interview. There's a URL for automated tests of your project, and if you pass, they'll schedule the interviews. The HR interview is straightforward, just to align expectations and salary requirements. I made it clear the technologies I work with and that I'm willing to work with PHP, which is the company's core. In the technical interview, I found it weak. The interviewer was a Manager who admitted he hadn't coded in a while. So, we didn't go into much detail, and after I mentioned I hadn't used Java, he dismissed me without further questions. The interview was very brief for a technical interview standard. Basic questions were asked. It was strange because, from the beginning, nowhere in the job description was Java mandatory. On the contrary, it encouraged using any programming language. And in the HR interview, I also informed them about my qualifications, and they still scheduled the technical interview. I felt it was a waste of time. If they wanted a Java developer, they should have stated it in the job description. Simple.