After spending the last few years juggling infra reliability and data engineering, I decided it was time for a change. The opportunity to work as a Frontend Engineer at Uber piqued my interest. I started my preparation process methodically—four months of coding, studying systems, and sleepless nights.

The first hurdle was refreshing my knowledge of frontend frameworks, particularly React. I devoted a week to diving deep into hooks, lifecycle methods, and state management—because let's be honest, the last time I wrote frontend code was during a hackathon in 2021. Armed with new insights, I practiced coding challenges on platforms like LeetCode, where my completion rate was dismally around 70%, often needing hints for problems tagged above 'medium.'

Interview day arrived and I faced a series of intense rounds with various engineers. The technical interview was particularly grueling; one moment welcomed a coding challenge on the spot, where I completely blanked on a fundamental algorithm. I ended up over-complicating a simple sorting task, which was almost my undoing. I spent a good five minutes feeling like I had failed, but managed to salvage it by walking through my thought process, allowing me to pivot just enough to gain some traction.

Finally, after a few weeks of back-and-forth, I received the offer from Uber. The compensation package topped six figures—a number that sounded far too good to be true. It was a relief and a high point just confirming that all those late nights and coffee-fueled coding sessions paid off. Sure, I had my share of turmoil and self-doubt, but in hindsight, it was all part of the journey. Who knew getting a frontend job would involve so much unraveling of my wiring!

Looking back, the mix of adversity and triumph was just what I needed to step into this exciting phase of my career. Can't wait to dive deep into Uber's tech stack and maybe bump into an interesting new problem every day—which I hear sometimes requires a coffee or two for solving.

Focus on the fundamentals of algorithms and data structures. Make sure you can talk through your thought process even when things get tough., Practice coding challenges under timed conditions. This will help simulate interview pressure., Deepen your knowledge of the specific frameworks required for the job. React was a priority for me, but make sure to understand the entire ecosystem., Don't ignore system design. Many senior roles require an understanding of architecture, and sometimes, the question will catch you off-guard., Stay calm during interviews. If you hit a wall, take a moment to breathe, and try to deconstruct the problem out loud.