Scope before build
Every engagement starts with an agreed brief and boundary. Internally that means writing things down — decisions, constraints, reasons — instead of relying on memory and momentum.
Build with us.
From the ground floor.
JUHENZA is a founder-led technology studio in its early chapter. There are no open roles to publish yet. Learn how we work and introduce yourself before a role exists.
How the work
actually runs.
The same principles we bring to client projects, applied inward.
Open by design
Everything built is intended to be open source, with the business in the work around the code: custom development, managed hosting, support and training. Working here means building things in public, deliberately.
Ownership stays with clients
Deployment access, documentation and handovers are part of the work. The craft standard is simple: the people who inherit what you build should never need you to keep it running.
No roles to apply
for yet.
When project volume justifies a first hire — most plausibly in software or AI engineering — the role will be described here first, with real scope and expectations. Introductions are still welcome. Messages reach the founder directly.
While you are here.
Good work starts
with a conversation.
Introduce yourself with the work you want to do and something you have built. If a fit appears later, this is where it starts.
Email the founder