Senior Software Engineer, Backend - Emerging Products
ripplingBrooklyn (NY)
Senior Software Engineer, Backend - Emerging Products
Posted today
ripplingBrooklyn (NY)
SENIORITY
Lead
About the role
Overview:
In this role you design and build backend services and APIs for Rippling’s multi-product platform, enabling reliable, secure workflows across Spend, IT, identity, and compliance. You partner with product and cross-functional teams to turn complex needs into scalable technical solutions, while advancing AI-powered workflows in enterprise-scale environments. You help ensure trust, transparency, and control as customers adopt automation at scale. Compensation / Benefits competitive salary benefits equity
Responsibilities:
Design and implement backend services and APIs powering core product capabilities Build reliable, secure, and scalable systems for high-volume workflows across spend, IT, identity, approvals, and compliance Make strategic architectural decisions around data modeling, performance, and reliability Translate business needs into robust technical solutions in collaboration with product, frontend, platform, and design teams Evolve systems involving workflows, permissions, policy enforcement, procurement, device/app management, and security controls Raise the technical bar via design reviews, code reviews, and mentoring Create unified product experiences that consolidate fragmented employee, spend, device, app, and access management
Key requirements:
5+ years of experience in production backend development using Python, Go, or similar high-scale language Deep expertise in distributed systems architecture, data modeling, and relational database performance Experience with large-scale systems and enterprise-grade reliability Strong CS fundamentals and ability to deliver complex projects Exceptional communication with technical and cross-functional stakeholders strong communication cross-functional collaboration mentorship Python or Go (or similar high-scale backend language) distributed systems architecture data modeling (relational databases)
Before you apply
Applying takes about a minute. These four things decide how fast it moves after that.
Your profile is current
It's what we read first. Occupations, seniority and locations matter more than a long history.
Two examples you can talk through
Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.
A number in mind
What you're on now and what would make you move. We negotiate better when we know both.
Your notice period
Employers plan around it, and it's the question that stalls offers most often.
Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.