Responsibilities
- Build real features alongside our engineers, with guidance, not hand-holding
- Learn how a multi-tenant platform actually works under real load
- Get your hands dirty with the messy stuff: why a container died, why a queue backed up, why something broke for one tenant. You won't fix it alone at first, but you'll learn how we do
- Prototype ideas fast, then learn what it takes to make them production-grade
- Sometimes sit in when we talk to customers, so you learn the problem before you write the solution
Requirements
- You use AI to code. Claude, ChatGPT, whatever helps you learn and move faster. We expect it, not tolerate it.
- But you're not satisfied just copying what the AI gives you. When it hands you code, you want to understand why it works. You're curious about the layers underneath: message queues, containers, how services talk to each other in a real system. You don't need to know all of this yet. You need to want to.
- You debug by trying to understand, not just pasting the error back into a chatbot and hoping.
- You take ownership of what you're given, even when it's hard.
- You've built side projects, joined hackathons, or shipped something nobody asked you to build. That initiative tells us more than your grades.
- You've tried starting something of your own, even if it went nowhere. We respect people who try.
- We build on NestJS and Next.js. If you already know them, great. If you know something close and can pick these up fast, that's fine too. We care that you can go deep, not that you memorized our exact stack.