You can very easily apply online, e.g., through LinkedIn. The response is quick.
Firstly, you'll talk with the recruiter, which is a rather usual talk about your past experience, the company's style, some common ways of working in the company, and your expectations.
The next round is the Coderbyte challenge with easy/medium algorithm questions and a simple React one. This one doesn't require a lot of preparation, despite you getting a huge email with a way to prepare for it.
After that, there was an application debugging session. The application is pretty simple, a kind of media player with transcription. However, the way it is written is not that straightforward: the folder structure is unclear with many index files containing logic, some overcomplicated usage of styled-component, very specific libraries, etc. Also, you will get a link to CodeSandbox and not the repo to work on. It took me around 5 minutes to make the environment editable for me. I have never used CodeSandbox for debugging purposes and, to be honest, it's far away from a good environment for that. For future applicants, I would recommend using a separate big monitor to feel more comfortable; it was hard to do on a small-screen laptop.
As a result, I wasn't able to build a proper map between the code and the application's view, and in the end, I fixed less than half of the bugs.
Also, I didn't find a flow with the interviewer, and we didn't have a nice cooperation during the interview.
Add a button using React that does some action.
The following metrics were computed from 6 interview experiences for the Apollo.io Senior Frontend Engineer role in Poland.
Apollo.io's interview process for their Senior Frontend Engineer roles in Poland is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having very good feelings for Apollo.io's Senior Frontend Engineer interview process in Poland.