Staff Engineer | Revenue and Financial Management Infrastructure

Stripe's Revenue and Financial Management group builds beyond payments into revenue management, financial operations and analytics, covering products such as Billing, Invoicing, Revenue Recognition and Reconciliation, plus the batch and real time platform underneath them for processing large scale financial data. This staff role is to help architect and design a system from the ground up, setting technical direction across projects while mentoring others on the team. The posting names these products as key pillars of Stripe's growing software business and a major revenue stream, which is a clear statement about how much visibility the work carries. Stated bar is twelve or more years with system architecture and distributed systems handling large volumes of data.

Published requirement is a strong technical background including 12+ years of experience with system architecture and designing distributed systems that handle large amounts of data. The role is a Staff Engineer position in Bengaluru. Team and product context: Stripe's Revenue and Financial Management group builds products that extend the company's scope beyond payments into revenue management, financial operations and analytics. Named products include Billing, Invoicing, Revenue Recognition and Reconciliation, along with the underlying platform for batch and real time processing of large scale financial data that powers them. The posting states these solutions are key pillars for Stripe's growing software business and a major revenue stream. Responsibilities as published: help architect and design this system from the ground up; set technical direction across a variety of projects and initiatives while mentoring and growing others on the team; scope and lead large technical projects that form the foundational pillars for financial data management infrastructure; and scrutinise technical designs and decisions. What makes this domain harder than it sounds: financial data infrastructure has correctness requirements that ordinary data platforms do not. Revenue recognition and reconciliation must be auditable and reproducible, results have to reconcile exactly rather than approximately, historical restatement has to be handled without corrupting prior periods, and the batch and streaming paths must agree with each other. Engineers who have done this work well tend to find the experience transfers strongly, because relatively few people can reason about both distributed systems and accounting semantics. The mentoring element is stated as part of the staff remit rather than as management, and no reporting line is mentioned, so we have published this as an individual contributor role. Good fit for a distributed systems engineer with twelve or more years who wants greenfield architecture where correctness is the hard constraint.