> Markdown version of [/jobs/ext/4649677-staff-software-engineer-accounts-ledgering](https://www.wearedevelopers.com/jobs/ext/4649677-staff-software-engineer-accounts-ledgering). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Staff Software Engineer, Accounts & Ledgering

- **Company:** Transparent Search Group
- **Location:** New York, NY, United States
- **Experience:** Experienced
- **Salary:** $210,000 - $275,000
- **Contract:** Permanent contract
- **Skills:** Artificial Intelligence, Python (Programming Language), PostgreSQL, Software Engineering, SQL Databases, Backend
- **Published:** November 9, 2026
- **Apply:** https://www.careerbuilder.com/job-details/staff-software-engineer-accounts-ledgering-new-york-ny--ecd2f161-4059-4288-b069-7aed522f7cf7

## About the Role

Software Engineering, Software Engineering, Clinical Study Publications, Artificial Intelligence (AI), Healthcare, Medical Coding, Healthcare Administration, Customer Relations, Revenue Management, Billing, * 8+ years building backend systems, including 3+ years designing and operating financial systems from 0 to 1

 * Hands-on experience building a double-entry payment ledger
 * Deep expertise in payments, billing, reconciliation, ledgers or accounting
 * Immutable, event-oriented data modeling where correctness is non-negotiable
 * Strong Python, PostgreSQL and SQL

## Description

The client is hiring a Staff Software Engineer (8+ years backend, 3+ years building financial systems from 0 to 1) who has built a double-entry payment ledger and has deep expertise in accounts and ledgering: payments, billing, reconciliation, ledgers or accounting. You will own the full architecture of money-critical systems at scale, with immutable, event-oriented data models where correctness is non-negotiable., * Design and operate a double-entry payment ledger and the next-generation account and ledger model, with invariants that make it structurally impossible to "print money".

 * Own the full money path: insurance ledger, posting and adjustment engines, patient account ledgers, bank reconciliation and AR reporting.
 * Reconcile billed charges, payer remittances, bank deposits and financial reports, and surface discrepancies before customers do.
 * Scale idempotent, explainable posting pipelines using negation/reversal semantics.
 * Operate money-critical systems on very large Postgres tables with safe migrations, projections, backfills and incident response.
 * Set the bar for observability and operational readiness, and mentor senior and staff engineers.