Developer Experience Engineering.

Build times, local dev loops, error messages, docs-as-code, tooling UX, platform DX, cognitive load, onboarding speed. Covers 8 sub-skills.

• Developer Experience Engineering · 1 of 3

  Time-to-first-commit for new engineers

  Comparing a buddy system vs a static onboarding doc, what does the buddy system primarily add for a new hire?

  AA guaranteed reduction in the size of the production codebaseBA live channel to unblock implicit knowledge gaps quicklyCA formal sign-off process for every internal architectural decisionDA replacement for any structured code review on first pull requests

• Developer Experience Engineering · 2 of 3

  Inner-loop iteration speed

  DevEx survey: 'I can run a realistic test of my change locally' = 41%. Logs show devs hand-curl staging APIs from local frontends. Which platform investment moves the needle?

  AA nightly synthetic load test report posted in the team channel dailyBA bigger CI matrix that runs every commit across more node versionsCPer-PR ephemeral environments wired to seeded backing servicesDA read-only mirror of production data exposed to every laptop directly

• Developer Experience Engineering · 3 of 3

  Cognitive-load-aware API design

  A platform team adds a config DSL with 38 keys, 12 of them required. Engineers report 'I copy-paste from the nearest service and pray'. The cognitive-load-aware redesign should:

  AGenerate the config from a wizard that prompts for each of the 38 keysBProvide a linter that flags every config which omits a recommended keyCAdd a JSON schema so editors autocomplete the 38 keys with descriptionsDAdopt sensible defaults so most services declare 0 or 1 keys explicitly