Tip 1 : DSA is important, practice around 150+ questions minimum.
Tip 2 : For the front end, JS is a must! Learn the basics and how it works under the hood.
Tip 3 : Learn SOLID and Design patterns.
Tip 1 : Keep it short and simple. Specify your projects and/or experiences.
Tip 2 : Even naming your resume helps, instead of naming it "resume.pdf" name it like "____resume.pdf". It actually helps recruiters and I got positive feedback for this.
This was just a screening round to check my intention and communication skills. They just asked me why was I looking for a job change, and told me a little bit about the profile.
The call was scheduled around 14:00 pm.
Tip 1 : Keep the answers generic, do not bash or talk ill about your current company as it might create a bad impression.
Tip 2 : Some points that I presented were that I wanted to widen my domain, look for better opportunities, etc.
This round mainly consisted of front-end questions, including JS, React, HTML, CSS, etc.
It was conducted around 16:00.
All I had to do was present my screen and write some code to the problem statement.
I had to create a form with 4 fields (name, email, age, location), and two buttons, "next" and "prev".By default, the name field would have focus, and the "prev" button would be disabled. Clicking on next would focus on the next field (email) and so on. Once you are focused on the last form field (location), the next button would be disabled.
Step 1 : Create the UI, and make sure that you add the `type="button"` on the buttons in the form so that they don't actually submit the form.
Step 2 : Add refs to the inputs, and add onClick methods on the next and prev button.
Step 3 : Create an array fieldRefs, and add all the refs in the array, and a variable index, where clicking on next would increment it, and clicking on prev would decrement it. Then use the focus() method to focus on the respective field.
Step 4 : Now, clean your code and use React-ish way to write it using useEffect, and pass the index as a dependency.
The problem was with CSS selectors. They gave me an HTML snippet, and I had to use CSS selectors like attribute selectors, class selectors and :not pseudo class.
Understand the different CSS selectors, pseudo classes, and pseudo elements.
His round consisted of multiple easy DSA questions, some frontend questions, and one thought experiment related to design. Again, this round was conducted around 15:00 in the afternoon.


If N=5 and given string S is “rtoor”, the string can be rearranged as “rotor,” which is palindromic.
Create a new empty string.
Iterate over the letters of the string, and append a new character which is the original character incremented by n characters, but if it exceeds z, then loop over to a.
Return the new string.



insert(X): Inserts an element X in the data structure and returns true if the element was not present, and false otherwise.
remove(X): Removes the element X from the data structure, if present. Returns true if the element was present and false otherwise.
search(X): Search the element X in the data structure. Returns true if the element was present and false otherwise.
getRandom(): Return a random element present in the data structure.
Type 1: for insert(X) operation.
Type 2: for remove(X) operation.
Type 3: for search(X) operation.
Type 4: for getRandom() operation.
It is guaranteed that at least one element will be present in the data structure when getRandom() operation is performed.
Can you implement every operation such that it works in O(1) time?
Let's say that some of our clients are complaining that our website is really slow/crashing for them. What could be possible solutions and how would you identify the problems.
Tip 1 : Mention the common solutions like optimizing assets, and bundle size.
Tip 2 : Think out of the box, maybe the problem was faced by people of a certain geographic location, check your load balancers, pods, use CDN, etc.
Tip 3 : Provide some solutions, in case we can't figure out what's happening because we are not able to reproduce the problem, add some analytics and crashlytics like Sentry in the frontend, and enable alerting.
What happens behind the scene when you type a URL in your browser and until the webpage is fully loaded?
Tell everything that happens behind the scenes.
The URL is resolved using DNS.
The corresponding system is searched.
A GET request is sent to the system.
The server accesses the file system, preprocesses the response, and sends the response.
Once the response is received, the browser parses the HTML, creates and loads the DOM, creates and loads the CSSOM, and finally starts executing the JS.
Now, this is a very brief answer, and my actual answer included everything from TCP connection and handshake to caching in DNS, port 80.
You can research on it and be prepared accordingly.
This was a call with the CTO. We had a nice conversation about Rooter, how it came into existence, etc.
This was basically a call to see if I would fit in the team and a general personality check.
The best way to clear these rounds are to be well versed in leadership principles. They are really helpful and you can use them for any company's behavioural round.

Here's your problem of the day
Solving this problem will increase your chance to get selected in this company
What is recursion?