Meet Victor Ligas, Founding Software Engineer
He works on the parts nobody sees: the money moving, the ledger behind it, and the retries that make a failed payment a non-event.

There is a version of this company that is a nice interface on top of a mess. Victor is a large part of why that is not the version we shipped.
His work sits under everything: disbursement and collection, the ledger that has to agree with itself at all times, the schedules, the retries, and the reconciliation a finance team never has to build because it already exists.
Why that matters more than it sounds
An advance is easy to give and hard to run. The hard parts are the second Tuesday when a debit fails, the customer who pays early, the one who pays twice, the cycle that finalises while somebody is mid-payment. Each of those is a small correctness problem, and getting one wrong is the kind of mistake that ends up in somebody's bank account.
So he is careful in a way that is genuinely reassuring to work beside. When Victor says something is fine, it is fine.
What he says about it
His summary of the job, roughly: money systems should be boring on purpose. We put that on a wall.