English - LATAM Candidate Prep Materials

Download as pdf or txt
Download as pdf or txt
You are on page 1of 25

Interview Process

2023

Format & Prep


Congrats on reaching the team interview stage!
Our team can’t wait to meet you. Here you will
find everything you need to know about our
interview format, how to prepare, and why Uber
is a great place to work for engineers.
Let’s go!
01 Why Uber
02 Interview Modules + Example Questions
03 Tips & Tricks
04 Meet our Engineers
05 Interview Checklist & Resources
Why Uber
Impactful Work

Uber has changed the world and we plan on continuing to do so. Join us on a mission to
ignite opportunity by setting the world in motion. Your day to day work will have an
impact on your immediate team, domain, Uber overall, and an impact on the world.

Uber Scale

With almost 100 million monthly users, operating in 10k+ cities, and 16 million trips per
day, our scale is unparalleled and our scope is global.

Growth & Learnings Opportunities

Our engineering leaders are dedicated to helping their teams learn and grow. By
providing our engineers with the right opportunities, scope of work, and interesting
challenges, learning is inevitable.

Complex technical challenges

There are so many parts of our product with unique technical challenges, especially on
the scale that we operate on. Every day you can expect to be challenged with complex
problems to solve with a team that supports you.
Our Scale

93MMonthly active riders


10K+
Cities that we operate in globally

16M
Uber trips happen each day
$21.9B
Gross bookings as of Q2 2021
Interview Process
*all interviews are conducted in English

Recruiter Phone Business


Screen Interview
Your initial call with a Full interview day(s)
recruiter to learn about focusing on a variety of
the role and share your modules and
experiences competencies

Business Phone Hiring Decision


Screen Our team then makes a
60 minute coding hiring decision based
assessment with one on performance in
of our engineers interview rounds.
Recruiter shares
outcome
Business Phone Screen
After your call with the recruiter, you will complete a 1-hour live coding interview with one
of our engineers. We will send a CodeSignal Link that will allow you to share your screen
with the interviewer. See the interview breakdown below.

Introduction (5 minutes) Coding (40 - 50 Minutes)


Be prepared to introduce yourself Questions (5-10 minutes)
Come to a working code and design within
and some of your accomplishments Ask any questions you may have! We
~40 minutes:
and responsibilities. This is a good recommend asking about the team
● Ask clarifying questions
time to meet the interviewer as well projects, life of an engineer, your
● Verbalize all your thoughts
and learn about what they do at Uber. interviewers experience at Uber, the
● Propose a solution with your
team culture - or anything else that
interviewer first
you are curious about. You may
● Then proceed to your
prepare some questions ahead of
implementation
time.
Preparing for your coding assessment
Coding skills to focus on Practice Resources Problem Solving Tips
General problem-solving skills: in the Even good candidates get tripped - Every question may have multiple
live coding exercise, you will be up because they are rusty or solutions; focus on solving the
asked to solve 1 technical exercises unfamiliar with this style of interview problem first and then discuss the
& write functional code to question. If you do a couple of tradeoff between these
implement the solution problems with mixed difficulty, you'll approaches.
be prepared. - Think about test cases for your
For Big-Tech-Like interviews: code including edge cases or error
- Common data structures and LeetCode cases.
algorithms (hash tables, trees, CodeSignal - If you get stuck or need
stacks) Hackerrank clarifications, don't be afraid to ask!
- Runtime analysis (Big-O) Top 10 Algorithms We are solving these problems
Vídeo Mock interview together.
Por Códigos e Entrevistas: Pessoas - One technique to write a better
engenheiras e o processo seletivo solution is to consider what you
da Uber | Uber (in Portuguese) would catch if you were code
Meetup Coding Interview reviewing your code.
Meetup Design & Architecture
Interview Code Review
Business Interview
If you pass the business phone screen, your sourcer will let you know that we are moving forward with
the final business interview and connect you with a recruiter who will be your point of contact moving
forward. In the business interview, we evaluate multiple competencies seen below. This can be done
all in one day, or spread out, depending on your preference.

Coding: Design & Architecture: Behavioral:


Algorithms & Data Structures Previously Solved Problem Impact - Efficiency & Quality
Depth in Chosen Technology New Problem Collaboration & Leadership
Business Interview: Interview breakdown by level
L4: Software Engineer II Some notes:
● 60 min: Coding: Algorithms & Data Structures - Work with your recruiter
● 60 min: Coding :Depth in Specialization to determine which level
● 60 min: Design & Architecture: New Problem you are interviewing for
● 60 min: Collaboration & Leadership
- Level is ultimately
L5A: Sr. Software Engineer determined by the panel
● 60 min: Coding: Algorithms & Data Structures
after the interviews are
● 60 min: Coding: Depth in Specialization
● 60 min: Design & Architecture: New Problem
completed
● 75 min: Collaboration & Leadership (45 min), Design & Architecture: Previously Solved Problem - Each process is slightly
(30 min) different; review your
L5B: Staff Engineer appropriate interview
● 60 min: Coding: Algorithms & Data Structures breakdown and study
● 60 min: Coding: Depth in Specialization accordingly
● 60 min: Design & Architecture: New Problem
● 60 min: Collaboration & Leadership
● 60 min: Impact - Efficiency & Quality (30 min), Design & Architecture: Previously Solved Problem
(30 min)
Coding Modules
Algorithms & Data Structures
This interview assesses problem-solving abilities via writing code that
reflects the correct use of algorithms and data structures as well as
being idiomatic in choice of language. The problems are generic
and not technical domain-specific. You are expected to ensure that
you create testable code and have correctly identified what you
would test.

Depth in Chosen Technology


This interview assesses depth in your chosen area of
specialization/technical depth via writing code that solves a problem
that would be similar to what you would do in the job.

Specializations include: Backend, Frontend, Android, iOS, Data,


Machine Learning/AI, Security, SRE
Leetcode Tips + Practice Questions
Leetcode tips Practice Questions
● Do a range of difficulty levels. Try different types ● Mini-Max Sum: asks the interviewer to find the
of problems at easy, and then see how the same maximum and minimum sum among an array of
type of problem got harder at medium, and then given numbers..
at hard ● Organizing Containers of Balls: tests the
● Try to cover a variety of different types of candidate’s knowledge of 2D arrays, sorting and
problems - e.g. graph traversal, recursion, dynamic iteration.
programming etc. ● Build a Palindrome: tests candidate’s knowledge
● Revisit your solutions and make notes - try to of strings and dynamic programming, as well as
understand what is the fundamental their ability to write clean, optimized code.
approach to use ● Subarray Division: Based on a technique used for
● Try different solutions to understand how the searching pairs in a sorted array (called the “two
same problem can be approached in different pointers” technique).
ways ● The Grid Search: tests the candidate’s knowledge
● You can keep practicing problems until you feel of strings and searching algorithms.
like you can solve them more often than not
Design & Architecture
Modules
Previously Solved Problem & Domain Deep
Dive
This interview assesses a past project you have worked on, what
your contributions were, and dives deep into the technical
challenges, intricacies, and architecture.

Be prepared to discuss a complex project that you have worked


on from start to finish.

New Problem
This is a whiteboarding interview where you will build the high
level architecture for a large scale application. You will be
evaluated on how you design a problem that is new to you but
relevant to what we work on at Uber. Be prepared to discuss
design requirements and evaluate trade-off decisions.
Design & Architecture: Resources
If you feel you need to brush up
on your design and architecture,
we recommend reading these
books and studying the high
level concepts.
Behavioral Modules
Collaboration & Leadership
This will evaluate how you:
● Build and sustain trusting, collaborative, and strategic relationships
within and across teams or orgs, working with integrity.
● Treat others with respect, embrace diverse perspectives and
encourage cooperation at all levels, leading by example.
● As a leader having conviction is expected and healthy debates
encouraged; when an outcome has been decided they embrace the
decision 100%. Embodies Uber's cultural values.

Impact - Efficiency & Quality


This will evaluate how:
● You scale yourself and the organization (defined as their manager’s
sub-tree) by making others better, more productive, and raising the
quality of what the org produces.
● Systems are built for long-term extensibility, how you led efforts to
leverage and improve existing solutions, etc.
Behavioral Example Questions Competency
Have you ever recognized a potential problem and Business acumen and intuition
addressed it before it occurred?

Have you ever had to solve a problem on your own, but Problem solving
needed to ask for additional help? How did you go about it?

Let’s say you disagree with your colleague on how to move Conflict resolution
forward with a project. How would you go about resolving
the disagreement?

Have you ever owned up to a mistake at work? Can you tell Honesty, willingness to improve and problem
me about it? solving
Broad Tips for Success
Technical Interviews Behavioral Interviews
● Break down the problem and share your thought ● Make sure you familiarize yourself with your own resume
process as you come up with solutions and and are prepared to discuss your past projects in detail.
implementation. This includes asking questions and ● Review the behavioral competencies listed in this deck
understanding the requirements of the questions. The and come prepared with examples of times you have
more an interviewer understands your thought process, demonstrated these skills.
the more they can collaborate with you and help guide ● Speak confidently about your past experiences,
you along the way. contributions, and motivators - we want to really get to
● If at any point in the interview you feel like asking for know you!
clarification, or think something doesn’t make sense, feel ● Interviewing is a two way street - make sure to come
free to challenge the interviewer! Also, don’t be afraid to prepared with questions for us so that we can give you all
admit to mistakes. What we’re looking for most is the information you’ll need to make a well informed
someone that can collaborate with other engineers to decision on Uber being a good fit for you.
solve bigger problems.
● We are not evaluating your knowledge of specific
Don’t Forget!
programming languages, but rather your ability to solve
If you feel like you are not succeeding in one interview, don’t
problems with the tools in your toolkit. Use tools that you
be afraid to ask questions, pause, and restart. Go into your next
are most comfortable with.
interview with full confidence! We look at all of your skills across
the board, not just one interview.
Meet our Engineers
Advice from our engineering team

Candidate Prep 18
Flavia Rangel, Sr. Software Engineer
Interviewing Tips
● I see interview processes as a sports contest, where to be able to
compete you have to study the requirements and practice. In my
experience, reading the recruiters e-mail around what to expect
and links to study, helped me to not be over anxious during the
interview session. So, if in real state it is "location, location, location"
in interview processes it is "preparation, preparation, preparation"

Why Uber?
● I've been working for Uber for 4 years now and I LOVE this
company. First, because I feel respected, recognized and pushed
to learn and grow. Second, because I have the opportunity to work
with the best professionals around the world. And Finally, third,
because by working at Uber I'm able to positively change people's
lives by setting the world in motion.
Guilherme Ferreira, Sr. Software Engineer
Interview Tips
● The interview process is quite fair, but don’t go unprepared.
● Take your time to study the material that was given. Read all the papers and revisit all
the concepts that are required for the interviews.
● There is a lot of content to study on Youtube about the intended topics. Devour those
videos. They are examples of real live interviews with real top tier engineers.
● Don’t think you’ll remember everything when the time comes, write it all down. Take
your time to write down real and descriptive stories about the behavioral topics. Think
through each of the topics and stories.

Why Uber?
● There are only a few companies around the world that might be able to say they’re
“changing the world” and only a few who impact the economics for everyone on a
large scale on each country.
● Uber does both and does it with grace.
Working in a company that impacts the world ● The amount of people that are directly impacted by Uber is astounding. If we were
on a daily basis, not only in the jargon, and to count each one of our driver partners as workforce, Uber would be the biggest
working with the most qualified engineers in company in the world, by far.
the world is a unique opportunity, like being in ● Granting all of them a tool on which they can make their living whilst providing a tool
the Fellowship of the Ring. Give your best and that allows anyone to surpass their own mobility limitations, is a work that seconds to
put effort in the hiring process so you can be none.
part of this amazing company.
Karina Kohl, Engineering Manager
Interview Tips
● Be assertive on your answers. If the question is not clear for you, ask for
clarification so you can go straight to the point. It is important to answer what
was questioned. As you can ask for clarification, you can also follow up with the
interviewer if they need more information.
● It is your time to shine. Have in mind your great achievements, your process of
problem solving, how you collaborate. A suggestion is to write down these
things. List the projects you have worked before and the highlights of each
one. Read it before the interview. Even if you got a little bit nervous, you do not
risk to forgot your previous achievements.

Why Uber
● You work with globally used solutions.
● The impact of the deliveries of every team is huge.
● You see what you build being used.
● People are great. You always have answers and support from your peers.
● Every conversation is deep. We considered inputs from different people and
different point of views to build our solutions.
Guilherme Vierno, Sr. Software Engineer
Interview Tips
● Prepare specifically for coding interviews. Interviews differ from an engineer's
day-to-day work, and many preparation materials are available online.
● Practice coding and design questions with a timer; get comfortable solving
questions on a tight deadline.
● Do mock interviews with a friend; you'll be training and have the opportunity
to get some feedback before the real deal.
● Use the programming language that you're most comfortable with.

Why Uber
● Work on a global team solving global problems. Join a team of thousands of
brilliant engineers.
● Engineering at Uber's scale: few companies worldwide have the scale we
deal with daily at Uber.
● The learning culture at Uber is fantastic. From day one, you'll be in contact
with bleeding edge techs, and the learning opportunities are nearly endless.
Interview Checklist

Download Zoom: Charge device Set up a space Grab some water


This is the platform and check wifi conducive to or coffee:
we use for video connection: interviewing: You will be talking a
conferencing. Make sure your Make sure your lot during the call
Make sure it is on device is charged space is quiet with and will probably
your device. and connected to minimal get thirsty!
the internet. distractions.
Resources
Technical Interviews
Software Developer Interview Prep
Cracking the Coding Interview

Leetcode Algorithms

Uber Engineering Blog


Engineering Interview Process

HackerRank - Common Questions

About Our Offerings


Ridesharing
Uber Eats

Uber Freight
Uber For Business
Good Luck!
We hope that we’ve
answered some of your
questions, and helped you
get a glimpse of what it is like
to be part of Uber.

Please contact your recruiter


if you have any questions.

You might also like