Full Stack Developer applicants have rated the interview process at WalkMe with 3.5 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 67% positive. To compare, the company-average is 53.8% positive. This is according to Glassdoor user ratings.
Candidates applying for Full Stack Developer roles take an average of 7 days to get hired, when considering 6 user submitted interviews for this role. To compare, the hiring process at WalkMe overall takes an average of 22 days.
Common stages of the interview process at WalkMe as a Full Stack Developer according to 6 Glassdoor interviews include:
One on one interview: 38%
Presentation: 25%
Group panel interview: 13%
Skills test: 13%
Phone interview: 13%
Here are the most commonly searched roles for interview reports -
I applied through an employee referral. The process took 1 week. I interviewed at WalkMe in Jan 2025
Interview
Group leader interview:
Design level url shortener.
Asked about what I did in the previous company.
Showed me the group repos responsibility.
Asked about how much salary do i want.
The process was pleasant. We started with an hour-long technical interview, followed by a homework assignment. During the interview, two people asked questions and you had to write code and answer their questions. Then there was a two-hour homework assignment.
I applied online. I interviewed at WalkMe in Nov 2024
Interview
A Disconcerting Interview Experience at WalkMe!
My recent interview journey at WalkMe proved to be rather enlightening, though not in the manner initially anticipated. The process commenced with a technical assessment centered on implementing a basic Todo list application with checkbox functionality. While I successfully completed the task with promptness and efficiency, a minor oversight regarding state management occurred—specifically, handling the 'isDone' status without utilizing useState. Though I promptly identified and rectified this error during the interview, the feedback received cited a purported lack of understanding regarding React's lifecycle mechanisms.
The subsequent rejection message, delivered with minimal elaboration, appeared to fixate disproportionately on this single instance rather than evaluating my comprehensive skill set. This experience, while disappointing, offered valuable insights into the organization's culture and decision-making processes.
What particularly struck me was the seeming disconnect between the company's external reputation and the actual interview experience. The technical evaluation appeared to emphasize rigid adherence to specific implementation patterns over problem-solving capabilities and adaptability.