Want to get hired at Lyft?
Backend Engineer - Scheduled Rides
Lyft
Toronto, ONOn Site
Original Job Summary
About the Role
At Lyft, our mission is to improve people’s lives with the world’s best transportation. As a Backend Engineer - Scheduled Rides, you will build differentiated products that enhance riders' and drivers' experiences, ensuring a dependable and delightful planned-rides offering.
Responsibilities
- Establish roadmap and system re-architecture
- Write well-crafted, maintainable code
- Participate in code reviews and uphold quality standards
- Share knowledge via tech talks and brown bags
- Lead large projects from ideation to execution
- Collaborate with internal partners to unblock and support initiatives
Experience
- 2-3 years of software engineering experience
- Proficiency in object-oriented programming and distributed systems
- Experience with relational and NoSQL databases
- Familiarity with Python and clear design documentation
- Ability to design, build and improve team-owned components
Benefits
Enjoy extended health and dental coverage, mental health benefits, family benefits including 18 weeks paid parental leave, subsidized commuter benefits, and flexible paid time off policies.
Work Arrangement
This role is hybrid: in-office at least 3 days per week with flexibility to work remotely up to 4 weeks per year.
Key skills/competency
- Backend Engineering
- Python
- Distributed Systems
- System Architecture
- Code Quality
- Collaboration
- Design Documentation
- Database Management
- Technical Leadership
- Agile Methodologies
How to Get Hired at Lyft
🎯 Tips for Getting Hired
- Customize your resume: Highlight backend engineering and Python experience.
- Research Lyft culture: Understand their mission and diversity values.
- Prepare portfolio: Showcase relevant distributed systems projects.
- Practice technical challenges: Focus on object-oriented and database topics.
📝 Interview Preparation Advice
Technical Preparation
circle
Review Python and OOP concepts.
circle
Study database and NoSQL fundamentals.
circle
Practice distributed system design problems.
circle
Brush up on system architecture patterns.
Behavioral Questions
circle
Describe a challenging project you led.
circle
Explain teamwork in cross-functional projects.
circle
Discuss handling code review feedback.
circle
Share conflict resolution experiences.