Production-grade, always
The standard does not drop because the work is internal or unpaid. Decisions get written down, and a shortcut gets named as a shortcut instead of quietly becoming the design.
Careers
Small, senior, and growing deliberately.
We grow deliberately rather than quickly. This page carries no open roles, no pipeline of filler postings, and no team page describing people who are not here. When that changes, it changes here first.
01: How the work runs
What you would be joining.
Stated as the work runs today. These are the properties worth keeping through growth, which is also the reason growth is slow.
Direct ownership
No layer of process between deciding something and shipping it. You would work directly with the person accountable for the outcome, because there is nobody in between to route it through.
No bureaucracy
Meetings are rare and decisions are same-day. That is the actual draw, and it is the first thing scale would cost, which is why headcount is not the goal.
02: The conditions
Where and how the work gets done.
Not benefits, and not a description of how the work might run later. These are conditions that hold today, which is the only reason they are worth printing.
Remote-first
Nothing about the work is tied to a location. It runs remotely, and nothing about how it runs assumes a shared timezone, so where you are is not a filter on whether the work would fit.
Hours are not the measure
Nothing counts attendance. What gets judged is what ships and how well it holds up under someone else reading it, not when it was written or how many hours went into it.
Tools of your choice
Use whatever setup makes you productive. Linux is the preference here, and it is what the systems work is built on, but it has never been a requirement for doing good work.
03: Direction
Who comes next.
Read this as the order the company expects to grow in, not as a plan with dates attached to it.
Nothing below is budgeted, scheduled, or being interviewed for. It is where the first hires would go if and when revenue supports them.
Engineering
A second pair of hands on delivery, senior enough to own a system end to end rather than a ticket queue.
Finance
Books, compliance and the statutory filings a registered company accumulates. Currently handled around the engineering, which does not scale.
Marketing
Distribution for work that is already real. Not a growth function inventing claims the engineering cannot back.
04: Open roles
None right now.
When a real role exists it lists here with its scope, its range and who it answers to. Until then this stays empty on purpose.
No open roles
There is no posting to apply to, and there is no waitlist collecting addresses behind one.
Send your work anyway05: The bar
What the standard is.
The standard the work is held to today, written down so a speculative application has something concrete to measure itself against instead of guessing.
- Self-directed, with writing strong enough to carry a decision without a meeting behind it.
- Genuine interest in Linux, systems and craft: the layer under the abstraction, not only the framework sitting on top of it.
- Code or design another engineer can extend without archaeology, documented wherever the reasoning is not readable off the thing itself.
- Comfortable working async, where a reply lands in hours rather than seconds and the work does not stall waiting on one.
- Intellectually honest about what you do not know, and fast to say so rather than to guess in public.
06: Speculative
Nothing open, but you are exceptional?
Send the work itself, a repo, a system you built, something you shipped, rather than a CV. Good people get remembered for when a role does open.