Taro Logo

Frontend Developer Interview Experience - Warsaw, Masovian Voivodeship

April 1, 2025
Neutral ExperienceNo Offer

Process

  1. Intro interview - This was good. It covered general information, a couple of CV-related questions, and that was it.

  2. Tech theory with HR - This lasted around 15 minutes and involved generic checklist questions. It was for a React-related middle position, so questions focused on React (What is Reconciliation, Micro vs. Macrotasks in the event loop, what is the DOM tree). I passed this.

  3. Tech interview with live coding:

    • Typescript first: This was a 1-hour task involving fetching data from a source. Some information and starter boilerplate were prepared. Essentially, I needed to implement loading state, data state management, fetching with error handling (the interviewer disliked try-catch, but it was mentioned as helpful for others), and TS types. If time permitted, I was expected to discuss optimization or write unit tests.
    • I managed to complete the task, and it worked. However, I received a denial later.

Exact feedback: "It was clear that you were thoughtfully approaching the task, though it seemed nerves may have impacted your performance on the day. While the solution wasn't completed within the timeline (which it was), we did notice your attempt to apply structure and logic to your work. There were some areas—such as type management (I did lose some time with generic types because of immense stress) and loading state (I don't recall, it was working) handling—where we think further practice and refinement would be valuable."

After this, if I had passed, there would have been two more interviews: team-fit and bar-raiser. Only the team-fit interview is clear, as hiring is not for a specific project but for assignment to a team. The bar-raiser role is perceived as corporate "uselessness" everywhere.

Overall, for me, the time constraints were too tight. I tend to overthink tasks and problems, which caused a loss of focus.

I consider myself lucky not to have joined there, especially given the company's current reputation.

Questions

Micro vs. macro tasks in the event loop: how they work, explained briefly.

Was this helpful?

Interview Statistics

The following metrics were computed from 1 interview experience for the Revolut Frontend Developer role in Warsaw, Masovian Voivodeship.

Success Rate

0%
Pass Rate

Revolut's interview process for their Frontend Developer roles in Warsaw, Masovian Voivodeship is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive0%
Neutral100%
Negative0%

Candidates reported having mixed feelings for Revolut's Frontend Developer interview process in Warsaw, Masovian Voivodeship.

Revolut Work Experiences