EngineeringSenior Software Engineer

Own the path from "make me an app" to an icon on a phone: the app MCP an assistant calls, the checks every app passes, and the host that serves it.

All open roles
Function
Engineering
Region
Remote
Type
Full-time
Experience
5+ years
Apply for this role

About the role

CloudCrane lets a person ask their assistant (Claude, ChatGPT, or any that connects to MCP) for a small app (a habit tracker, a spending log, a packing list) and have it land on their phone's home screen. The assistant writes one HTML file and publishes it through our MCP server; we check it, keep every version, and serve it at its own address, where it installs, opens full screen and works offline. What the person saves stays on their phone.

This role owns whole slices of that, not tickets. You'll take something that is still a sentence ("an update must never lose what someone saved") through the MCP tools, the service, the database, the apps host and the tests until it holds on a real phone.

What you'd do

  • Build and extend the app MCP: the tools an assistant sees, what each grant may do, and the errors that tell an assistant how to fix what it sent
  • Own the checks an app passes before it's published, and the warnings kept with each version
  • Keep the apps host honest: one answer per address, worked out once and served the same here and at the edge
  • Build the runtime library every app is written against (planned): saved data that survives every update, with export and import
  • Review others' work for correctness, races and the failure modes a passing test suite misses

What we need

  • Five or more years building production backends, with real ownership of something that had users
  • TypeScript at depth, or another statically typed language you'd pick this up from quickly
  • Strong SQL, and a reason for every place you'd enforce a rule in the database instead of in code
  • You write tests as part of building, and can say what each one would catch
  • You've debugged a race condition in production and can describe how you proved the fix

Nice to have, not required

  • You've built against the Model Context Protocol, or another protocol strangers' clients call
  • Progressive web apps, service workers and their update edge cases
  • Cloudflare Workers or another edge runtime

How we work

  • Small team, thin slices, shipped weekly. Nothing sits on a branch for a month.
  • Reviews are real. Every feature ships with its tests, and a bug found in review is cheaper than one found by someone using it.
  • Private by default. A person's app data stays on their phone, and nothing we build may need to read it.
  • We only claim what ships. That applies to the product, the roadmap and the offer letter.

How hiring works

  1. 1A 30-minute call about something you've built and what was hard about it.
  2. 2A working session on a real problem from this codebase. You can drive, or we can pair.
  3. 3A conversation about how you make decisions when the evidence is thin.
  4. 4References, then an offer. We aim to answer within a week at every stage.

Apply: Senior Software Engineer