← Back to all jobs
Lyft logo

Staff Backend Engineer, Payments

Lyft

🌎 Remote — Anywhere in the USFreelanceSoftware Engineering$233K – $258K /yr
Apply with RemoteHire24Posted 17 days ago

You apply directly through RemoteHire24. We review your application and contact shortlisted candidates by phone, WhatsApp, or Telegram.

Job description

Lyft is hiring a Staff Backend Engineer, Payments to join our fully remote team in the United States. As a Staff Backend Engineer, Payments, you'll design, build, and ship reliable software that scales to millions of users. This is a freelance, work-from-home role open to candidates across the US (Remote — Anywhere in the US). About the role You'll design, build, and ship reliable software that scales to millions of users, partnering with a friendly, distributed team across US time zones. We care about outcomes over hours and give you the autonomy, tools, and support to do your best work from home. What you'll do: • Improve performance, reliability, and developer experience • Collaborate with product and design on new initiatives • Develop, test, and maintain features across the stack • Review pull requests and mentor teammates • Write clean, well-tested, and documented code What we offer: • 401(k) retirement plan with company match • Paid parental leave • Competitive salary and meaningful equity • Flexible working hours across US time zones • Generous paid time off and company holidays How we work We're remote-first and async-friendly. Expect clear documentation, regular feedback, supportive teammates, and real opportunities to grow your career. Lyft is proud to be an equal opportunity employer. We celebrate diversity and are committed to creating an inclusive environment for everyone.

Requirements

Minimum qualifications: • 7+ years of experience, including leading teams or projects • Strong communication in a remote, async environment • Proficiency in one or more modern languages (TypeScript, Go, Python, or Java) • Experience with version control and CI/CD • Solid understanding of data structures, APIs, and databases Nice to have: • A track record of taking ownership and shipping independently • Comfort communicating clearly and proactively in writing