Glassdoor users rated their interview experience at rag & bone as 100% positive with a difficulty rating score of 3 out of 5 (where 5 is the highest level of difficulty). Candidates interviewing for Frontend Developer and Business Analyst rated their interviews as the hardest, whereas interviews for Frontend Developer and Business Analyst roles were rated as the easiest.
The hiring process at rag & bone takes an average of 7 days when considering 2 user submitted interviews across all job titles. Candidates applying for Business Analyst had the quickest hiring process (on average 7 days), whereas Business Analyst roles had the slowest hiring process (on average 7 days).
I met with an outside talent acquisition manager, then met with the hiring manager. After that, they required an on site meeting with 4 of the team members which consisted of 2 hours in office. I applied in Oct and never heard anything back regarding my application status, even after following up with their HR twice. A bit of a disappointment but a true reflection of the company's morals, which has been also stated in their reviews. No bonus offered either.
Not too bad. Basic in person interview and then call with regional manager. Overall pretty easy and straightforward. Understand KPI metrics. Look presentable. Say you want to be in retail longterm- looking for retention
I applied through university. The process took 1 week. I interviewed at rag & bone (Gurgaon, Haryana) in Jul 2022
Interview
How would you design a simple online banking dashboard or insurance portal?"I’d use ReactJS on the frontend and ASP.NET Core Web API in the backend. The backend talks to SQL Server using C#. APIs would be used for login, policy listing, and application. I’d structure the backend with service and controller layers, and add basic logging, error handling, and token-based auth."
Interview questions [1]
Question 1
I’d use ReactJS on the frontend and ASP.NET Core Web API in the backend. The backend talks to SQL Server using C#. APIs would be used for login, policy listing, and application. I’d structure the backend with service and controller layers, and add basic logging, error handling, and token-based auth."