I’ve got a phone screen for a frontend role at Uber in a week. The recruiter told me I’ll probably get one leetcode style question and one “implement x in JavaScript” type question.
Could anyone give me any more details on what to expect? How difficult is the leetcode question likely to be, and what kind of “x” am I likely to be asked to code in JS?
I know every interviewer is different but is there anything Uber as a company specifically looks for?
Thanks!
Want to see the real deal?
More inside scoop? View in App
More inside scoop? View in App
blind
SUPPORT
FOLLOW US
DOWNLOAD THE APP:
FOLLOWING
Industries
Job Groups
- Software Engineering
- Product Management
- Information Technology
- Data Science & Analytics
- Management Consulting
- Hardware Engineering
- Design
- Sales
- Security
- Investment Banking & Sell Side
- Marketing
- Private Equity & Buy Side
- Corporate Finance
- Supply Chain
- Business Development
- Human Resources
- Operations
- Legal
- Admin
- Customer Service
- Communications
Return to Office
Work From Home
COVID-19
Layoffs
Investments & Money
Work Visa
Housing
Referrals
Job Openings
Startups
Office Life
Mental Health
HR Issues
Blockchain & Crypto
Fitness & Nutrition
Travel
Health Care & Insurance
Tax
Hobbies & Entertainment
Working Parents
Food & Dining
IPO
Side Jobs
Show more
SUPPORT
FOLLOW US
DOWNLOAD THE APP:
comments
In hindsight maybe I should have held off until I was more confident.
I had to implement a few different functions. I couldn’t get one of them perfectly, and ran out of time on the last.
I started the problem by discussing what data structures I could use to form the core of the solution, with pros and cons, etc. The interviewer sounded impressed and the vibe was positive. However in hindsight that took up a lot of time that I could have spent on coding the solution.
The problem wasn’t terribly hard - I could have nailed it given 10-15 more minutes probably.
I think this is a problem I face a lot - if I spend extra time discussing details or talking about “what I’m thinking”, I seem to run out of time.
Or if I start with a brute force approach with the intent to iterate to something optimal, I run out of time.
Some interviewers say they really want to see what you’re thinking and how you tackle problems, but based on experience and anecdotes, I can’t help but feel getting the 100% optimal solution trumps everything else.