← All open roles
You will own features end to end — schema through API through interface — across client projects in e-commerce, logistics, health, and internal tooling. Expect direct client contact and real say in technical decisions. Expect also that nobody will hand you a fully specified ticket; a good part of this job is turning a vague business problem into something buildable.
What you’ll work on
- Production web applications in React and Next.js, built for real traffic and real SEO requirements
- Node.js services and APIs, plus the relational data models underneath them
- Deployment and CI/CD on AWS or Azure — you ship your own work rather than throwing it over a wall
- LLM-backed features: retrieval, structured extraction, and workflow automation wired into systems that already exist
- Reviewing other engineers’ code and setting the standards we hold each other to
What we need from you
- Several years writing JavaScript and TypeScript professionally, with the judgment that comes from having maintained what you built
- Real depth in React, and production experience with Next.js — server-side rendering, routing, and the rendering trade-offs between them
- Node.js backend work: API design, authentication, error handling, and database access you can reason about
- SQL fluency, including the ability to spot a query that will fall over once the table gets large
- Comfort deploying to a cloud provider and debugging the class of problem that only appears in production
- Clear written English — most of our collaboration is asynchronous and in writing
Helpful, not required
- React Native or Flutter
- Hands-on LLM or AI integration work beyond the tutorial stage
- Docker, infrastructure-as-code, or observability tooling
- Agency or client-services background — you already understand how scope moves mid-project
How we work
Remote, asynchronous by default, with overlap when a client call needs it. You will have context on why you are building something, not just what to build. Code review is a conversation rather than a gate, and we would rather discuss an approach before a week goes into it than after.
How to apply
Send your CV plus something you have built that you are willing to talk through in detail. A repository, a live URL, or a short write-up all work equally well. Tell us what the hard part was and what you would do differently now — that tells us considerably more than a list of technologies.
Apply for this role