I applied through a recruiter. The process took 4 weeks. The process is long. The steps are not eliminatory, and you will reach the end even if you perform poorly on the previous one, which maximizes the waste of time in the event of rejection. In my case, they did not say which position I would be applied to, and my placement would be made during the process. Subjectivity reigns from step 2.

• Hunter: First, a recruiter reaches out to you on LinkedIn. There is an initial conversation about your experience, salary expectations, and the number of clients positively impacted by your deliverables.
• Technical Test: After step 1, you will receive a technical challenge with a 5-day deadline (which can be extended).

The development language is of the candidate's choice, and the problem may vary. The problem is well-described, with mathematical formulas to implement the solution explicitly provided. Without a doubt, this is the only stage of the process where subjectivity does not reign. It is the best stage in my opinion; however, it carries the least weight in the evaluation.- Architecture: You will participate in a process with 2 more engineers from the company. You will be presented with a problem and, together with them, you must present a solution (for me, it was an integration with a credit card operator via files). Here, the subjectivity of what is "right" or "wrong" begins, with "positive" or "negative" points.

As they inform you, the primary goal is not to arrive at a working solution, but rather to evaluate how you work in a team (in my case, I was evaluated negatively for deleting elements without informing the other participants, in order to resize them again on the Google Whiteboard).- Culture: You will be interviewed by an HR representative, who will ask you the same questions as in step 1, but in greater depth. There is an emphasis on your deliverables, leadership, decision-making, and how this impacted the client and how many were impacted.

As well as questions about inclusion and diversity, and what you have done to make your company more inclusive (even without having hiring power, I was marked down in this factor).- Pair: You will do a pair programming session and evolve the code you delivered in the technical challenge. Here is another point of subjectivity, since your code, the patterns used, and the application's resilience are none of them evaluated. Once again, they want to see how you work. The way I coded made the implementation they wanted 70% complete (literally it was adding an IF!), yet I was marked down for not stating my reasoning behind that IF.After all these stages (about 1 month), you will receive the result of your process.

You can reach step 5 even with negative points already from step 2. Stage 4 carries a heavy weight, and I believe this stage should be the first one, so the candidate's time would be spared. In my case, I had to develop an application from scratch (which takes time, regardless of your experience) and I was amazed when, in the feedback session, it was not even mentioned. Concepts of SOLID, resilience, and functional programming were not even taken into consideration. I missed a technical chat, a stage where I could deeply discuss the application of certain technologies.In summary, my process was evaluated subjectively, with negative feedback like "Didn't ask for help" or "completely removed a part of the solution from the board."

The salary is attractive, and it is up to each individual whether or not to subject themselves to this. I would only participate in another process if subjectivity were eliminated and the complete resolution of the problem, as well as good coding, carried a greater weight. And no, I don't think this is the company's theme, I just got unlucky (at least I hope so). Being rejected from processes is part of everyone's professional life, and what outraged me was my wasted time, reaching step 5 when by step 3 I was already out. Another point is that each stage does not have a specific weight; apparently, they are all equivalent, so it is impossible to know what really weighed in.

The HR people are attentive and caring. Good luck to you who will participate in the process, and I hope I helped.

What part of your code would you improve?