Fill in the recruitment form, tell us which role interests you, and start on something that is already open.
Dead Pixels runs on volunteers. Every role listed here is open, and none of them expect a portfolio or a computer science degree. Tell us what you want to work on and how much time you realistically have.
How it works
Fill in the recruitment form. It asks which role interests you, what you have worked on before if anything, and roughly how much time you can give. There is no test and no interview panel.
We reply by email and point you at something that is already open. Both projects have stages nobody has claimed yet, so there is usually a small first task available in whichever area you picked.
Work happens in the open. Every change is read by someone else before it lands, and scope creep and quiet data collection are the two things reviewers look for first.
Recruitment form
One short form. Pick a role, say what interests you and roughly how much time you have, and we will follow up by email.
01Roles we are looking for
- 01 Developer / Programmer Pick an unclaimed stage on either roadmap. Editor tooling, debugging, package management, desktop shell.
- 02 UI / UX Designer Interface layouts, interaction patterns, and the design language both projects are built on.
- 03 Graphic Designer Icon sets, wallpapers, boot screens, and the visual identity around each project.
- 04 Researcher Dig into prior art, privacy behavior in existing tools, and what people actually need from them.
- 05 Documentation Writer Install steps, guides, and plain explanations of how a system works. Worth as much as the system itself.
- 06 Tester Run early builds on machines we do not have and file precise reports when something breaks.
- 07 Community / Social Media Run the accounts, answer questions, and get the work in front of the people it was built for.
- 08 Project Planner Keep the roadmaps honest, track what is in progress, and hold scope to the five values.
04How work happens
Open development, written down
There is no private roadmap and no internal decision log. This is the whole process, and every step of it happens where you can read it.
Proposed in public
Ideas start as a written issue with the reasoning attached. If the argument is weak, it is easier to see it early.
Built in the open
Work happens in public branches. Anyone can watch it take shape, and anyone can pick up a stage that has stalled.
Reviewed together
Every change is read by someone else. Scope creep and quiet data collection are what reviewers look for first.
Shipped and documented
Nothing is finished until someone who did not write it can install it, use it, and explain what it does.