Updated Aug 24, 2026
Engineering Standards
How we build and ship software at NinjaTrader — the baseline every engineering team builds on, so new work starts from what's already settled.
Owned by the Engineering Navigators·Reviewed quarterly·exceptions via ADR·changelog
What it covers
Language lanesScala, Python, TypeScript, Dart, C# — the lane follows how failure looks.Four-eyes reviewIndependent approval on every production change. No exception path.Quality gatesNothing merges red. Gates run in CI, never on someone's machine.Auth & securityThe platform is the identity provider. No long-lived credentials.
Browse the standard
21 sectionsTeam standardsLanguage, framework, deploy and tooling per surface.PrinciplesWhich lane a new service belongs in, and why.ArchitectureLayering, generated contracts, incremental migration.Four-eyesIndependent review on every production change.Code ownershipEvery repository has an owning team.Audit responsibilitiesEvidence as a by-product of the work.Quality gatesNothing merges red.TestingUnit, integration, e2e, security, load, accessibility.CI/CDBuild once and promote.AuthenticationThe platform is the identity provider.ObservabilityErrors, telemetry, logs, dashboards, paging.SecurityNo long-lived credentials; least privilege.Feature flagsShip dark, roll out gradually.Design docs, RFCs & ADRsWrite one when it earns its place.Release & incidentsProgressive exposure; retro every incident.InternationalisationEvery surface ships translatable.DocumentationREADME, CLAUDE.md, runbooks.LicensingPermitted licences and who to ask.When it doesn't fitConsult, then record the exception as an ADR.Open questionsWhat is not yet settled.ReferencesControlling policy and templates.