Ho presentato la mia candidatura online. Ho sostenuto un colloquio presso Ergatta nel mese di lug 2019
Colloquio
The interview process was very laid back and relaxed. I was allowed to attack the problem however I wanted, discussing what I was thinking as I went. I was free to google whatever syntax I needed as well.
The CTO asked probing questions with certain choices, and some even helped me alter my path.
It definitely felt like the "why" was more important than "what" I coded. Just as equally important was how I could discuss my thoughts and the problem with others.
I can only hope all future interviews are as open, welcoming, and even educational as this one was.
Domande di colloquio [1]
Domanda 1
"Why did you choose that code structure?"
"What do you think about this alternative? Why would it be better/worse?"
Ho presentato la mia candidatura tramite un'agenzia di reclutamento personale. La procedura ha richiesto 3 settimane. Ho sostenuto un colloquio presso Ergatta nel mese di set 2020
Colloquio
I had five separate interviews, three of which were behavioral and two technical. For the behavioral interviews I met with each of the cofounders Tom, Al, and Pras and we chatted about some of my past work and what I found intriging about Ergatta.
The first technical interview I had was with Pras, the CTO. It was a pair programming session where we refactored some code and wrote a few unit tests. It was simple and approachable and Pras was helpful rather than critical. I didn't feel amazing about my preformance but that's how it goes sometimes.
The second technical interview I had was with one of the Android Engineers. We didn't really dive much into code but talked more about system architecture and brainstormed how I'd write this or that sort of UI.
It took around 3 weeks from hearing about Ergatta to getting an offer. And I've loved it ever since.