Settlement Operations Lead

Replenysh; Costa Mesa (CA); Hybrid; USD 110,000 - 170,000; Full time

Job summary

Replenysh, Inc. seeks a detail-oriented operator to own the settlement engine, ensuring every dollar in and out is correct and on time. You will analyze exceptions, design preventive controls, and ship automation to reduce silent errors across a broad supplier network.

You’ll design dashboards and scripts to expose issues early, iterate quickly, and collaborate with cross-functional teams to improve the health of financial flows.

Qualifications

• Experience owning financial settlement or invoicing workflows.
• Ability to design controls and prevent regressions in complex systems.
• Comfort building dashboards, alerts, and automation to support reliable settlements.

Responsibilities

• Own the settlement engine: ensure accurate invoicing and timely payouts across all counterparties.
• Diagnose failures, perform root cause analysis, and redesign systems to prevent recurrence.
• Build instrumentation: dashboards, alerts, and automated controls to maintain reliability.

Skills

Settlement systems

Invoice accuracy

Payout timing

Root cause analysis

Process instrumentation

AI fluency

Systems thinking

Spreadsheet prowess

Scripting

Tools

Claude Code

Codex

Pi

Cursor

Job description

Own the settlement engine. Make sure every dollar in and out is right, on time, every time.

Take the challenge

We hire this role by what you build, not by where you've worked. Skip the resume. Open the challenge, use any tools you want, and show us how you'd run the work.

Replenysh is the operating layer for circular supply chains routing, recovering, verifying, and settling material flows across 5,000+ network partners. Every transaction has multiple counterparties and settlements buyers, sellers, service providers, freight, commissions, and more. Right now, too many of them have silent errors. We need someone who treats operational correctness like a product.

Why this role matters

Trust is the foundation of every material network. A supplier who waits ninety days to be paid never forgets it. A buyer who receives an incorrect invoice questions every future transaction. Operational trust is not a support function at Replenysh it is core infrastructure. Settlement reliability is the operational nervous system of the company and the foundation everything else gets built on.

What you will own

• Invoice accuracy: every buyer is billed the right amount, every time.
• Payout timing: every seller is paid in full and on schedule.
• Reconciliation: every transaction closes cleanly across all counterparties and settlements.
• Exception management: anomalies get caught, escalated, and resolved before anyone calls.
• Root cause analysis: when something breaks, you find the underlying cause and design it out.
• Process instrumentation: dashboards, alerts, and controls that prevent regressions.

Who we are looking for

• Precision operator with builder instincts: not a passive task executor.
• Obsessive loop-closer. You feel personal pain when something falls through a crack.
• When something breaks, you don’t say ‘I didn’t see it.’ You ask: ‘How could the system allow this to happen?’
• Cracked spreadsheet user. Pivot tables, lookups, modeling: second nature.
• You’ve probably built a spreadsheet, script, automation, dashboard, or internal tool because something annoyed you.
• AI-native. You reach for Claude Code, Codex, Pi, Cursor, or scripts before doing repetitive work by hand.
• Systems thinker. You design controls and automations, not just process steps.
• You don’t just fix errors: you redesign systems so the same error cannot happen twice.
• Detail-obsessed, but not slow. You move fast and check your work twice.

How we will evaluate the challenge

• Did you prioritize correctly? Did the most consequential issues get attention first?
• Did you find root causes, or just symptoms?
• Did you think like an owner, or like an auditor?
• How did you handle ambiguity? Did you create clarity from messy inputs, or wait for permission?
• Is your proposed system actually preventive, or just reactive?
• What did you choose to build first, and does it create leverage?
• How clearly and concisely do you communicate?
• Did you use AI fluently, or did you grind through everything by hand?

The challenge

It is your second day at Replenysh. Yesterday, a supplier called angry because they have not been paid for material shipped almost ninety days ago. This morning, four more things broke. Welcome to the role.