Financial Systems Engineer

About Extend:

Extend is revolutionizing the post-purchase experience for retailers and their customers by providing merchants with AI-driven solutions that enhance customer satisfaction and drive revenue growth. Our comprehensive platform offers automated customer service handling, seamless returns/exchange management, end-to-end automated fulfillment, and product protection and shipping protection alongside Extend’s best-in-class fraud detection. By integrating leading-edge technology with exceptional customer service, Extend empowers businesses to build trust and loyalty among consumers while reducing costs and increasing profits.

Today, Extend works with more than 1,000 leading merchant partners across industries, including fashion/apparel, cosmetics, furniture, jewelry, consumer electronics, auto parts, sports and fitness, and much more. Extend is backed by some of the most prominent technology investors in the industry, and our headquarters is in downtown San Francisco.

About the Role:

Extend runs a service-contract business where every dollar must be traceable from inbound merchant data, through our operational and analytics databases, into the accounting system, and back out to obligor, reinsurer, and audit reporting.

The Financial Systems Engineering team owns the systems and controls that keep that traceability automated, tested, and auditable. Your scope runs from raw merchant data through invoicing and financial reporting: the models that determine what gets invoiced and reimbursed, the financial models the business reports from, and the tie-outs that prove the numbers agree.

You’ll report to our Director, Financial Systems Engineering. The role is hands-on SQL and dbt with real ownership: you write the logic that produces reported numbers and you answer for what you ship.

What You’ll Do:

• Build and maintain invoicing and reimbursement logic. The models that calculate what has been invoiced, what is due, and what is in error across contracts sold and claims paid.
• Reconcile across systems. Automated tie-outs between inbound merchant data, operational databases, the warehouse, and the accounting system.
• Drive variances to root cause. Establish the source of truth on each side and resolve breaks at the source.
• Build and maintain financial models in dbt. Revenue recognition, obligor and reinsurer reporting, and claim cost, with tests, documentation, and PR review.
• Triage reported data issues. Quantify impact, identify who needs to act, hold affected invoices pending correction, and track the systemic fix.
• Validate claim and service order expense accuracy. Confirm reported expenses match what was paid, and extend automation across reimbursement paths.
• Partner on merchant configuration. Support internal audits of how inbound merchant data maps to internal representations, and work with the owning teams to resolve findings.
• Build standing financial controls. Loss ratio and anomaly monitoring by merchant, closed service orders with unexpected expenses, attribution gaps, each routed to an owner automatically.
• Investigate and correct data against production APIs, and partner with engineering teams on the upstream fixes that stop the problem recurring.
• Support internal and external audits with traceable, documented, reproducible results.

What We’re Looking For:

• 4-6 years in analytics or data engineering. Building analytical or financial models in dbt (or equivalent) under version control, with testing and PR reviews.
• Strong SQL. You write efficient, well-structured SQL against large financial datasets, and you can trace complex existing models to confirm the logic matches the business intent.
• Reconciliation instincts. You know what a source of truth is, how to prove two systems agree, and what to do when they don’t.
• Comfort with financial data. A wrong number here reaches an invoice, an auditor, or a partner, and you work accordingly.
• API fluency for investigating and correcting operational data.
• Clear written communication. You’ll explain data to accountants and account owners, and push back when a request doesn’t hold up.
• A bias toward root cause and automation. Fixing this month’s invoice is the baseline. You want to know why it broke and how to keep it from breaking next month.
• Comfort with ambiguity. You can shape how the work gets done when the path is not already defined.
• Bonus: merchant reconciliation; warranty, insurance, or service-contract programs; claims and reimbursements; order-to-cash systems; NetSuite; obligor and reinsurer reporting; or AI-assisted workflows for operational triage.