Sr Software Engineer/AI (Financial)
- Compensation
- Not disclosed
- Location
- Not listed
- Work setup
- Remote
- Seniority
- Senior
- Employment
- Not specified
- Experience
- 3+ years
- Category
- Software engineering
- Posted
Skills
Must have
- TECHNICAL REQUIREMENTS
- • Technology Stack: C#, .NET.• Database: PostgreSQL — required.• Cloud: Microsoft Azure or AWS — required.• Financial systems: Ledger, reconciliation, banking integrations.• AI implementations: AI/LLM
- • At least 5 years of overall professional working experience.
- • Senior-level or higher engineering capability, with independent ownership of complex backend systems; ideally 3–5 years or more building financial applications.
- • C# and .NET backend development.
- • Practical experience with ledger or reconciliation solutions and banking or financial platform integrations, including transaction lifecycles and discrepancy resolution.
- • Deep understanding of immutability, idempotency, race conditions, auditability, and financial transaction consistency. Ability to prevent decimal precision loss and rounding errors.
- • Strong PostgreSQL skills covering schema design, SQL, transactions, isolation levels, locking, constraints, indexing, performance, and exact numeric data types.
- • Hands-on Azure experience developing, deploying, and supporting services, with secure configuration, access controls, monitoring, and production troubleshooting.
- • Experience delivering backend applications within a Microsoft technology environment.
- • Demonstrated AI-enabled delivery using coding assistants, with the ability to use Claude Code effectively and independently review, debug, and test generated code.
- • Hands-on implementation of AI/LLM or generative AI application features beyond coding-assistant usage, including API integration, output evaluation, failure handling, and data protection.
- • Strong testing skills covering monetary calculations, duplicate processing, concurrent transactions, reconciliation, integration failures, and recovery.
- • Clear written and spoken communication; ability to clarify financial requirements, document decisions, and communicate progress and blockers.
Nice to have
- • Experience with code versioning tools, such as GitHub or GitLab.
- • Double-entry accounting, subledgers, settlement, bank statement ingestion, or financial close processes.
- • Event-driven architectures, message queues, transactional outbox patterns, and replayable processing.
- • AI for reconciliation assistance, exception classification, or financial document processing with controlled validation and approval.
Full description
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 one senior engineer or above for a financial systems project focused on ledger, reconciliation, and banking platform integrations. The engineer must understand the financial consequences of design decisions and build systems that preserve accurate, auditable records under retries, concurrency, and partial failures.
The role requires .NET/C#, PostgreSQL, Azure, AI-enabled delivery using Claude Code, and hands-on AI/LLM or generative AI implementation experience. Ideally, candidates will bring 3–5 years or more of experience building financial applications.
Responsibilities
ABOUT THE PROJECT
- Build financial applications centered on ledger integrity, reconciliation workflows, and integration with banking and financial platforms.• Work within a Microsoft technology environment using PostgreSQL and Azure. The specific backend language and framework remain to be confirmed.
ABOUT THE ROLE
- Translate financial rules into reliable services, own implementation and testing, and communicate technical decisions, progress, and blockers clearly.• Use Claude Code to accelerate delivery while remaining accountable for the correctness, security, and maintainability of all generated changes.
WHAT YOU'LL WORK ON
- Ledger services. Design and build financial ledger services, transaction posting workflows, balance calculations, and reconciliation capabilities with clear accounting rules and traceable transaction histories.
- Immutable records. Implement immutable financial records and controlled correction or reversal workflows that preserve the original transaction and its audit trail.
- Idempotent processing. Build idempotent APIs, ingestion processes, and background jobs so retries, duplicate messages, and repeated requests do not create duplicate financial effects.
- Concurrency and consistency. Prevent race conditions and inconsistent balances through appropriate transaction boundaries, isolation levels, locking, concurrency controls, and database constraints.
- Monetary accuracy. Protect monetary accuracy through explicit decimal precision, scale, rounding, and serialization rules across application code, PostgreSQL, and external integrations.
- Reconciliation solutions. Develop reconciliation workflows that match ledger records against banking or payment data, identify missing or duplicate transactions, investigate discrepancies, and support exception resolution.
- Banking integrations. Integrate with banking and financial platforms through APIs, files, or event-driven interfaces, accounting for delayed data, partial failures, out-of-order events, and safe replay.