Platform engineering
Rust, Go and TypeScript services across intent, admission, mediation, execution and evidence. Interest in distributed systems correctness rather than framework churn.
Careers
Build systems that can account for themselves.
NiGeNje is a small, evidence-led engineering effort building an intent- and invariant-governed control platform for autonomous and distributed systems. We care about correctness, honest boundaries and work that can be reviewed.
Current hiring status
We are not currently advertising paid roles.
NiGeNje is pre-product. Our immediate focus is platform integration, qualification evidence and design-partner work, not headcount growth. We would rather say this plainly than publish speculative vacancies.
We still welcome introductions from engineers and researchers who work on the same problems. Send a short note describing what you have built and what you think is hardest about governing autonomous action. There is no promise of a role or a response timeline.
Indicative areas
Where future roles are likely to sit.
These are areas of work, not open positions. They are listed so an introduction can be specific. Any future role would be advertised with its own scope and process.
Formal methods and λ-Safe
Type systems, contract compilation, decidable fragments and invariant-preservation research. Comfort with stating exactly what an analysis does and does not establish.
Security engineering
Identity, permits, replay protection, trust boundaries and evidence integrity. Interest in honest threat models over certification theatre.
Product design and technical writing
Enterprise control-console design, technical documentation and evidence-first communication for engineers and risk owners.
Solutions and architecture
Working with design partners to define invariants, bounded evaluations and the evidence a reviewer would need.
How we work
Evidence over assertion.
The product exists to make autonomous action reviewable. The engineering culture has to meet the same standard: explicit claims, explicit limits and records that another engineer can inspect.
- State the claim and the boundary in the same breath.
- Prefer the smallest control that actually enforces something.
- Do not present a simulation, a test or a diagram as production evidence.
- Write down what failed; an unresolved limitation is part of the design record.
- Keep interfaces narrow and records reviewable.
What this page does not offer
- No compensation bands, relocation packages or visa promises are stated here.
- No guaranteed response time or talent-pool retention period.
- No claim that a specific role exists today.
Contact details and how submitted information is handled are described in the privacy notice. Do not send sensitive personal data or confidential material in an initial introduction.
Introduce yourself
One specific problem is more useful than a generic CV.
Describe a system you built, a correctness problem you solved, or an invariant you struggled to preserve. The form below uses the same intake route as the rest of the site; if no receiver is configured it will say so rather than pretending to accept your message. Email is always available.
Prefer email? Write to george@nigenje.com.