Company
micro1
Annual salary
$350k – $500k/yr
Location
Remote
Listed
2d ago
- Level:
- Lead
Join the talent pool
Set up a profile and we'll consider you for roles at labs like micro1.
Set up your profile →About this role
We're looking for a Staff Software Engineer to architect and build our financial infrastructure from the ground up. You'll own the systems powering global payouts, payment processing, ledgering, reconciliation, and financial controls, ensuring every expert gets paid accurately and on time.
This is a highly hands-on, high-ownership role for an engineer who has previously designed and built financial systems at scale. You'll set the technical direction for our payments infrastructure, working closely with engineering, finance, operations, and leadership to build reliable systems that can support our next stage of growth.
What you'll do
- Architect and build scalable financial infrastructure from scratch, owning the technical roadmap for global payments and payouts.
- Design reliable, idempotent payment workflows across multiple currencies, payment rails, and providers, with safe retries and robust failure handling.
- Build double-entry ledgering, reconciliation, and audit systems to ensure accurate tracking of financial transactions.
- Integrate global payment providers, banking partners, and payout rails, including ACH, SEPA, SWIFT, and local payment networks.
- Develop financial controls, monitoring, approval workflows, and fraud prevention mechanisms to safeguard money movement.
- Design resilient, event-driven systems capable of handling provider outages, delayed settlements, failed transactions, and high transaction volumes.
- Lead architectural decisions, technical design reviews, and complex migrations while maintaining payment accuracy and operational continuity.
- Partner directly with founders, finance, and operations to translate complex financial requirements into reliable, scalable engineering solutions.
- Establish engineering best practices for financial correctness, observability, incident response, and long-term platform reliability.
What you need
- 8+ years of backend software engineering experience, including significant technical ownership of production financial systems.
- Proven experience architecting and building payment, payout, or ledger infrastructure from scratch, taking systems from initial design through production and scale.
- Deep understanding of payment processing, money movement, transaction lifecycles, idempotency, concurrency, and distributed systems.
- Hands-on experience designing double-entry ledgers, financial reconciliation processes, and auditable transaction systems.
- Experience integrating payment providers and banking infrastructure across multiple payment rails, currencies, and geographies.
- Strong backend engineering skills in TypeScript or similar languages, with expertise in SQL, relational databases, and event-driven architectures.
- Experience building highly reliable financial systems with robust failure handling, monitoring, security, and operational controls.
- Strong understanding of financial data integrity, transaction consistency, and safe migrations of business-critical systems.
- Demonstrated ability to independently own complex technical initiatives, make architectural decisions, and deliver production systems in fast-moving environments.
- Excellent communication skills and the ability to collaborate effectively with engineering, finance, operations, and executive stakeholders.
Nice to have
- Experience building global contractor payouts, payroll infrastructure, or cross-border payment platforms.
- Familiarity with financial compliance requirements, including KYC/KYB, sanctions screening, tax documentation, and audit controls.
- Experience scaling financial platforms to process millions of dollars monthly across multiple countries.
- Familiarity with SOC 2, PCI DSS, or financial audit requirements.
- Experience with stablecoin or crypto-based payment infrastructure.
- Experience building internal finance tools, reconciliation dashboards, or payment operations platforms.
- Experience leveraging AI coding agents and AI-assisted development workflows in production engineering.
About micro1 and legal notices
Compensation & Benefits Notice
The national pay range for this full-time position is base salary of $200,000 –$260,000. All employees are eligible for equity compensation, and employees may also receive performance-based bonuses, dependent on role and subject to company policies. micro1 provides a comprehensive benefits package, including up to 100% reimbursement for health-insurance premiums, paid time off, a 401(K) plan with a company match, and additional benefits designed to support a high-performing, remote-first workforce.
micro1 is an equal opportunity employer. All qualified applicants will receive consideration for employment without regard to race, color, religion, sex (including pregnancy, sexual orientation, or gender identity), national origin, age, disability, genetic information, veteran status, or any other characteristic protected by applicable local laws, regulations and ordinances. If you need assistance and/or a reasonable accommodation during the application process, reach out to [email protected].
Our hiring process utilizes artificial intelligence tools to assist in candidate screening and assessment. Our AI tools are designed to complement, not replace, human decision-making.
Skills and categories
Common questions
How do I apply for the Software Engineer (Staff), Financial Platform & Infra role at micro1? +
Use the Apply button on this page. It opens micro1's own application form, so you apply directly with them.
What does this micro1 role pay? +
micro1 lists $350k – $500k/yr.
Is this role remote? +
The listing is remote. Check micro1's posting for any country or time zone requirements.
Software Engineer interview prep
Questions Software Engineer interviewers often ask. They aren't taken from this listing.
How do you approach designing a system when the requirements are still likely to change?
I design around the parts of the problem I'm confident are stable, like the core data model, and keep the parts most likely to change, like specific business rules, isolated behind clear interfaces. Over-engineering flexibility everywhere just adds complexity to parts of the system that were never going to change.
What's your process for debugging an issue that only reproduces in production, not locally?
I add targeted logging around the suspected area and compare production data or configuration against my local setup, since an issue that's environment-specific usually traces back to a real difference between the two rather than a fundamentally different bug. I avoid making speculative changes without first confirming where the divergence is.
How do you decide when a piece of code needs a test versus when it's low-risk enough to skip?
I prioritize tests for logic with real business consequences if it breaks, or code that's likely to be touched again later by someone unfamiliar with it. Simple, rarely-changed glue code gets less coverage, since the cost of a thorough test there often exceeds the risk it's protecting against.
How do you evaluate a proposed technical solution's trade-offs, like performance versus maintainability?
I start from the actual constraint that matters for this specific system, whether that's genuinely performance-critical or whether maintainability is the bigger long-term cost, rather than defaulting to whichever trade-off I personally prefer. Optimizing for performance the system doesn't need just adds complexity nobody benefits from.
This listing mentions these tools. Brush up before a technical screen:
Related roles
More full-time jobs at micro1
micro1 builds AI-native infrastructure and employs a globally distributed team of engineers, researchers, and operations professionals.
See all micro1 roles →