Member of Technical Staff - confidential search (fintech)

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.

About the role

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 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 organization. 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 behavior 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 organization, 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.

Requirements

What we actually require: You've built systems where being wrong had consequences. Money, records, claims, transactions, anything where a bug meant someone had to be told and something had to be corrected. Payments is the obvious version of this. It isn't the only one
You've owned something properly, end to end. You designed it, shipped it, kept it alive, made the architecture calls and lived with them afterwards. That can be a whole system at a small company or a serious subsystem inside a large one.
What matters is that it was yours, not that it was big
You want to be in San Francisco, in person, and you want this kind of responsibility. Both of those are real and neither is flexible
Both of those are real and neither is flexible

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.

San Francisco, in person

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.

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.

Requirements

What we actually require: You've built systems where being wrong had consequences. Money, records, claims, transactions, anything where a bug meant someone had to be told and something had to be corrected. Payments is the obvious version of this. It isn't the only one
You've owned something properly, end to end. You designed it, shipped it, kept it alive, made the architecture calls and lived with them afterwards. That can be a whole system at a small company or a serious subsystem inside a large one.
What matters is that it was yours, not that it was big
You want to be in San Francisco, in person, and you want this kind of responsibility. Both of those are real and neither is flexible
Both of those are real and neither is flexible

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.

San Francisco, in person

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.

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.

Requirements

What we actually require: You've built systems where being wrong had consequences. Money, records, claims, transactions, anything where a bug meant someone had to be told and something had to be corrected. Payments is the obvious version of this. It isn't the only one
You've owned something properly, end to end. You designed it, shipped it, kept it alive, made the architecture calls and lived with them afterwards. That can be a whole system at a small company or a serious subsystem inside a large one.
What matters is that it was yours, not that it was big
You want to be in San Francisco, in person, and you want this kind of responsibility. Both of those are real and neither is flexible
Both of those are real and neither is flexible

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.

San Francisco, in person

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.

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.

Requirements

What we actually require: You've built systems where being wrong had consequences. Money, records, claims, transactions, anything where a bug meant someone had to be told and something had to be corrected. Payments is the obvious version of this. It isn't the only one
You've owned something properly, end to end. You designed it, shipped it, kept it alive, made the architecture calls and lived with them afterwards. That can be a whole system at a small company or a serious subsystem inside a large one.
What matters is that it was yours, not that it was big
You want to be in San Francisco, in person, and you want this kind of responsibility. Both of those are real and neither is flexible
Both of those are real and neither is flexible

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.

San Francisco, in person

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.

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.

Requirements

What we actually require: You've built systems where being wrong had consequences. Money, records, claims, transactions, anything where a bug meant someone had to be told and something had to be corrected. Payments is the obvious version of this. It isn't the only one
You've owned something properly, end to end. You designed it, shipped it, kept it alive, made the architecture calls and lived with them afterwards. That can be a whole system at a small company or a serious subsystem inside a large one.
What matters is that it was yours, not that it was big
You want to be in San Francisco, in person, and you want this kind of responsibility. Both of those are real and neither is flexible
Both of those are real and neither is flexible

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.

San Francisco, in person

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.

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.

Requirements

What we actually require: You've built systems where being wrong had consequences. Money, records, claims, transactions, anything where a bug meant someone had to be told and something had to be corrected. Payments is the obvious version of this. It isn't the only one
You've owned something properly, end to end. You designed it, shipped it, kept it alive, made the architecture calls and lived with them afterwards. That can be a whole system at a small company or a serious subsystem inside a large one.
What matters is that it was yours, not that it was big
You want to be in San Francisco, in person, and you want this kind of responsibility