← Все заказы

Business Systems Engineer - Finance

Abridge

14 ч назад

Текст заказа

ABOUT ABRIDGE
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. This year, the platform will support more than 100 million patient-clinician conversations across more than 300 of the largest and most complex health systems in the U.S. With deep workflow integration, the Abridge clinician intelligence platform has been validated to support encounters in 28+ languages across specialties and care settings.
Abridge is setting the industry standard for the responsible deployment of Al across health systems with continual and transparent Al evaluation. Clinical decision support references and cites gold-standard sources of evidence, and features like Linked Evidence map AI-generated documentation to source data, helping clinicians quickly trust and verify the output.
Abridge was awarded Best in KLAS for Ambient AI in 2025 and 2026, in addition to other accolades, including TIME Best Inventions of 2024 and 2025, CNBC Disruptor 2025, and Fast Company’s Most Innovative Companies 2025.
We are a growing team of practicing clinicians, AI scientists, PhDs, creatives, technologists, and engineers working together to transform healthcare. We have offices located in San Francisco, New York, and Pittsburgh.
THE ROLE
We're looking for a Business Systems Engineer to connect and automate the systems Abridge runs on, starting with Finance. You'll own the data and AI platform our Finance team runs on, and help every person on the team build with it.
Abridge's AI is used by clinicians at hundreds of health systems, and Finance has to keep pace with a company growing that fast. We do it with a lean team that builds. Every finance system lands in one warehouse, one semantic layer defines the numbers, and agentic workflows take on more of the close, reconciliations and reporting every month. You'll be the engineer at the center of it, reporting to our VP of Finance Operations.
The role has four parts:
→ Integrations. Keep every finance system flowing into Snowflake, accurately and on time: ERP, spend management, banking, CRM, HRIS and payroll, and cloud and AI cost.
→ Semantic layer. Grow the governed metrics layer, so ARR, burn, headcount and spend mean one thing everywhere. Its users are people and AI agents alike, and both read the same definitions.
→ A harness-agnostic agent platform. This is a design principle for us: skills, connectors and context that run the same in Claude Code, Codex, Cursor or whatever ships next, so no single tool locks us in.
→ Team enablement. Help accountants and analysts build, ship and maintain their own agentic workflows for close, reconciliations, AP, procurement, revenue recognition, technical accounting and reporting.
This isn't an ERP administration role, and it isn't about evaluating tools and writing decks. You won't configure the ERP, but you will design and build what flows into and out of it. It's hands-on engineering: you'll own what you build and keep owning it. You'll also know when a problem needs an agent and when a plain, deterministic pipeline is the better answer.
Most of your time will go to Finance's systems. You'll also partner with our IT & Automation, People and Revenue Systems teams on the systems we share, such as HRIS, CRM and identity.
You'll work closely with:
→ our GL Accounting Manager, Technical Accounting Manager, FinOps Lead and Payroll Manager, who build and run workflows on the platform
→ FP&A, who own most metric definitions
→ our IT & Automation, Revenue Systems, People, Data Engineering and Security partners
This role is based in San Francisco or Chicago, working from our office on a regular schedule.
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.
WHAT YOU'LL BRING
→ Engineering foundation: You've built or maintained business systems, integrations or data pipelines, with production code in repositories you've owned.
→ Python, SQL and databases: Strong in Python and SQL, and you understand how databases work: modeling, performance and keeping data correct. Comfortable with git, pull requests and CI (we use GitHub Actions).
→ Warehouse and modeling: Hands-on with a cloud warehouse (Snowflake preferred) and with data modeling, ideally including a semantic or metrics layer (Cortex Analyst, dbt, Cube, LookML or similar).
→ Integrations: You've built or maintained integrations with SaaS or ERP APIs and reconciled the result to the s

Похожие заказы