Business Systems Engineer - Finance

Abridge

Where
Hybrid in SF Office
Type
Full time

Posted 5 hours ago· Checked live at Abridge 47 minutes ago

Live.Open on the employer's own site.

See how you score for this job

One sentence and your resume. We score it against what Abridge asks for, line by line.

See my score
Is this job still open?
Yes. We checked it live on Abridge's own hiring page 47 minutes ago.
What is the job?
Founded in 2018, Abridge is the first AI-native clinician intelligence platform organized around the patient, built for clinicians, and designed to help health systems coordinate the clinical, financial, and evidence-based decisions for every moment of care. Powered by purpose-built AI for healthcare, Abridge connects patients, providers, payers, and life sciences companies.
What does it pay?
The posting doesn't say.
Our verdict
Live. Open on the employer's own site.

What the job is

Founded in 2018, Abridge is the first AI-native clinician intelligence platform organized around the patient, built for clinicians, and designed to help health systems coordinate the clinical, financial, and evidence-based decisions for every moment of care. Powered by purpose-built AI for healthcare, Abridge connects patients, providers, payers, and life sciences companies.

What you'll do

Own Finance Integrations

→ Own the Finance team's GitHub repositories: pipelines, the semantic layer, workflows and our skills marketplace. Review changes, keep CI healthy and set the standard for how the team ships.

→ Architect and own the integrations between Rillet, our ERP, and the systems around it: payroll (Rippling), spend (Ramp), banking (SVB), Salesforce (CRM), and others as we add them. Decide what flows where, by API, webhook or pipeline, and when to use a native connector or build our own.

→ Build and maintain the Python loaders and scheduled jobs that land our finance systems in Snowflake every day.

→ Keep them healthy: freshness, row-count and source tie-out checks every day, alerts that reach the right person, and runbooks someone else can follow.

→ Close the coverage gaps by bringing in the systems that don't reach the warehouse yet, such as sales tax, close management, equity and contracts.

→ Maintain the scripted ERP postings we already run, with tie-out checks and change control.

→ Partner with our IT & Automation and Revenue Systems teams on shared systems and standards.

Build Out the Semantic Layer

→ Extend the governed metrics layer (Snowflake Cortex Analyst today) to cover spend, AI tooling, budget and the hiring plan, and add the relationships that let it answer cross-table questions.

→ Take metric definitions from draft to canonical with their owners in FP&A and Accounting: one definition each, documented, tested and versioned.

→ Run validation and drift checks on every change, and keep the monitoring agent that proposes fixes honest.

Keep Us Harness Agnostic

→ Design the shared context (skills, MCP connectors and operating instructions) so a workflow behaves the same in every agent harness we use.

→ Run the team's skills marketplace: packaging, versioning, auto-update and retiring stale skills.

→ Evaluate new models and agent tools as they ship, and adopt the good ones without rewriting our workflows.

→ Own the guardrails: service credentials, read-only roles, data tiers, and a person approving anything an agent sends, posts or changes.

Help the Finance Team Build

→ Partner with accountants and analysts to scope, build and ship agentic workflows for the close, reconciliations, accruals, AP, procurement, revenue recognition, technical accounting and reporting.

→ Every workflow has a named owner in Accounting or Finance who signs off on its logic and output. You own the engineering; they own the answer.

→ Make building easy: templates, code review, office hours and documentation, so workflows outlive the people who wrote them.

→ Grow more reviewers than just yourself. Success means the team trusts what it built and can maintain it without you.

→ Move workflows from draft to live with tie-outs, a clear human review step and an exception path.

→ Examples of what you'll build: reconciliation agents that prepare a workbook for an accountant's review, scripted journal entries that post only when amounts tie, a contract-to-revenue agent that drafts subscription setups, and month-end accrual analyses. Workflows can live in GitHub or inside the tools the team already uses: our ERP, spend management and HRIS.

Bonus points if you have

→ Built custom MCP servers, not just used them.

→ Written skills, prompts or MCP connectors that other people rely on.

→ Exposure to finance or accounting data (an ERP, the general ledger, the close), or time on a Finance, Accounting or FP&A team. We'll teach you the accounting.

→ Built business systems across functions, such as HRIS, CRM, identity or IT tooling.

→ Exposure to IPO readiness, SOX controls or audit support.

→ Worked in healthcare or another regulated industry.

In your application, include a link to, or a short description of, something you've built that other people use: a pipeline, a skill, an MCP server, an agent or an internal tool.

We value people who want to learn new things, and we know that great team members might not perfectly match a job description. If you're interested in the role but aren't sure whether you're a good fit, we'd still like to hear from you.

Similar open jobs

Software engineer jobs in San Francisco (1711)Jobs in San Francisco (11746)