Sr Software Engineer/AI (Financial)

Overview

This is a fully remote role on PH night shift schedule (9 PM–6 AM) with work equipment provided.

Role overview

We are looking for a senior contract engineer to assist with the creation of an in-house ledger and bank reconciliation platform. You will join an existing payments engineering team, own the platform’s architecture and delivery, and work directly with Treasury and Accounting operations.

The work calls for someone who understands the financial consequences of design decisions, has built bank reconciliation or matching systems in production, and keeps records accurate and auditable under retries, concurrency, and partial failures. AI is central to how this team builds software. You must be fluent at working with AI coding agents every day, not just familiar with them.

About the role

• Be a senior engineer for the bank reconciliation platform: own architecture, key design decisions (including data and service topology), implementation, and testing.
• Turn Treasury and Accounting reconciliation rules into reliable, testable services. Clarify ambiguous requirements with operations stakeholders and document decisions.
• Work AI-first: use Claude Code and agentic workflows to plan, build, refactor, debug, and test, while staying fully accountable for the correctness, security, and maintainability of every change.
• Communicate progress, risks, and blockers to engineering leadership and business partners.

• Bank reconciliation matching engine. Design and build configurable matching across bank, payment, and ledger data: one-to-one, one-to-many, and many-to-many matches, aggregated book records, rule sequencing and rule groups. Identify missing, duplicate, and partial transactions.
• Exception resolution. Build workflows and React-based operations tools so Treasury and Accounting users can investigate discrepancies, apply manual matches, and resolve exceptions with a full audit trail.
• Ledger integrity. Immutable financial records, controlled correction and reversal workflows, traceable transaction histories, and balance calculations, including FBO account balances.
• Bank and payment data ingestion. Idempotent, re-playable ingestion of BAI2 bank files, payment rail data, funding rail data, and service events, handling delayed data, out-of-order events, returns, and partial failures.
• Accounting integration. Generate journal entries from bank reconciliation results and deliver them to accounting software, including day-end entries.
• Concurrency and monetary accuracy. Correct transaction boundaries, isolation levels, locking, and constraints. Explicit decimal precision, scale, rounding, and serialization across C#, PostgreSQL, and external integrations.
• Prototype assessment and service design. Evaluate the existing prototype, decide what to keep, and help redesign.
• Parallel run and cutover. Plan and run side-by-side validation against the current process, measure match accuracy, and lead the cutover.
• Cloud operations. Build and run services on AWS while integrating with existing Azure-hosted services, with monitoring, secure access, resilient processing, and actionable diagnostics.
• AI in the product. Where it adds value, apply AI/LLM capabilities to bank reconciliation, such as exception classification or match suggestions, with evaluation, data protection, and human approval for financial decisions.

Technical requirements

• Backend: C#, .NET. (required)• Frontend: React, Typescript (required)• Database: PostgreSQL — required. (MSSQL - helpful)• Cloud: AWS for the new platform and Azure for existing services (both used)• Financial systems: Ledger, reconciliation and matching, bank file ingestion (BAI2), ACH and other payment rails, double-entry accounting, general ledger integration• AI-enabled delivery: Claude Code and agentic development workflows (required)• AI implementations: AI/LLM features in production applications (strongly preferred)• Observability: Datadog or equivalent

Required qualifications

• Senior-level or higher engineering capability, with independent ownership of complex backend systems. Ideally 3–5+ years building financial applications.
• Has built or substantially owned a reconciliation or transaction-matching system in production, including one-to-many and many-to-many matching, rule configuration, and exception handling.
• Event-driven architectures, message queues, transactional outbox patterns, and re-playable processing.
• Working knowledge of double-entry accounting, subledgers, settlement, and general ledger integration; understands how reconciliation supports financial close and audit.
• Experience ingesting bank and payment data such as BAI2 or similar statement formats and ACH files, including returns and reversals.
• Deep understanding of immutability, idempotency, race conditions, auditability, and transaction consistency. Able to prevent decimal precision loss and rounding errors.
• Strong C# and .NET backend development.
• Production React experience building internal or operational tools.
• Strong PostgreSQL skills: schema design, SQL, transactions, isolation levels, locking, constraints, indexing, performance, and exact numeric types.
• Fluent, daily use of AI coding agents (Claude Code or equivalent) as a core part of how you work: directing agents, writing clear specs and prompts, and rigorously reviewing, debugging, and testing generated code. Able to evaluate and harden AI-generated code you did not write.
• Strong testing skills covering monetary calculations, duplicate processing, concurrent transactions, matching accuracy, integration failures, and recovery.
• Experience setting technical direction and mentoring other engineers.
• Clear written and spoken communication. Able to work with Treasury and Accounting stakeholders to pin down financial rules, document decisions, and report progress and blockers.

• Shipped AI/LLM features in production, including API integration, output evaluation, failure handling, and data protection, especially for reconciliation assistance, exception classification, or financial document processing.
• Has replaced a vendor or ERP reconciliation process, including parallel runs and migration of historical and in-flight data.
• Accounting software integration or bank reconciliation experience.
• High-volume payments, bill pay, or FBO account environments.
• Working in change-controlled database environments with DBA review.
• Breadth across money movement (payments, funding, chargebacks) that would carry over to follow-on work.

Required Skills ASP.NET (C#) (5), PostgreSQL (5), Microsoft Azure (5), AWS (5), Large Language Model (LLM) (3)

Years of Experience Needed CSS (5), PostgreSQL (5), Visual Studio (5), GitLab (5), Azure Cloud (4), AWS (4), Claude Code (3), REST API (5)

• The problem. Client processes high volumes of utility and bill payments. A single bank transaction often corresponds to many payment records (and vice versa), including large numbers of near-identical split payments going to different destinations.
• What the platform must do. Many-to-many matching, aggregation of book records, rule sequencing (applying a rule across all transactions before moving to the next rule), rule groups, and a clear workflow for exceptions that need human review.
• Where it fits. An existing .NET service is the primary source and translation layer for payment data. Bank activity arrives through BAI2 files and payment rails (ACH, check, card settlement, bill pay networks).
• Delivery. Build, then a parallel run against the current bank reconciliation process before cutover.