I applied online. The process took 3 months.

Phase 1: Interview. This interview was online with a member of the People team. They asked about my professional background and my salary expectations.

Phase 2: The coding test. The test consists of developing a program following functional and non-functional requirements. The test is of medium to easy difficulty. If you think that just by completing all the requirements of the test you would pass to the next phase, you are mistaken. Fulfilling these requirements described in the test is the bare minimum necessary. Precisely because it is not so difficult, the code must be of the highest quality, extensible, and testable. I could do it in any language. I was already preparing to carry out the test in Clojure even though I had never programmed in this language. Ever since I had sent my CV, I had been studying and practicing. Upon receiving the test, I thought that for that level of difficulty presented to me, I could already develop the test in Clojure. It was a risk that I chose to take aiming to demonstrate my learning capacity. In the documentation written by me, there were instructions on how to run my code, justifications for the choices I made to solve the problem, and I also explained what my testing strategy was. In addition to unit tests, I did very strong integration tests. After submitting it, I waited a week and received the email saying that I was approved for the next phase.

Phase 3.1: Whiteboard. The third phase is composed of three interviews. The first one for me was a whiteboard on software architecture. This by far was the most difficult phase. I sweated cold. This phase is with you and 2 other engineers. They give you a hypothetical problem and ask how you would design the architecture of the system that would solve the problem.

Phase 3.2: Pair Programming. I was informed that in this phase I would do pair programming with two other engineers. The People representative told me that it could be that they would extend the test that I delivered in the second phase, or that it could also be a brand new development from scratch. Who would decide this would be one of the engineers who were evaluating me. But when the moment arrived, it was revealed to me that they would extend my test. You have time to do the proposed challenge. In my case, it was adding more functionalities to the delivered test. I managed to finish with a lot of time to spare. This is not necessarily good because they say that they do not evaluate by speed but rather how you develop, but this still caught their attention because I did indeed finish with a lot of time left over.

Phase 3.3: Culture Interview. This is a steroid version of the Phase 1 interview. They ask questions about your career and feedback that you have received.

After these three parts of the third phase, I was told that these 6 people (2 per interview) who had contact with me in this phase would meet and debate whether or not it made sense for me to join the team. I waited for 4 business days and received the message that I was approved and that I was in the final phase.

Phase 4: Conversation with the Managers. The chat was very relaxed. It was not an interview. It was a chat about what the team they lead is like, what the challenges are, and what the goals of the area are. In this conversation, they also revealed to me that the position was for a team with members from other countries, so they also asked me how my English was. On the same day, the People representative sent me an email asking if she could call me. I answered yes, and upon answering, she gave me very positive feedback on all the phases and made me the offer.

Is diversity at work important? What is the deployment process like in my company? About past experiences in my career. Do you feel comfortable in a team where no one speaks Portuguese and they only communicate in English?