this seems to translate "we fucked it so hard with trying to vibe code a real thing, your job is to fix it and take all the blame"

https://xcancel.com/fernandaso52511/status/2034984420885540947

Fernanda Souza (@FernandaSo52511)

Senior Backend Engineer (AI + Payments) We’re building a global, API-first payments platform. The core is already live — payments API, ledger, commerce, checkout, dashboards, infrastructure. Much of the codebase has been generated by AI. 💰 $30k–$40k/month · Remote · Contractor We need someone who can look at all of this and say: “this will break in production” — before it actually does. What already exists - Full payments API (PaymentIntents, Refunds, Customers, Charges) - Double-entry ledger with atomic entries - Native commerce engine (Products, Orders, Fulfillment, Inventory) - Hosted checkout, Merchant Dashboard, Admin Portal — all deployed - API Gateway in Go (auth, rate limiting, circuit breaking) - 60+ PostgreSQL tables, strict TypeScript, versioned migrations - Async workflows for webhook delivery and settlement - Terraform managing 183+ AWS resources - CI/CD with smoke tests and automated deploys Your mission Be the last line of defense between code and real money. Concretely: 1. “This will break in production” Identify failure points before they cause downtime — silent crashes, missing restart policies, monitoring gaps, non-recovering processes 2. “This code will cost us money” Double charges, race conditions in the ledger, lack of idempotency, unsafe refund/dispute flows, incomplete reconciliation 3. “This is a security risk” Exposed secrets, missing encryption at rest, misconfigured VPCs, unauthenticated endpoints, injection vectors in AI-generated code 4. “This database will fail” Unsafe migrations, lack of backup/disaster recovery, unindexed queries, broken transactions, schema changes causing downtime Day-to-day - Deep audit of AI-generated backend code (TypeScript + Go) - Review financial flows to identify edge cases that could cause losses - Validate infrastructure decisions and highlight reliability risks - Build integration tests proving critical flows work end-to-end - Ensure observability is strong enough to detect issues in minutes, not hours Stack TypeScript · Hono.js · Drizzle ORM · Go · PostgreSQL (Aurora Serverless) · Redis · Temporal · Docker · AWS ECS Fargate · Terraform · Cloudflare We’re looking for someone who - Has 5+ years in backend engineering, preferably in fintech/payments - Has operated production systems handling real money — incidents, postmortems, on-call - Can audit AI-generated code and spot what AI misses - Has strong intuition for “this will break” before it does - Knows PostgreSQL deeply (transactions, locking, migration safety, disaster recovery) - Has experience with observability (tracing, alerting, runbooks) - Values accuracy over speed — a ledger bug in production is worse than a week of delay Nice to have - Experience with PCI DSS compliance - Familiarity with double-entry ledger systems - Experience with Temporal or distributed workflows - Go for high-performance services - Experience finding (and fixing) financial bugs in production 🔗 Application Form: https://form.typeform.com/to/aQt51Pfi

Nitter
@davidgerard good god burn it with fire
@davidgerard Yeah. I'm gonna need to see at least one more zero in those pay rates for cleaning out your cesspool. At least.

Even though with another "0" it would be a lot of money for me, I still would not do it.

Instead of getting that money and do this "work", I'd rather get no money and just look out the window and watch some birds. It would be the better deal for me.

@jmax @davidgerard

@duke_of_germany @davidgerard My criterion is enough money that after six months, I can do exactly that for the rest of my life.

(n.b. - I do think quite highly of myself. But nobody, including me, is worth that kind of money.)

@duke_of_germany @davidgerard And the work, assuming I did, would actually be fending off the bozos while I did a complete rewrite.
@davidgerard "Senior" 💰 $30k–$40k/month lmao
@spiqueras @davidgerard This is way more money than I see most senior roles advertising in the US. They are often near 100-120k a year.
@davidgerard They handle payments. WHAT COULD GO WRONG.
@davidgerard man if i were younger i would take them up on this, but now days i don't think i have the spoons to deal with this level of shitshow
@ariadne @davidgerard oh wow, some of what they listed makes me think this is absolutely the job from hell.

@ariadne @davidgerard

  • Values accuracy over speed — a ledger bug in production is worse than a week of delay

lmao, if only there were some way to (as the cool kids are saying these days) 'shift left' such concerns.

@davidgerard @dysfun these are the types of jobs I used to take on 😂
@ariadne @davidgerard i mean i did too, but usually not knowing how bad it would be.

@davidgerard Incredibly low pay rate for that level of job as well - a job that would have paid $2M+ per year and they want it for $360k-$480k lol.

Even when they are doing the 'rah rah we need super skilled important people' thing to try and attract people, they are still like 'but AI means we don't have to pay you much because you are just an AI herder, not a programmer'.

@davidgerard (Also also 'last line of defense, 100% responsibility for everything including all of the money stuff' and they say 'senior' instead of 'staff' - clown shoes)
@davidgerard something tells me software engineering will remain alive and well 😀

@davidgerard

Much of the codebase has been generated by AI.
[...]
We need someone who can look at all of this and say: “this will break in production” — before it actually does.

Not sure the "looking at it" step is even necessary, tbh.

@davidgerard Oh I can do that for free even:

I can look at all of this and say: “this will break in production”

GLWT

@davidgerard the idea of “engineering reliability” as a coat of paint
@davidgerard Look, all the hard parts are already done: infrastructure, distributed systems, database design, encryption, financial flows, etc. Now we just need someone to bolt on safety and security after the fact. How hard can it be‽
@davidgerard
They tried to vibe-code a PCI-DSS compliant payment processing system??? Lol. Lmao.
@davidgerard This is satire, right? Right?!
@davidgerard Scapegoat wanted, must be willing to face all the consequences of our decision making and surrender a future career elsewhere because of the reputational harm when we throw you to the wolves.
@davidgerard why they don't just ask claude to "not make any mistake!"
@[email protected] While I wouldn't put it past an AI-pilled startup to try using AI to poorly "solve" a problem that was solved by the Mesopotamians, I wonder whether this is real. The user joined twitter this month, and has only the one post. It's so over the top absurd it's hard to believe a real human being would write it, let alone post it.

@davidgerard i dont get it. Why can't they just ask claude to review the codebase and fix all the bugs?

I am told that ai always works, you just need to prompt harder.

@davidgerard With that salary I could retire early. With that job description I will retire right into the grave.
@davidgerard The job title is wrong, it should read "accountability sink"