Full Stack Engineer

Why Indemni, why now?

Every year, $20T of U.S. freight changes hands on the strength of a paper Bill of Lading and a quick nod at the dock door. When thieves strike, a $250k load can vanish in minutes.

Indemni is turning that soft underbelly of global trade into a strength. We’re shipping the first real-time identity & document verification platform purpose built for logistics. Think Stripe’s risk engine, but for cargo moving through warehouses, ports, and yards all over the world.

Started by operators from Flexport and DoorDash, we’re already piloting with warehouses and carriers across the US who move some of the most valuable cargo between warehouses, airports and ports (think national security level importance such as server racks, GPUs, electronics, etc.).

What you’ll do

• Own green-field architecture. Lay the rails for high volume, low latency verification products in a domain that has zero tolerance for downtime or mistakes.
• Ship product at speed. Prototype, iterate, and push to production weekly alongside the founders. Your code will literally decide whether a million dollar load gets released.
• Set engineering culture. Define our bar for code quality, security, and documentation. Choose the tools, conventions, and rituals future hires will follow.
• Think like a founder. Jump from backend to mobile, from white-boarding a new risk-scoring model to debugging our warehouse app. If it helps customers sleep at night, it’s in scope.

Our stack

JS+TS / React / React Native (Expo) / Node/Express / Supabase (Postgres + Edge Functions) / Python (ML)

How we think about hiring (ranked from most important to least):

• Bias for action. “Ship > perfect” resonates, but you still write the unit test (the stakes are high)
  • Example: Warehouse has a new requirement for verifying Hazmat documentation in the check-in flow. How fast do we get that live?
• Product intuition. You ask why before how, and think first and foremost in problem statements (what problems am I solving and is this a problem worth solving?)
  • Example: Freight Broker is asking if we can auto-translate documents into different languages. Is this something we prioritize now based on why we think this is important, and how do we fit this in our roadmap and the way we build in the future?
• Comfort everywhere in the stack. Wrangling SQL in the morning, and debugging API logs in the afternoon are a breeze for you.
  • Example: Driver is having trouble checking into the app. How do we handle a live edge case of a driver using a flip phone in 2025?
• 5+ yrs building distributed systems in Node/Express, serverless, or similar. 
  • Example: If we’re handling X number of verifications a day, what should our short-term, medium-term and long term stack look like and how do we balance that against intensive vs. non-intensive tasks (i.e. pinging APIs for verification vs. lookup government databases for compliance).
• Nice-to-haves: Logistics, WMS/TMS, Fraud/Risk ML experience, computer-vision pipelines, or hardware-adjacent experiences (RFID, scanners, etc.).
  • Example: If you’ve ever heard of Extensiv or a scanner gun before.

What’s in it for you

• Build an industry-defining company at the zero-to-one stage. Your code, your fingerprints on every decision.
• Hardware-meets-AI playground. From OCR to edge devices at docks, the problems are meaty and uncharted. 
• Real-world impact. Prevent million-dollar thefts, protect supply chains that stock everything from national security products to eggs at your local grocery store.

Logistics:

• Location: Financial District, San Francisco. We’re a hybrid team, which means whiteboards, driving to the warehouse together for customer visits when needed, and free lunch and dinner for when we work late.
• Process: Intro chat → onsite pair-build (<1 hour) →  founder coffee → offer. We move fast.

Benefits

• Medical, dental & vision insurance
• Unlimited PTO
• Hybrid-work environment
• Gym Stipend