Builder

Job description

Job responsibilities

• Own products, not tickets. Take a problem from "we heard this from customers" to "it's live in 4,000 locations." You decide what to build, how to build it, and when to ship.
• Talk to customers. Visit kiosk deployments, sit with operators, watch transactions happen, and understand pain points firsthand — not through a requirements doc.
• Design the experience. Sketch UIs, prototype interactions, and make product decisions. You don't need to be a trained designer, but you need taste and empathy for the person standing at the kiosk.
• Build simple MVPs and ship them quickly from 0 to 1. Dream up new architecture to solve challenging problems. Rethink and recreate existing codebases for scale.
• Write great code. Full-stack: React/TypeScript for kiosk UIs and dashboards, Python for backend services and ML pipelines, C++ for on-device inference.
• Build with AI. Use LLMs, copilots, and AI development tools to move at 10x speed. Understand how to leverage AI models in production — not just as toys.
• Solve hard problems at the intersection of hardware and software. Work with a small interdisciplinary team in hardware, software, and design to build new versions of products from scratch.
• Support what you ship. When something breaks at a customer site, you feel it. Continuously improve and maintain code that's already in production.

Job requirements

• You're a builder at heart. You'd be building software even if nobody paid you. You have side projects, open source contributions, or a startup in your past (or future).
• You're deeply technical. 5+ years shipping production software. Excellent knowledge of one or more of: Python, Node.js , C++, Go, C#, Java.
• You think like a product person. You don't just ask "how should I build this?" — you ask "should we build this at all?" and "what would make this 10x better for the user?"
• You have taste. You care about the details — the animation speed, the error message copy, the API naming convention. Craft matters.
• You move fast. You bias toward action. Ship MVPs, get feedback, iterate. You'd rather have something in front of users in a week than a perfect spec in a month.
• You're comfortable with ambiguity. We won't hand you a fully-specced PRD. You'll figure out what the right thing to build is, often with incomplete information.
• You use AI as a multiplier. You're fluent with AI-assisted development tools and understand how to use LLMs to accelerate your workflow — from code generation to prototyping to analysis.
• You can go start a company. This is the litmus test. If you could credibly do every job at a startup — engineering, design, product, customer support — you're the kind of person we're looking for.