Alt Platform Inc

Own cloud infrastructure, AWS resources, CI/CD pipelines, developer environments, observability, incident response, and tooling that improves engineering velocity. | Requires 7+ years of infrastructure, platform, or SRE experience, with deep AWS and Terraform expertise and a track record managing deployment infrastructure, developer tooling, and non-production environments. | Alt is unlocking the value of alternative assets, starting with the $5 B trading-card market. We let collectors buy, sell, vault, and finance their cards in one place and we are backed by leaders at Stripe, Coinbase, Seven Seven Six, and pro athletes like Tom Brady and Giannis Antetokounmpo. Our next frontier is real-time pricing at scale—the Alt Value that powers every trade, loan, and product on the platform. We're looking for an Infrastructure Engineer to own the platform that Alt's engineering team builds on. Today, infrastructure work at Alt is distributed across product engineers with no dedicated owner. You'll change that. You'll lead our cloud infrastructure, developer environments, and observability, making the entire engineering org faster, more reliable, and more cost-efficient. This is a foundational hire. You'll define how Alt operates as an AI-native engineering organization, from the environments our agents run against to the deployment pipelines our engineers ship through every day. What You'll Do Here: Own cloud infrastructure end-to-end: Take ownership of Alt's AWS footprint (ECS, RDS/Aurora, EC2, S3, SQS, ALB, and more). Right-size over-provisioned resources, de-provision orphaned services, implement resource tagging, and build cost visibility so we can make informed trade-offs as we scale. Build reproducible environments: Lead the effort to give every engineer (and every AI agent) the ability to spin up isolated, prod-like instances of Alt on demand. This means database cloning, per-branch services, routing, seed data, and auto-teardown. This is the substrate for how we want to build software. Fix staging: Make non-production environments reliable and representative, so engineers can stop testing in production, stop setting up test state by hand, and stop working around flaky search infrastructure. Bring Terraform under control: Fix infrastructure-as-code drift, build CI/CD automation, and make infrastructure changes safe and reviewable. Own observability and incident response: We run Datadog, Sentry, and Posthog across the stack. Rationalize our monitoring, improve alerting, and make sure we catch issues before our users do. Be a multiplier: You'll be the infrastructure leader for a growing engineering team. Level up the org through documentation, tooling, code reviews, and mentorship. Set the standard for how we operate. This is a perfect fit if you… Think in systems, not tickets: You see the connection between a flaky staging env, a rising cloud bill, and engineering velocity. You want to fix the root cause, not patch symptoms. Care about developer experience: You measure your success by how much faster and more confidently your teammates can ship. You build tools and platforms, not just infrastructure. Are cost-conscious by instinct: You know the difference between saving money and cutting corners. You think about unit economics when you see over-provisioned instances. Are excited about AI-native engineering: You see reproducible environments as the substrate for AI agents to do real work, and you want to build that substrate. Want to lead, not just execute: This isn't a role where someone hands you Terraform tickets. You'll define the infrastructure roadmap, make trade-off decisions, and own outcomes. What You Bring to the Table: 7+ years of infrastructure, platform, or SRE experience with deep AWS expertise (ECS, RDS/Aurora, EC2, ALB, IAM, CloudFormation or Terraform) A track record of owning and improving CI/CD pipelines, deployment infrastructure, and developer tooling at a growing company Experience building or managing non-production environments: staging, ephemeral environments, seed data systems, or similar Strong opinions on observability. You've instrumented systems, built dashboards, and improved incident response. Strong collaboration and communication skills. You write great docs, ask smart questions, and give thoughtful feedback. Bonus: Experience with cost optimization at scale What You'll Get From Us: Direct impact: You'll be the first dedicated infrastructure hire, the person who defines how Alt's engineering platform works and scales. Autonomy: High-trust environment with ownership over critical infrastructure and developer experience. What we offer: For full-time Employees We cover 85% of your medical, dental, and vision, and up to 50% for dependents. HSA/FSA available Generous PTO that people actually take Parental leave at full salary $200/month wellness + $100/month home office stipend Free DoorDash Pass membership, because dinner shouldn't be a decision Remote-first (for most positions), with WeWork access when you want a room with other humans 401(k) Alt Equity to all full-time employees

Own architecture and orchestration for payment processing, banking integrations, and risk management while meeting demanding reliability and scalability targets. | Requires 5+ years of backend engineering focused on payments, money movement, and relational database design, plus Python, AWS, and payment-provider experience. | Alt is unlocking the value of alternative assets, starting with the $5 B trading-card market. We let collectors buy, sell, vault, and finance their cards in one place and we are backed by leaders at Stripe, Coinbase, Seven Seven Six, and pro athletes like Tom Brady and Giannis Antetokounmpo. Our next frontier is real-time pricing at scale—the Alt Value that powers every trade, loan, and product on the platform. The Role An auction closes and every seller in it gets paid in the same moment, each against a different fee schedule — some by ACH, some by wire, some instant. A buyer funds a five-figure purchase and the bank returns it three days later. A webhook arrives twice, out of order, from a provider that was down for an hour. Every one of those movements has to reach the right account, on the right rail, at the right time, and land in the ledger exactly once. That is the whole job. You own how money physically moves at Alt: the providers, the rails, the orchestration layer that routes between them, and the risk posture that keeps a marketplace of high-value transactions safe. The ledger team owns the record; you own everything that happens between a customer's bank and that record. You are not building a checkout flow. You are building the liquidity that makes this marketplace work. The KPI: 99.99% reliability on gateway and banking integrations, and a time-to-funds for sellers and borrowers that we measure, publish, and beat every quarter. In payments, "mostly working" is a failure. The people who are great at this have integrated a provider that lied to them, and they design for the third retry, the late return, and the duplicate callback because they've been on the wrong side of all three. What You'll Own Rails and money movement. ACH origination and returns, RTP and other instant rails, wires, cards, and stablecoin settlement. A $300K wire and a $300 ACH debit are different products with different controls, and you'll design for both. Credit-push rails change what you can auto-charge and when funds are final — you'll own those product consequences, not just the integration. Provider architecture and orchestration. Multi-PSP integrations built so the next one isn't a rewrite, and a single orchestration layer that routes each movement to the right provider by cost, speed, and health. Webhooks, idempotency, retry semantics, state machines, failure modes on the third retry, and provider failover that nobody notices. Payouts and collections. Getting sellers and borrowers their money faster than anyone else in this market: instant payout options, batch payouts at auction close, and the rail and timing choices that make them safe. On the other side, cash advance disbursement and the scheduled auto-pay batches that collect repayments run on your rails. The ledger team decides what a pending balance means; you decide how and when the money actually moves. Risk on high-value flows. The fraud, dispute, and chargeback posture for a marketplace where one bad transaction is a five- or six-figure problem. Holds, limits, and settlement windows set with data — and you'll know what each one costs in conversion. Step-up verification triggered by risk signals rather than blanket friction. Payment operations. When a transfer is stuck, a return code is unfamiliar, or a provider goes quiet mid-batch, you find out why. You'll own the tooling that lets operations and support answer "where is my money" without paging an engineer, and you'll feed clean, complete processor data to the ledger team's reconciliation so their breaks are real breaks and not missing webhooks. The posting contract, from the producer side. Every movement you originate lands in the ledger through a typed contract the ledger team owns. You'll build against it, push on it when a new rail doesn't fit, and guarantee exactly-once delivery into it. The trade-off calls. Shipping speed against uncompromising reliability; build custom versus buy an orchestration platform. You'll be asked to defend both directions. The team. Be a multiplier through rigorous code reviews, technical documentation, and mentorship. How You'll Use AI Here We don't want to hear that you use Claude every day. Everyone does. We want to know what you've built with it. Concretely, in this role: Turn a payment provider or bank partner integration spec into a typed client and a test suite in an afternoon instead of a sprint — including the ACH return codes and reversal paths nobody wants to hand-write Stand up a rail simulator that produces the failures a sandbox won't: a late return, a duplicate callback, a partial reversal, a webhook that arrives twice out of order, a settlement that lands after the window closed. Then run the orchestration layer against it Build an agent that watches provider health, webhook lag, and return rates, and proposes a routing change or a hold before the on-call sees the alert Put an MCP server over provider APIs and our payment state so "why did this payout fail" is a question support asks in plain language Use models to generate adversarial test cases for the orchestration state machine — the provider that acks and then times out, the failover mid-batch, the return that hits after the payout cleared — and find the transitions nobody specified Use Claude Code or Cursor as the default way you work through a provider migration or a refactor, not as autocomplete If you've built agents, wired up connectors, written skills or MCP servers, or shipped internal tooling your team actually depends on — lead with that. Name the artifact, not the tool. What You Bring 5+ years of experience with a heavy focus on backend systems — Python, Postgres, AWS. You've worked on real money movement. ACH origination and returns, RTP or FedNow, wires, or equivalent. You know what an R01 is, why NACHA return windows matter, and why a credit-push rail changes the product flow and not just the API call. You've integrated more than one payment provider in production, and you've lived through one of them failing. You've handled large transactions, where the failure mode is a five- or six-figure problem and someone notices immediately. You're API-native. Webhooks, idempotency, eventual consistency, and exactly-once delivery are your default vocabulary. Strong SQL and relational design. You know how to write a transaction that won't fail under load — including at auction close and during scheduled auto-pay batches. Marketplace or two-sided flow experience. Buyers and sellers, settlement between them, and the timing tension that creates. An obsession with reliability. You think deeply about idempotency, race conditions, and what happens on the third retry. Product-owner thinking. You don't just build a pay button. You understand the flow of funds and how to communicate financial status clearly to a user who is worried about their money. Pragmatism. You know when to build a custom internal solution and when to leverage a third party to get the job done. Strongly preferred: direct experience with Stripe, Plaid, Airwallex, PayPal, Modern Treasury, or Increase, and with evaluating or building a payment orchestration layer across more than one of them. Strong plus: fraud, dispute, or chargeback work on a marketplace; hands-on with risk tooling like Sardine, Sift, or Stripe Radar; enough React and TypeScript to ship the payment-method and payout surfaces you own. Bonus: distributed systems; stablecoin or on-chain settlement; KYC/KYB, bank partnership, or bank-sponsor program exposure; the alternative asset space. You collect, or you have a view on where this market is going. How We'll Interview You We'll be specific so you can prepare. Before any of it: download the app, put a card up, make a bid, and try selling — go through the workflows. Every round assumes you've used the product, and we expect your point of view to sharpen as you go. For this role, look specifically at the deposit, payment method, and payout surfaces. Recruiter screen — 25 minutes, Google Meet. Come ready to talk about the metric you own today and how you're performing against it, why Alt specifically, and how you're actually using AI. We'll answer your questions. Hiring manager — 45 minutes, Google Meet. Be ready to go deep on the provider integration or money-movement system closest to your own hands: what you built versus inherited, the trade-offs you made, and what you'd change now. Technical screen — 60 minutes. A hands-on working session on a rail behaving badly — duplicate and out-of-order webhooks, a late return, a provider that acks and then times out — and a payout batch that has to complete exactly once. Think out loud. Architecture and system design — 60 minutes. Design a payment orchestration layer under real constraints: two providers, failover mid-batch, instant and batch payouts, a risk hold on a five-figure transfer, and a ledger contract you don't control. We'll push back on at least one of your choices on purpose — how you take that matters as much as the design. Culture interview — 30 minutes. How you work with the people who depend on your systems — operations, finance, support, and the customer on the other end of a held transfer. Leore, our founder and CEO — 30 minutes. Everyone who joins Alt meets Leore. Come with a point of view on where you'd take Alt's money movement first. Reference check(s) — 15 minutes with a former manager(s). What we offer: For full-time Employees We cover 85% of your medical, dental, and vision, and up to 50% for dependents. HSA/FSA available Generous PTO that people actually take Parental leave at full salary $200/month wellness + $100/month home office stipend Free DoorDash Pass membership, because dinner shouldn't be a decision Remote-first (for most positions), with WeWork access when you want a room with other humans 401(k) Alt Equity to all full-time employees

Build and scale high-concurrency bidding and listing systems with AI-powered features for real-time auctions. | 5+ years experience with Python, Postgres, cloud infrastructure, React, TypeScript, and building reliable high-performance systems. | Alt is unlocking the value of alternative assets, starting with the $5 B trading-card market. We let collectors buy, sell, vault, and finance their cards in one place and we are backed by leaders at Stripe, Coinbase, Seven Seven Six, and pro athletes like Tom Brady and Giannis Antetokounmpo. Our next frontier is real-time pricing at scale—the Alt Value that powers every trade, loan, and product on the platform. The Role The last ten seconds of an auction are the whole product. Hundreds of people who have been watching one card for a week all arrive at once, every one of them refreshing, every one of them bidding. That's this job. You build and scale the high-concurrency bidding and listing systems behind nine figures of annual GMV, and you build the surfaces on top of them. Not one or the other. The low-latency backend logic that resolves a bid and the responsive real-time UI where a collector watches it land are the same feature, and they're both yours. The number this team is measured on: auction GMV. Every system here either moves it or protects it. What You'll Own: The auction engine. Build and scale the high-concurrency bidding and listing systems that power nine-figure annual GMV. Thundering herd in the closing seconds is a design constraint, not an incident. AI-powered liquidity. Develop the next generation of features that use AI to give consignors and sellers instant valuations and upfront liquidity. Being wrong here costs money, which is what makes it interesting. Personalized discovery. Use data and machine learning to match unique, one-of-one collectibles to the right buyers. Every item is a cold start; that's the problem. Power-seller tooling. Design and launch the management tools that high-frequency sellers and veteran hobbyists actually need. Watch what they do in spreadsheets today, then delete the spreadsheet. The whole experience. Backend bid resolution through the responsive UI where the action happens. You own the schema change and the screen it ripples out to. The bar. Mentor the team and set the standard for code quality, reliability, and performance. How You'll Use AI Here: We don't want to hear that you use Claude every day. Everyone does. We want to know what you've built with it. Concretely, in this role: Ship instant valuation into the consignor flow — take an Alt Value, a card's condition and provenance language, and recent comps, and produce an upfront liquidity offer a seller can accept in one tap. This is the flagship AI feature on this team, and it is user-facing Use vision and language models to enrich listings at scale: parse condition notes, extract attributes from listing photos and descriptions, and turn a messy long tail of one-of-one items into structured data a recommender can actually use Build a load-and-concurrency harness you can talk to — generate the closing-seconds bid storm, replay it against a branch, and get back where the write path bent, without spending two days wiring a load test Stand up an agent over auction telemetry that watches close windows and flags anomalies — bid latency creeping, a seller's listings underperforming their comps — before a power seller emails us about it Put an MCP server over listing, bid, and pricing history so "why did this lot close low" is a sentence, not another one-off query Use Claude Code or Cursor as the default way you work through a refactor or a migration, not as autocomplete If you've built agents, wired up connectors, written skills or MCP servers, or shipped internal tooling your team actually depends on — lead with that. Name the artifact, not the tool. What You Bring: 5+ years building and scaling complex applications — Python, Postgres, AWS or comparable cloud infrastructure. Modern frontend mastery. Deep experience with React, TypeScript, and building high-performance real-time UIs. Real-time is the operative word: this is not a CRUD screen. Reliability under pressure. A track record of building systems that stay up when the stakes and the traffic are highest. You've been paged during the worst possible ten minutes. AI pragmatism. You've taken LLMs or computer vision models and turned them into practical, user-facing features that solved a real business problem. Not a demo. Product instincts. You don't build what's on the ticket. You understand the collector mindset and build things that delight them — and you can explain the why behind past work before you explain the how. High agency. You thrive where you're expected to find the highest-leverage work and go execute it without a hand-holding manual. Bonus: experience with personalization engines, recommendation systems, or AI/ML integrations. Startup experience. You collect, or you have a view on where this market is going. How We'll Interview You We'll be specific so you can prepare. Before any of it: download the app, put a card up, make a bid, and try our selling feature. Every round assumes you've used the product, and we expect your point of view to sharpen as you go. For this role, actually sit through the end of a live auction. Notice what the UI tells you and what it doesn't. 1. Recruiter screen — 25 minutes, Google Meet. Come ready to talk about the metric you own today and how you're performing against it, why Alt specifically, and how you're actually using AI. We'll align on comp and answer your questions. 2. Hiring manager — 45 minutes, Google Meet. Be ready to go deep on a project you owned end to end — starting with the problem it existed to solve, then the design, then what was yours versus the team's, then the outcome. 3. Technical screen — 60 minutes. A hands-on working session on a concurrency problem close to what this role actually does. Think out loud. 4. System design — 60 minutes. Design the bidding path under real load. We'll push back on at least one of your choices on purpose — how you take that matters as much as the design. 5. Why Alt,- 30 minutes. Exactly what it says. Come with something specific. 6. Leore, our founder and CEO — 30 minutes Everyone who joins Alt meets Leore. Come with a point of view on where you'd take auctions first. 7. Reference checks — 15 minutes with a former manager(s) What we offer: We cover 85% of your medical, dental, and vision, and up to 50% for dependents. HSA/FSA available Flexible PTO that people actually take Parental leave at full salary $200/month wellness + $100/month home office stipend Free DoorDash membership, because dinner shouldn't be a decision Remote-first (for most positions), with WeWork access when you want a room with other humans 401(k) Alt Equity to all full-time employees