Backend Engineer

We are seeking a talented and curious backend Engineer to join our team as a backend developer. The ideal candidate will have strong experience in cloud and services, with a focus on large cloud, edge compute, and data transfer across multiple network protocols. Experience with containerized development and cloud-to-edge development patterns is highly preferred.

We need a backend engineer who's actually comfortable at that cloud-to-edge boundary, not just someone who's shipped CRUD APIs behind a load balancer. You've built and run real services in production, you think in terms of protocols and failure modes, not just endpoints, and you're the kind of person who'd rather spend an afternoon figuring out why a connection drops under load than write it off as a flaky network. We're a small, fast-moving team, so we need someone who can own a real piece of this without a lot of hand-holding, but who also wants to learn from people around them, this isn't a role for someone who already has it all figured out.

• Designing and building backend services that move data reliably between our cloud systems and edge/device environments, across more than one network protocol

• Containerizing and deploying services that need to run consistently whether they're in the cloud or out at the edge

• Working directly with the engineers building the physical and product side of things to figure out what the backend actually needs to support

• Digging into real production issues (latency, dropped connections, data consistency across unreliable links) and fixing the root cause, not just the symptom

• Improving and hardening systems that are already live, not just greenfield work

You're not building backend services that live in a clean, fully-online world and call it done. The systems you build here have to keep working when the network doesn't cooperate, because they're often talking to something physical and real, not just another service in the same data center. You'll work directly with the engineers and teams building that physical side, with nothing in between, no layers of approval to get through to ship something.

• 3 to 5 years of backend experience building and running large-scale, in-production services

• Strong hands-on experience in Java, Python, or Kotlin (comfortable moving between at least two of these). Any other languages are welcome too.

• Real experience with cloud services and edge compute, and with moving data across multiple network protocols

• Experience with containerized development, and ideally with cloud-to-edge deployment patterns specifically

• Comfortable with agile ways of working and continuous integration, not because a process says so, but because it's how a small team actually keeps shipping

If you want a clearly scoped ticket queue and a manager checking in on progress, this isn't it, there's no layer between you and the decision. If you need the whole system mapped out before you'll touch an unfamiliar protocol or an edge-case failure, that'll be a tough fit here. And if you're looking for a remote, keep-to-yourself setup, we're an in-person team by choice, and that's part of what makes this work.