The short version
A well-funded fintech in San Francisco is hiring engineers. We're running the search and we're not naming them in the ad. You'll get the company, the founders, the backers and the full picture on a first call.
What we can tell you is what the work is, because that's the part that should decide it.
The work
You'd own money movement. Ledgered internal state, transaction lifecycle management, idempotency, retries, deterministic replay. Continuous reconciliation across independent ledgers, card network events, banking events and third party reports, and the tooling to chase a mismatch to its root before it compounds.
You'd build the guardrails that stop bad states happening rather than catch them late: double spend, duplicate webhook processing, inconsistent balances, orphaned settlements.
You'd own the integrations with card issuing, banking and disbursement, and credit partners, and the compliance and reporting infrastructure that the banking partner and the regulators depend on.
The system serves hundreds of accounts today. The job is taking it to hundreds of thousands, through spiky demand, without dropping or duplicating a single event. Correctness here isn't a quality bar. It's the product.
Why the title is Member of Technical Staff
Because they'd rather hire the person than fill the box.
Small engineering team, very large payments surface area. The engineers who do well there pick up whichever part of the stack matters most that quarter and own it end to end. Ledger one month, an issuing integration the next, fraud decisioning after that.
The title gets shaped around what you're strongest at once they've met you.
Who it's for
You've built systems that were critical. Payments, card issuing, banking rails, ledgered systems, high throughput backends. You've been close enough to money movement to have real opinions about how it goes wrong.
You've owned a system end to end, rather than a component inside a large organisation. You've been the person who gets paged, decides the architecture, and lives with the consequences of both.
You assume banks, queues, vendors and networks are unreliable, and you build things that stay predictable anyway. Reliable to you means the same behaviour at 10 payments or at 10,000,000.
You're obsessive about correctness and auditability. Retries don't erase history. Idempotency is deliberate. Validation belongs where truth lives.
If you want a defined lane inside a large payments organisation, this isn't it.
Practicalities
San Francisco, in person. Visa support available. Highly competitive SF-level compensation and top tier equity offered.
Fifteen minutes is enough for us to tell you who they are and for you to decide whether it's interesting.
That's the list. If those three are true, apply. We'd rather read your application and decide than have you decide for us.
What helps, but isn't required
Any of these will get our attention. None of them are gates.
This probably isn't the right role if
You want to work remotely. We're in the office together in San Francisco and that isn't flexible.
You want a defined roadmap to execute against. We often don't know what the right thing to build is until someone goes and finds out.
You'd rather go deep on one service for the next three years. That's a good way to work. It just isn't how this team is built.
CardlessSan Francisco
$160K–$295K / yr
Posted Sep 24, 2026
$300K–$500K / yr
Posted Sep 21, 2026
FukuSan Francisco, California
$200K–$280K / yr
Posted Dec 10, 2025
FukuSan Francisco, California
$150K–$280K / yr
Posted Dec 10, 2025
HuzzleEl Salvador
Pay not posted
Posted Sep 8, 2026
The Better Money CompanyNew York City
Pay not posted
Posted Oct 6, 2026
Source: the Eqltech Workable job board. We last checked this job 51 min ago. We first saw it 51 min ago. A job on a job board does not always mean that the team interviews people now. We found this job board in a public list. We did not yet compare it with the careers page of the company.
No one has reported an interview at Eqltech yet. Did you interview there? Add the questions.