Senior Full-Stack Software Engineer, Unsecured Cards

About the role

The Cards team at Chime recruits a Senior Full-Stack Engineer to build and scale new card products and the backend systems that power them. This role solves complex problems across product, design, risk, credit, and compliance while delivering trusted member experiences at scale.

Software engineers turn product ideas into working code. Engineers work in small teams, review each other's work, and ship in small batches. Most teams follow agile practices such as sprints and daily standups. Engineers also write tests, fix bugs, and improve performance. The field values clear communication as much as technical skill. Engineers spend part of every week on planning, code review, and debugging, not just writing new code. The ability to explain a technical decision in plain words separates strong engineers from the rest.

Key facts

What you'll do

This work supports millions of members by designing and building scalable backend services and frontend applications for web and mobile.

Multi-engineer efforts are led by breaking down problems, defining scope, and driving execution to deliver high-impact features.

Technical design decisions balance performance, reliability, and long-term maintainability.

Engineers are mentored and supported to enhance team velocity, code quality, and overall execution.

Requirements

Production-grade software is built over 5+ years, with a track record of shipping reliable, user-facing features. Projects or major features are owned end-to-end, including design, implementation, and delivery.

Backend APIs and services are developed with Ruby on Rails or comparable frameworks, alongside modern frontend frameworks such as React or React Native. Transactional databases and caching systems are operated effectively, with an appreciation for clean, well-tested, maintainable code.

Experience working in ambiguous, fast-moving environments enables solution definition rather than only implementation. Collaboration skills support effective partnership with product managers, designers, and other engineers. A mindset focused on impact, quality, and continuous improvement is maintained. Fintech, lending, or other regulated/credit domain experience is a strong plus.

Practical notes

or Stride Bank, N.A., Members FDIC. Typical interview steps

Hiring for engineering roles usually starts with a recruiter screen, followed by one or two technical rounds. Candidates often solve a coding problem, discuss past projects, and answer system design questions. Some loops include a take-home task. Final rounds typically cover team fit and give candidates a chance to ask questions. Interviewers look for how you break down an unfamiliar problem, not just whether you reach the answer. Practicing a few problems aloud and reviewing your own past projects are the best preparation.

Good to know

Work in this area relies on modern web and mobile technologies, backend APIs, and transactional data systems. Engineers in regulated domains often collaborate with compliance, legal, and risk teams to ensure product behavior meets standards. Continuous learning and iterative improvement are common in fast-growth technology organizations. Cross-functional collaboration is essential when building financial products used by millions of members.

Questions to ask

Worth asking in any interview: how the team measures success, who the role works with daily, what the onboarding looks like, and what the company is trying to achieve this year. Asking what past hires did well is a strong final question. Keep the list short and pick the questions that matter most to you.

Career growth

Engineering careers usually progress from individual contributor to senior, staff, and principal levels. Some engineers move into management and lead teams of five to twenty people. Others stay on the technical track. Growth follows demonstrated impact, not tenure alone. A typical engineering ladder has clear levels with defined expectations for scope, quality, and mentorship. Moving up usually requires owning outcomes end to end rather than completing assigned tickets.