{"schemaVersion":"jobsearcher.job.v1","id":"e42aaafb15cdc2abbe5b1a27","url":"https://jobsearcher.com/jobs/e42aaafb15cdc2abbe5b1a27","canonicalUrl":"https://jobsearcher.com/jobs/e42aaafb15cdc2abbe5b1a27","title":"Senior Software Engineer, Payroll Engine","description":"Senior Software Engineer, Payroll Engine de Anda portfolio company Team: Payroll Level: Senior (IC) Location: Remote (U.S.) Start: early November 2026 Compensation: $100,000–$105,000 THE ROLE You own the heart of the product: the payroll domain model, the append-only ledger, and the pay-run engine that takes a run from draft to committed check. Your code decides what people get paid. The exit criterion for your first four months is that the engine reproduces a corpus of real pay runs from the incumbent system to the cent. WHAT YOU WILL DO • Design and build the domain model: pay groups and calendars, earning and deduction codes with limits and ordering, employee tax profiles, year-to-date and quarter-to-date accumulators per EIN. • Build the ledger as an append-only record of every committed check and adjustment, the single source for registers, general ledger, year-end and audit. • Build the pay-run state machine: draft, preview, calculate, approve, commit; regular and off-cycle runs; manual checks; voids and reversals; retroactive pay. • Implement gross-to-net orchestration around the tax adapter: pre-tax and post-tax deductions, imputed income, supplemental wages, garnishment calculation with withholding limits. • Build the generic hours-and-earnings import, then the bridge from the portfolio company's time-and-attendance product that turns locked, approved timecards into earnings lines with rate, pay code, work location and job-cost dimensions. • Build and maintain the regression harness: replay the corpus on every change, report variances to the cent, and run every variance to ground. • Write Technical Documents from the product manager's PRDs, direct coding agents against them, and review every agent-authored PR line by line before merge. • Keep money as integer cents and committed runs immutable; make every calculation re-runnable from stored inputs and engine version. MUST HAVE • 5+ years building transactional backend systems in Python; Django and PostgreSQL in production. • Has shipped a system where money is the output: payroll, billing, banking, insurance claims, accounting. You can explain how you kept a ledger correct under concurrency and corrections. • Fluent in integer-cents arithmetic, rounding rules, and the difference between a correction and a reversal. • Designs state machines and event-sourced or append-only data models; knows why committed records are never edited. • PostgreSQL depth: migrations against live data, constraints, transactions, advisory locks or equivalent. • Writes tests as part of the change; has built or maintained a replay or golden-file regression suite. • Has worked with AI coding agents on real deliverables: writes specs an agent can execute and reviews agent output critically. • Comfortable in a monorepo with CI, Docker Compose and GitHub Actions. NICE TO HAVE • U.S. payroll domain: pay codes, pre/post-tax ordering, YTD limits, FLSA overtime, garnishment priority rules, multi-EIN employers. • GraphQL schema design (Graphene) and React/Apollo for the pay-run UI. • Celery or equivalent for long-running calculation jobs. • Time and attendance or scheduling domain; job costing and labor allocation. • Experience maintaining AGENTS.md-style conventions for a team. NOT A FIT • CRUD-app backgrounds with no financial or transactional system experience. • Engineers who treat floating-point money as fine until it isn't. • Someone who treats agent output as done once it compiles. • Someone who wants a green-field stack; this lives inside the portfolio company's existing time-and-attendance codebase.","company":"De Anda Capital","rawCompany":"de anda capital","city":"Remote","state":"OR","isRemote":true,"isActive":false,"createdAt":"2026-11-01T11:23:17.045Z","occupations":[{"code":"15-1252.00","title":"Software Developers","slug":"software-developers"},{"code":"43-3051.00","title":"Payroll and Timekeeping Clerks","slug":"payroll-and-timekeeping-clerks"},{"code":"15-1251.00","title":"Computer Programmers","slug":"computer-programmers"}],"industries":[{"code":"541511","title":"Custom Computer Programming Services","slug":"custom-computer-programming-services"},{"code":"513210","title":"Software Publishers","slug":"software-publishers"},{"code":"541512","title":"Computer Systems Design Services","slug":"computer-systems-design-services"}],"jobPosting":{"@context":"https://schema.org","@type":"JobPosting","title":"Senior Software Engineer, Payroll Engine","description":"Senior Software Engineer, Payroll Engine de Anda portfolio company Team: Payroll Level: Senior (IC) Location: Remote (U.S.) Start: early November 2026 Compensation: $100,000–$105,000 THE ROLE You own the heart of the product: the payroll domain model, the append-only ledger, and the pay-run engine that takes a run from draft to committed check. Your code decides what people get paid. The exit criterion for your first four months is that the engine reproduces a corpus of real pay runs from the incumbent system to the cent. WHAT YOU WILL DO • Design and build the domain model: pay groups and calendars, earning and deduction codes with limits and ordering, employee tax profiles, year-to-date and quarter-to-date accumulators per EIN. • Build the ledger as an append-only record of every committed check and adjustment, the single source for registers, general ledger, year-end and audit. • Build the pay-run state machine: draft, preview, calculate, approve, commit; regular and off-cycle runs; manual checks; voids and reversals; retroactive pay. • Implement gross-to-net orchestration around the tax adapter: pre-tax and post-tax deductions, imputed income, supplemental wages, garnishment calculation with withholding limits. • Build the generic hours-and-earnings import, then the bridge from the portfolio company's time-and-attendance product that turns locked, approved timecards into earnings lines with rate, pay code, work location and job-cost dimensions. • Build and maintain the regression harness: replay the corpus on every change, report variances to the cent, and run every variance to ground. • Write Technical Documents from the product manager's PRDs, direct coding agents against them, and review every agent-authored PR line by line before merge. • Keep money as integer cents and committed runs immutable; make every calculation re-runnable from stored inputs and engine version. MUST HAVE • 5+ years building transactional backend systems in Python; Django and PostgreSQL in production. • Has shipped a system where money is the output: payroll, billing, banking, insurance claims, accounting. You can explain how you kept a ledger correct under concurrency and corrections. • Fluent in integer-cents arithmetic, rounding rules, and the difference between a correction and a reversal. • Designs state machines and event-sourced or append-only data models; knows why committed records are never edited. • PostgreSQL depth: migrations against live data, constraints, transactions, advisory locks or equivalent. • Writes tests as part of the change; has built or maintained a replay or golden-file regression suite. • Has worked with AI coding agents on real deliverables: writes specs an agent can execute and reviews agent output critically. • Comfortable in a monorepo with CI, Docker Compose and GitHub Actions. NICE TO HAVE • U.S. payroll domain: pay codes, pre/post-tax ordering, YTD limits, FLSA overtime, garnishment priority rules, multi-EIN employers. • GraphQL schema design (Graphene) and React/Apollo for the pay-run UI. • Celery or equivalent for long-running calculation jobs. • Time and attendance or scheduling domain; job costing and labor allocation. • Experience maintaining AGENTS.md-style conventions for a team. NOT A FIT • CRUD-app backgrounds with no financial or transactional system experience. • Engineers who treat floating-point money as fine until it isn't. • Someone who treats agent output as done once it compiles. • Someone who wants a green-field stack; this lives inside the portfolio company's existing time-and-attendance codebase.","datePosted":"2026-11-01T11:23:17.045Z","dateModified":"2026-11-01T11:23:17.045Z","hiringOrganization":{"@type":"Organization","name":"De Anda Capital","sameAs":"https://jobsearcher.com"},"jobLocationType":"TELECOMMUTE","applicantLocationRequirements":{"@type":"Country","name":"US"},"jobLocation":{"@type":"Place","address":{"@type":"PostalAddress","addressLocality":"Remote","addressRegion":"OR","addressCountry":"US"}},"identifier":{"@type":"PropertyValue","name":"JobSearcher","value":"e42aaafb15cdc2abbe5b1a27"},"url":"https://jobsearcher.com/jobs/e42aaafb15cdc2abbe5b1a27"}}