An exemplary recruitment process:
- Well-organized / structured: 1. Call with a recruiter; 2. Offline coding exercise; 3. 3 30-min slots (within 1.5 hour block) of interviews with engineering team members.
- All candidates feel welcome, also technology/language-agnostic OOP-oriented engineers: no hard requirement to have golang background.
- Friendly, pressure-free environment: the candidate is encouraged to learn golang at their own pace before attempting the exercise. Talent acquisition team keep in touch to enquire about the progress and see if the candidate is still interested in the role but without creating an artificial pressure or enforcing strict timelines.
- Relevant to the role: As a coding exercise, the candidate is asked to develop an http client library to integrate with the flagship product of Form3 - a few sample endpoints of the payment API. As part of the interview with the engineering team, the candidate has an opportunity to understand the Form3 architecture, design a real-life distributed system, debug a simulated production issue in the Form3 systems as a role-playing game.
- Prompt post-interview feedback (48 hours).
Perguntas de entrevista [3]
Pergunta 1
Coding exercise in golang: http client library using Form3 api
Debugging/ investigating a live production issue in Form3 systems in the form of a role-playing game. How to approach setting up a CI/CD pipeline in a startup vs a bigger company? Questions about the technologies mentioned in the CV.
Candidatei-me por meio de recrutador(a). O processo levou 3 semanas. Fui entrevistado pela Form3 (Buenos Aires) em nov. de 2022
Entrevista
It was a pretty straightforward process. One screening interview, a take home exercise, and a technical interview. The technical interview has different levels of complexity, from discussing the exercise implementation to infrastructure decisions.
Candidatei-me por meio de recrutador(a). O processo levou 3 semanas. Fui entrevistado pela Form3 (Londres, Inglaterra) em jun. de 2022
Entrevista
I had a very good meeting during screening call. The guy even shared a tips for the home exercise. I had to spent 5 days to write the code with developing the client library, unit testing, integration testing, makefile, setting dockerfile and so on.
After 4 days, i received the feedback and its really annoying clarification from the panels (who ever you are).
It seems they are Gen-Y(who always complain and not really look into the implementation code). The comments from them are only focus on configuration, not able to run the code(even i tried download it from different machine and run it without an issue). Cry baby !!
i felt like the whole comments is just not relevant. You guys need to be more matured and maybe ask more senior guys to involve in the process.
To management : you guys really need to see all of the comments from the bad response. You are having a DIVA type of developers review our code
