Software Engineer
Akia is the AI agent for hospitality. Hotels and vacation rental managers hand her guest communication and the day-to-day work: check-in, upsells, guest requests, staff dispatch. She handles it across text, web, and email. Thousands of properties run on Akia today. We're venture-backed, founded by a team of ex-Meta engineers and operators. We're hiring software engineers. Akia runs real operations for real properties, so a bug has consequences and a good week is obvious from the outside. You'll ship to production in your first week. The team is small, which means there's nobody to hand a half-finished problem to. You'll pick up something ambiguous, decide what it should be, build it, and watch it run. You'll also be building an agent while working alongside one. A lot of our code is written with Claude, and the engineers who move fastest here treat that as a craft rather than autocomplete. You need to be genuinely fluent with these tools yourself. Reading about them doesn't count. What you'll own. Features end to end. The schema, the API, the interface, the deploy, and whatever breaks at 2am. The agentic loop itself. What Akia can see, which tools she's allowed to call, and how she decides. Integrations with the property management systems the whole product depends on. Mews, Cloudbeds, Hostaway, Guesty, and dozens more, each with its own idea of what a reservation is. Evals. Changing an agent without a way to measure whether she got better is guessing, and we'd rather know. Production. You're on call for what you build. What we're looking for.3+ years writing production software, with real ownership of something that shipped and had users. Strong TypeScript and comfort across the stack. React and Next.js on the front, Postgres behind it. You make product calls. When the spec is thin you'd rather ask two questions and build than wait for a document. Real hands-on fluency with LLMs and agents. You use Claude or ChatGPT every day for actual work, you treat prompting as a craft (context, instructions, examples, iteration), and you've built something with these tools. Bachelor's degree or equivalent experience. Nice to have. You've shipped an LLM feature to production and dealt with what comes after. Latency, cost, evals, the model changing under you. Telephony, real-time audio, or messaging infrastructure. Hospitality technology background. Why this role. Small team, real users, and a product where the AI is the product. You'll see what you built running at thousands of properties, and you'll hear about it fast when it's wrong.