Careers
Not hiring yet. Say hi anyway.
There are no open roles at CodeMorph today. But if building trustworthy developer tools sounds like your kind of problem, we'd like to know you before we're looking.
The work
What we'll need, eventually
Compilers and static analysis
Parsers, module resolution, type systems, and graphs that stay correct on messy real-world code.
Editor engineering
Deep work inside a Code - OSS based desktop app: performance, UX and the patch set that keeps it current.
Applied AI
Context selection, repair loops and evaluation for model-driven code changes that have to be right.
Developer experience
Docs, onboarding and design that make a powerful tool feel calm.
How we work
Small, careful, remote-friendly
- We write things down. Decisions, trade-offs and known debt live in the repo, not in someone's head.
- We ship in small, verified steps, the same way CodeMorph migrates code.
- We're based in Lagos and happy to work with great people anywhere.
Values
What we care about
Proof over promises
We verify our own work the way CodeMorph verifies migrations: with tests, measurements and honest write-ups.
Craft
Developer tools are judged in the details. We sweat the edge cases, the error messages and the empty states.
Ownership
Small team, big surface. People own outcomes end to end, from design to the changelog entry.
Honesty
With users, with each other and in what we ship. If something isn't ready, we say so.
When we hire
How it will work
So you know what to expect, before there's a role to apply for.
- 01
An open role, written plainly
What the work is, who it's for, the salary range and where you can work from. - 02
A conversation
About what you've built, what you want to work on next and what you need to do your best work. - 03
Real work, paid
A short, paid project close to the actual job, instead of a whiteboard puzzle. - 04
A quick decision
We'll respect your time and give you a clear answer with reasons.
Introductions
What to send
When you introduce yourself below, the most useful things to include:
- · Links to things you've built: repositories, products, writing or talks.
- · The part of CodeMorph you'd most like to work on, and why.
- · Where you're based and how you like to work.
- · Anything you'd change about CodeMorph after trying it. Honest critique is welcome.
Introduce yourself
A few lines about what you've built and what you'd want to work on. Links welcome.