The finance-STAR variant: lead with scope and the architecture trade

The finance-STAR variant: lead with scope and the architecture trade

1. 1Situation, with scale, constraints and the gap. Set the numbers and name what wasn't defined: "Usage was metered in three systems, none reconciled and revenue rec for overages was a quarter-end spreadsheet nobody trusted." Then name the constraints you worked under: the timeline, the SOXSarbanes-Oxley Act. A US law that forces companies to keep auditable controls over any system that affects their financial reporting. Press Enter for the full definition. bar, the off-the-shelf platform's limits and a team of one. The gap is the story.
2. 2Task, framed as what you had to define. "I had to decide where the revenue subledger lived, how metering became an invoice idempotently and which controls were coded versus configured. None of it existed."
3. 3Action, in the first person and split build-vs-configure. "I configured the CPQ-to-order flow off the shelf, but coded the rating engine and the reconciliation job because the platform couldn't express our tiered overage logic." That split is the senior signal.
4. 4Result, in finance units. Close cut from N days to M, reconciliation break rate driven to near zero, ARR/billings roll-forward tied to the GL, audit evidence generated automatically or metering scaled Nx without a rebuild.
5. 5Reflection, one line. The trade you'd revisit or the principle you carried forward. That is what reads staff-level.