Documentation.

Transparency from the inside out.

How We Work

Lethal Labs operates as a distributed, highly autonomous, asynchronous firm. We do not track hours. We do not micromanage. We measure output via git commits and deployed features.

Our primary focus is divided into two areas: sustaining our proprietary SaaS products (which generates capital) and continuously donating high-performance primitives to the open-source community as public goods.

How To Become an "Insider"

"Insiders" are the core maintainers and staff engineers forming the backbone of Lethal Labs. We rarely hire through traditional interviews. Instead, we use an open, meritocratic approach.

  1. Phase 1: Contribute (Open Source). Find one of our public repositories on GitHub. Fix a bug, optimize an algorithm, or submit an RFC for a feature. Prove your capability through PRs.
  2. Phase 2: Establish Context. After consistent high-quality contributions, current Insiders will grant you triage permissions. Engage in code reviews architecture discussions.
  3. Phase 3: The Invitation. Once consensus is reached among the core team, you will receive a formal invite to join Lethal Labs, granting access to private SaaS repos and corresponding compensation.

Already an established engineer?

If you have a strong portfolio or a track record in system architecture, you may bypass Phase 1. Request an immediate technical assessment by emailing dramrxt@proton.me with a link to your GitHub profile.

Architecture & Standards

Before submitting PRs, ensure you have read our core engineering guidelines available in our GitHub repository Wiki. The wiki covers:

  • Performance benchmarks and latency upper-bounds for new features.
  • Strict linting and styling (Prettier/ESLint configs for JS/TS; Rustfmt for Rust).
  • Design system primitives and CSS variable naming conventions.