Software Engineer, Communication Platform

About the role

You will build and scale the communication platform that serves millions of Chime members as a foundational member of a small, nimble team. The role focuses on delivering fullstack features and driving key architectural changes that support the mission of helping members achieve financial progress.

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

Mobile and backend architecture is shaped through designing, developing, testing, releasing, and scaling changes to support member communication. This work ensures the platform serving millions of members remains robust and scalable.

Complex problems within the team domain are addressed through collaboration with cross-functional partners, which accelerates development velocity and aligns solutions with product goals.

Reliability for millions of users is maintained by developing thoroughly tested code and conducting quality assurance across the stack.

The messaging layer that powers communication for millions of members is improved through driving architectural enhancements that strengthen core communication flows.

Requirements

A minimum of 3 years of fullstack development experience is required to perform this role effectively.

Backend development skills with frameworks are demonstrated through experience, including optional exposure to GraphQL or Ruby.

Mobile development skills with frameworks are shown through experience, including optional exposure to React Native.

Effective cross-functional collaboration is necessary to work closely with team members in a fast-paced setting.

Architectural patterns for large production services are understood, enabling safe changes that avoid disruptions for millions of users.

A passion for learning is demonstrated by sharing knowledge with teammates, paired with keen attention to detail in all work.

Strong empathy for users guides the creation of products that truly serve their financial needs.

Practical notes

This position requires onsite work in San Francisco with a hybrid schedule of four days in the office and Fridays remote. Employment eligibility details and policies, including remote work options and benefits, vary by location. 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

Platform reliability directly affects how members manage their finances, making stability and performance essential.

Modern tools and practices are used to build scalable systems that serve a large user base efficiently.

The environment values ownership, learning, and continuous improvement at individual and team levels.

Diverse teams collaborate to solve meaningful problems in financial technology.

Independent execution is balanced with teamwork to deliver high-quality product experiences.

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.