Professional Documents
Culture Documents
SCREEN
3. Back-end interviews are based on CS
fundamentals..
4. You have to reach a solution to the
Be ready and prepare for your problem (you'll be expected to have a
working solution with the code running
interview! by the end of the session).
HOW YOU WILL BE Take some time to think about what
you like about Lyft's product, our fun-
EVALUATED: loving and exciting culture means
everything to us; make sure you’re able
1. Correctness - Your code should be able to match that because first impressions
to successfully run within coderpad and mean a lot!
solve the given problem.
2. Performance - Keep performance in PRACTICE PROBLEMS: Browse our engineering blog. and come
mind for proposed solutions. Be ready with insightful, curious questions about
Highly encouraged to try:
to analyze the time and space our product and teams.
1. https://leetcode.com/problems/asteroid-
complexity of your solutions. *Tip: Do
collision/
not wait until the end to Debug. Before you interview ask yourself,
2. https://leetcode.com/problems/number-
3. Clean Code - Your code should be well “Why Lyft?” - We are looking for
of-islands/
decomposed and written with good 3. https://leetcode.com/problems/lru- Engineers that are just as passionate as
variable names. The goal is that your cache/ our team members.
interview can easily understand the 4. https://leetcode.com/problems/word-
code you’re writing (ie looking at code search/
structure and organization, ensuring
Good Luck!
5. https://leetcode.com/problems/trapping
good basic syntax, is code easy to read, -rain-water/
etc).
4. Verbal communication and Practice your technical interview with
collaboration will be really important, a mock-up interview
as this gives us insight into how you
work with your team to find a solution! Additional Resources:
Make sure to ask clarifying questions, 1. https://leetcode.com/problemset/all/
ask for feedback, take the feedback, 2. https://www.geeksforgeeks.org/
and be able to implement changes. 3. https://www.hackerrank.com/dashboard