Uber's interview process can be confusing. It starts with a take-home assignment. If you clear this, the next step should be an on-site interview with a specific team. However, the recruiter ultimately decides your next steps.

In my case, the recruiter contacted me a week later, stating my profile wasn't suitable for a backend role. When I mentioned I am a backend engineer, she advised me to update my resume to reflect this. I revised my resume, adding four words and changing my title to "Backend Engineer." Suddenly, this was a profile that managers liked, or so I was told. I suspect my resume wasn't initially shown to an engineering manager and only was after I added the word "backend." Subsequently, I had an on-site interview, which included:

• Two technical rounds
• One design round
• One "bar raiser" round
• One manager round

The design round seemed to concentrate heavily on databases, specifically within NoSQL, and their trade-offs.

Overall, the engineers appeared decent. However, the recruiters were quite inconsiderate, making rude remarks such as, "Your profile is a junior profile; we don't consider internships" (despite my eight years of full-time experience and no internship experience), and "We only want backend engineers." Essentially, they look for keywords in your resume that are highlighted and bolded. If these keywords are absent, they proceed as they see fit.

LeetCode for technical rounds should be enough.

For design, definitely concentrate on DB. They go into a lot of details.