Wrike logo

Wrike Frontend Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 5 interview experiences · FREE TO READ

2.4 Rounds average
Average Typical difficulty
60% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Wrike.

Showing 3 of 5
Wrike logo
Wrike

Senior Front End Developer

Engineering · nearly a year ago

Senior Average Negative experience No offer 2 rounds
Interview process
Recruiter call Technical screen
Interview formats
Coding Behavioral

I applied for a role that was advertised as a Senior Frontend Engineer. In my initial chats with HR, I talked about my salary expectations, but then they said the budget was actually lower and that it was more of a mid-senior type of role. I stuck with it though because I was still interested. The technical interview itself was pretty good and the interviewers were professional. But the live coding part felt more like something for a junior-to-mid level role, not senior. When I asked, the interviewers confirmed it was mid-level and that the mix-up came from HR, not the tech team. It was clear then that the job wasn't what was advertised, so I decided to stop. The interviewers were nice and communicative, but the whole thing was a letdown because the job level didn't match what they said at first. It would be better if they were clearer about the role scope and seniority from the beginning so people know if it's a good fit and don't waste time.

Confirmed questions1 question
  • Can you build a to-do application using React?
Wrike logo
Wrike

Front End Developer

Engineering · a year ago

Entry Average Positive experience No offer 3 rounds
Interview process
Recruiter call Technical screen Phone screen Background check
Interview formats
Technical Behavioral

The process wasn't too long. All interviews were in Russian, but they did check my English level. The tech part was interesting, but the tech folks weren't very friendly. I also didn't get any feedback, just the usual email saying 'we did not select you.' Personally, I think it would be better to get at least a little comment on what was wrong or good.

Confirmed questions1 question
  • Can you describe methods for continuous data exchange between a client and a server?
Wrike logo
Wrike

Frontend Developer

Engineering · more than a year ago

Mid Average Positive experience Accept offer 2 rounds
Interview process
Technical screen Recruiter call
Interview formats
Technical Behavioral

First up was a chat with some engineers, where they hit me with technical stuff and some soft skill questions too. Took a good couple of hours. After that, I had a quick call with an HR person.

Confirmed questions2 questions
  • What technical questions did they ask for the Frontend positions, mostly about the browser and how do applications written in js work there?
  • Additionally, were there any questions about architecture, design principles, and patterns?

Wrike Frontend Engineer Interview Questions

Quoted word for word from Wrike interview reports.

Can you write a function that solves a simple problem with O(n) time complexity?

Read reports

Can you describe methods for continuous data exchange between a client and a server?

Read reports

What technical questions did they ask for the Frontend positions, mostly about the browser and how do applications written in js work there?

Read report

Additionally, were there any questions about architecture, design principles, and patterns?

Read report

Formats, difficulty and experience

Across all 5 Wrike interview reports.

Interview formats

Behavioral 45.5%
Technical 36.4%
Coding 18.2%

Interview difficulty

Easy 0%
Average 100%
Difficult 0%

Candidate experience

Positive 60%
Negative 40%