This content originally appeared on DEV Community and was authored by Prashant Yadav
Visit practice.learnersbucket.com If you are preparing for your JavaScript interview. Practice JS and System design questions and ace your interview. No authentication required.
On June 7 a recruiter contacted me through LinkedIn saying that she has an amazing opportunity for Senior Frontend Role at Razorpay and would you be interested in Interviewing.
Fast forward to July 7th I got my offer letter from Razorpay. It was really great Interviewing at Razorpay because their hiring was focused on overall aspects and not simply on Problem Solving (DSA).
They didn’t have a DSA round, at least for the frontend role.
In total there were 4 rounds taken.
1. JavaScript platform round. (1 panelist) – (1 hour).
In this round, I was asked 3 questions based on JavaScript’s core concepts.
I solved the first two without any hustle as I had already practiced and solved them before.
In the third one, I got stuck at one point (due to time constraints and pressure) but in the end, I was able to pull it out.
2. Machine Coding Round. (2 panelists) – (1.5 – 2 hours).
In this round, there were two panelists.
I was asked to create a Toast component in any framework of my choice. The question came with two options.
- Must have feature.
- Nice to have feature.
Must have feature.
- Toast should be triggered on a button click.
- At a time three Toast should be visible on the screen, the moment fourth comes first should be discarded.
- It should have a close button.
Nice to have features.
- Different variations.
- Auto-close after a certain time.
- Globally accessible through out the app.
I was provided an online platform to code, They asked if I want to use Redux or not and I got ahead with redux.
Libraries were preloaded, but you had to code everything from the scratch. If required you can use google.
I implemented both the features without googling. (Practice paid off.)
The two panelists had different roles to play during the interview.
- Who had kept asking cross-questions on the approach I was following.
- He was silently observing the way I was coding, Is it modular, scalable, extendable, or not.
3. System design round (1 panelist) – (2.5 hours)
In this round, I was asked to create a blogging platform like a medium from the scratch but for Razorpay’s ecosystem.
Features
- Restricted posts based on user’s role.
- Draft and Publish state.
- Managing session.
- The website should work independently as well as should integratable, based on Razor’s authentication. How would I manage the cookie-based authentication on subdomains?. If hosted on a different domain It should force login.
- Micro-Frontend architecture, widget approach.
- Optimization, SEO, AMP.
It was one of the longest rounds of interviews I have given.
Explained lots of different approaches I would follow, the major one was the use of WYSWIG editor
How would I render the HTML in React, security, cross-site scripting attack?
Server-side or client-side rendering, their tradeoffs, what about the hybrid approach?.
Lots of cross-questions on my approach.
How would I manage the authentication and authorization?.
It was a great round, I learned a lot from it, In the end, cleared it.
One week before I had read the engineer blogs of Canva, Uber, & Slack on how do they optimize large-scale web apps. These really helped me think out of the box and put my points with increased confidence.
4. Hiring Manager (1 panelist) – (1 hour).
It was with the VP or LEAD, I don’t remember exactly, but it was a simple and straightforward round based on previous work experience, what I looking for in the current role, etc.
All and all it was really quite an experience Interviewing at Razorpay.
This content originally appeared on DEV Community and was authored by Prashant Yadav
Prashant Yadav | Sciencx (2021-10-15T19:46:21+00:00) Razorpay frontend interview experience. Retrieved from https://www.scien.cx/2021/10/15/razorpay-frontend-interview-experience/
Please log in to upload a file.
There are no updates yet.
Click the Upload button above to add an update.