Tessel runs an AI-native process: you apply in your assistant, it helps you put your experience forward, and a named human reviews every decision. Using AI assistance is encouraged. You're evaluated on substance, never on whether you had help.
Add the careers connector (one time)
On claude.ai or the desktop app: Settings → Connectors → Add custom connector, name it Tessel Careers, paste this URL, and sign in when prompted.
https://tessel-retired.aiplayboox.com/careers
Start a new chat and say
I'd like to apply to the "Backend Engineer" role at Tessel. Their careers connector is at https://tessel-retired.aiplayboox.com/careers. Once it's connected, walk me through applying and help me put my experience forward well.
Or let the button type it for you:
Add the careers connector (one time)
In ChatGPT: Settings → Connectors → Advanced → Developer mode, then Create a connector named Tessel Careers with this URL (OAuth).
https://tessel-retired.aiplayboox.com/careers
In a new chat, enable it under Tools and say
I'd like to apply to the "Backend Engineer" role at Tessel. Their careers connector is at https://tessel-retired.aiplayboox.com/careers. Once it's connected, walk me through applying and help me put my experience forward well.
Or let the button type it for you:
The connector speaks MCP (Streamable HTTP + OAuth). Point your client at the URL below, authenticate, and the tools guide the rest.
https://tessel-retired.aiplayboox.com/careers
Backend Engineer
Tessel — Berlin or remote (Europe)
€75,000 – €105,000 · Full-time
About Tessel
We build the scheduling layer that logistics teams run their day on. Six
people, profitable since last year, no growth-at-all-costs nonsense. Our
customers move real things around real cities, so when our service is slow,
someone's van is idling.
The role
You'll own the services behind our scheduling engine: the API our customers
integrate with, the job runner that recalculates routes when the world
changes, and the data model underneath both. Today that's Python and
Postgres, with a Go service handling the hot path.
This is a small team, so you'll be close to the people using what you build.
Expect to talk to customers, and expect your decisions to stick around.
What we're looking for
that don't lock a table for nine minutes
engineer
Nice to have: Go, queueing systems, anything involving routing or scheduling
under real constraints.
How we hire
We keep it short and we tell you where you stand at every step.
1. Intro conversation with Nadia, our recruiter. Thirty minutes, live. What
you've built, what you want next, what we're actually like.
2. A written exercise, done in your own time. One real problem from our
backlog, roughly two hours. We pay for your time.
3. Technical conversation with Karim, who leads engineering. Live, ninety
minutes, walking through your exercise and one system you've run.
4. Team conversation. Live, forty-five minutes, with two of the people you'd
work beside every day.
5. Offer decision, made by Karim.
Every candidate gets an answer, whichever way it goes.
Applying
Tell us what you've built and why it mattered. We read everything that comes
in.
New to connectors? Read the two-minute candidate guide. Add the board to your assistant once, then apply to any role from chat.