Senior Engineer, Developer Experience

Rocket Money•Washington, DC

3h•$150,000 - $185,000•Hybrid

About The Position

The ideal candidate is local to and interested in working from any of our offices (Silver Spring, NYC, SF, Miami, Denver) local to them 1-2x per week. ABOUT ROCKET MONEY 🔮 Rocket Money’s mission is to meaningfully improve the financial prosperity of millions of people. Rocket Money offers members a unique understanding of their finances and a suite of valuable services that save them time and money – ultimately giving them a leg up on their financial journey. ABOUT THE TEAM 🤝 Team Boost sits at the intersection of user-facing performance and developer productivity. We make Rocket Money fast and reliable for the millions of people who use it, and we make the codebase a joy to work in for the engineers who build it. We own the tooling, infrastructure, and best practices that help every engineer at Rocket Money ship faster and with more confidence. If you're the kind of engineer who gets excited about shaving milliseconds off app startup time, seconds off a critical database query, and minutes off a colleague’s feedback loop, this is the team for you. The unique challenge of Team Boost is holding developer experience and user experience in alignment, and we hold a sincere belief that the best outcomes happen when we make it easy for engineers to build performant software by default.

Requirements

5+ years of professional experience working with some combination of Node/TypeScript, React, React Native, GraphQL, and Postgres (or similar relational database).
A passion for performance and observability: improving load times, digging into metrics and traces to diagnose issues, or speeding up CI pipelines all sound like fulfilling projects.
Comfortable working across the full stack and diving deep into unfamiliar systems to understand how they work and how to make them better, whether that’s tracing a performance regression through GraphQL resolvers, ORM models, or caching layers.
Experience leading or participating in large-scale codebase migrations where “just rewrite it” wasn’t an option. Understanding the technical and social challenges that come with new tooling and processes, and how to break massive changes into safe, incremental steps.
Being both a student and a teacher, curious about new tools and technologies, eager to share what you learn through RFCs and technical strategy docs, and energized by the ambiguity that comes with a growing engineering organization.
Thinking about developer feedback loops as a product: how long does it take from saving a file to seeing the result, from pushing a commit to getting CI feedback, and thriving on measuring these processes and then working to systematically shrink them.

Nice To Haves

Experience with GitHub Actions, E2E testing frameworks, or mobile-specific concerns like over-the-air updates and native build tooling is a plus.
Bonus points for hands-on experience with large-scale TypeScript + GraphQL stacks and pnpm workspaces.

Responsibilities

Make the right thing the easiest thing: Identify developer friction points like slow type-checking, confusing test infrastructure, or painful onboarding and eliminate them through documentation, tooling, and automation.
Lead large-scale initiatives with precision and clarity: Write RFCs for projects related to our mission, build consensus across teams, and systematically execute architectural changes across the codebase.
Hunt down performance bottlenecks across the full stack: profile, instrument, and resolve issues spanning client rendering performance, GraphQL latency, and database query performance.
Raise quality and confidence through automation: Improve code quality across the engineering organization by authoring custom lint rules, maintain code generation pipelines that ensure type safety across packages, tune and maintain CI workflows to be both thorough and fast, and ensure that quality gates catch real issues rather than slow developers down.
Keep the foundation solid: Upgrade and maintain critical dependencies across a large dependency graph by navigating breaking changes in tools and manage pnpm catalogs, patches, and overrides to keep ~20 packages building cleanly.