Careers

Working at OctopusLab.

We're not actively hiring yet. We will be — and when we are, we want to hear from you.

Solo founder · pre-launchRemote, async, distributedEquity from day one
Why this place

Small team, real surface area.

Joining this early means owning entire products end-to-end and watching your decisions land in front of real users within the week. Here's what that actually feels like.

Ship code, not slides
Every team member commits to the same repo. PR descriptions and a working main branch are the artifacts that matter. We don't run a roadmap deck culture.
Async-first, time-zone agnostic
Long-form writing beats meetings. Two short syncs a week, the rest is heads-down. Work the hours that match your brain — we care about what landed, not when you were online.
Real ownership
Equity from day one and full autonomy over your surface. If you own the builder, you decide what ships in the builder. No three-layer approval chain to change a button.
Distance from process
No JIRA tax. No stand-up theater. A lightweight issue tracker, a chat channel, and a shared sense of what's broken this week. Process gets added when the lack of it actually hurts — not before.
What we'd hire for first

The first three roles — when the time comes.

None of these are open yet. We're publishing them so you know what we're building toward — and so we can have a real conversation if your shape matches one of them.

Full-stack engineer
Not actively recruiting

You'd own a vertical slice across Next.js, the NestJS API, and the Vercel Sandbox runtime that hosts user projects. Comfort with Postgres, queues, and reading other people's TypeScript is the bar.

Next.jsNestJSPostgres
Open to introductions and informal chats. Reach out — we'll remember.
AI / agents engineer
Not actively recruiting

LLM workflow design — prompts, tool definitions, evals, retries, the unglamorous parts. You've shipped something agentic in production and have opinions about what breaks at scale.

LLMsAgentsEvals
Open to introductions and informal chats. Reach out — we'll remember.
Designer-engineer
Not actively recruiting

Tailwind, product sense, and a high bar for the small things — empty states, focus rings, motion that earns its keep. You design in the codebase, not in Figma handoffs.

TailwindProduct designTSX
Open to introductions and informal chats. Reach out — we'll remember.
Don't see your shape on the list? If you'd genuinely move the product forward and we'd be foolish not to talk, write anyway. The list is a starting point, not a fence.
Get in touch

If this resonates, write to us.

Include a paragraph about you, a link to something you shipped, and the one part of OctopusLab you'd improve first. Short emails get faster replies than long ones.

careers@octopus-lab.appLearn about the team
What to include
  • A paragraph about you. What you've been building, what you want to build next, where you are in the world.
  • Something you shipped.A repo, a deployed URL, a PR you're proud of. Code we can read beats a CV.
  • The one thing you'd fix on OctopusLab. Open the product, find a rough edge, tell us what you'd do. This is the part we read first.

We read everything. We don't always reply within a day — sometimes a week — but a real human will. If we're not the right fit right now, we'll say so directly instead of going quiet.