I AM HIRED

Неделя 310 ₽Месяц 630 ₽3 месяца 1 680 ₽Год 5 680 ₽

Staff Backend Engineer — San Francisco Bay Area

Разработчики, Backend · вчера, 21:00 · 21.11.2026

Зарплата не указана

Откликнуться

Компания: ••••••••

Локация: San Francisco Bay Area

Формат: не указан

Занятость: Полная занятость

Грейд: Senior

About The Role

A Xhr9XkjNXXD contract starts as a sentence and ends as a payout. In between, the backend turns the wording into terms, has the creator review and sign them, locks the stake in escrow on Base, matches a taker, waits for the AI resolver, holds a 48-hour dispute window and pays the winner. Every step is a state change with money behind it, and each one has to be right the first time and still right when it runs again after a timeout.

You'll be one of the few engineers who decide how that backend is shaped as it grows: the Postgres data model, the server actions behind the web app, the public API and MCP server that AI agents use, and the notifications and webhooks that tell people what happened. It's TypeScript throughout (Next.js on Vercel, Postgres on Supabase with Drizzle), and you'll own whole areas of it, not tickets in it.

This is an individual contributor role. There's no layer of process between a good design and production: you pick the problem, write it down, get a review from people who care, and ship.

What you'll do

• Own the contract lifecycle in the backend, from the draft a creator reviews to the payout: the states, the edge cases (an offer that expires as someone takes it, a dispute raised in the last minute, two people trying to take the same open seat at once) and the tests that pin them down.

• Design the schema and queries for the next stage of growth: contracts, stakes, the mirror of the chain, resolver runs, and the event pages, home feed and leaderboards that read them.

• Shape the public API (REST, OpenAPI, idempotency keys, rate limits, OAuth scopes) and the MCP server, so an AI agent acting for someone is exactly as safe as that person clicking themselves.

• Build the backend for what's next: v6M4XRTA6fd-WmKHvg contracts, where Xhr9XkjNXXD takes a side with its own money, and the mobile apps we're planning on the same API.

• Make the paths people feel fast: the share link that opens from a group chat or a post on X, the event page, the moment between signing and seeing your stake locked.

• Review designs across the team, write the documents others build on, and raise the bar for code that touches money.

• Be on call for what you own, and when it breaks, find the cause and remove it.

What you'll bring

• Staff-level backend experience: you've set the technical direction for systems other engineers built on, and you ran them in production.

• Strong TypeScript and Node.js, or deep experience in another backend language and the appetite to work in ours.

• Real depth with Postgres: schema design, indexes, transactions and locking, and reading a query plan when a page gets slow.

• Systems behind you where a bug cost someone money (payments, trading, marketplaces, wallets), and the habits that came from it in how you design, test and ship.

• You've built for a consumer product with real traffic, including the spikes that come when everyone shows up at once.

• You pick the most important problem yourself, write the plan and see it through.

Bonus points

• Next.js server actions, Drizzle or Supabase.

• Public API or developer platform work: versioning, OAuth, webhooks, agents.

• On-chain apps, wallets or stablecoin payments.

• Enough React to build the screen for the API you just designed.

Your first 90 days

• 1Ownership of one core backend area, with a written map of its states, failure modes and gaps.

• 2One change shipped that removes a whole class of bugs from the contract lifecycle, not just one bug.

• 3The slowest path users feel made measurably faster, with numbers before and after.

• 4A plan the team agrees on for what the backend needs before seeded contracts and mobile apps.

About Xhr9XkjNXXD

Xhr9XkjNXXD turns any disagreement into a contract. Someone writes a yes-or-no question in plain words ("Will Bitcoin trade above $150,000 by March 31?", "Will IShowSpeed's stream go past 24 hours?"), puts money on their side, and one other person takes the other side. Both stakes are locked in a USDC escrow contract on Base until the outcome is known, and the winner takes the pool.

The hard part of a prediction market is settling it fairly. Ours is settled by an AI resolver that reads official records, credible reporting, price feeds and even livestreams, quotes its evidence word for word, and checks itself in code. Either side can dispute an outcome for 48 hours, and human moderators decide what the AI can't. Deposits work with crypto from most chains, with cards and Apple Pay, and from exchanges.

We're early, and the people who join now decide what Xhr9XkjNXXD becomes. We care most about two things: reaching the people who already argue about outcomes every day (crypto traders, sports fans, stream chats, group chats), and knowing each world well enough to write contracts that are worth taking.

How to apply

Email •••••••• with the subject “Application: Staff Backend Engineer”. Include your LinkedIn or CV, and:

• A backend system you designed and owned: what it handled, how it failed and what you'd change now.

• How you'd model a contract's states so that a retried request can never pay anyone twice.

Apply by email

Поиск по вакансиям

Название компании скрыто

Названия компаний и их продуктов мы не публикуем на сайте — они доступны в Telegram-боте I AM HIRED. Откройте эту вакансию в боте: увидите название, сможете откликнуться и настроить рассылку подходящих вакансий.

Открыть вакансию в боте