2 min read

25 Questions Your Eng Onboarding Should Answer

The quickest way to onboard to a new system in lieu of detailed docs or any semblance of an onboarding program is........ asking questions. Peruse my list of 25 questions your engineering onboarding should cover
25 Questions Your Eng Onboarding Should Answer
"And that, gentlemen, is SCRUM." - Silicon Valley

As someone who attended 7 different schools before high school and uh have hopscotched my way around several different companies during my career I'm something of an expert beginner and have found the quickest way to onboard to a new system in lieu of detailed docs or any semblance of an onboarding program is........ asking questions.


Here is a sampling of questions your engineering onboarding should cover - this is not exhaustive and fairly generic high-level but should give you a nice springboard for bringing an engineer up to speed.

  1. How many environments are there between local dev and production?
  2. What is the state of service ownership here? aka the line of responsibility between developers and operators
  3. How to deploy?
  4. How to rollback?
  5. How to file bugs?
  6. What are the custom in-house tools? Does everyone have contributing rights to them?
  7. How do we measure the customer experience? the health of the system?
  8. What is the path a request takes from the edge to a particular instance of a service?
  9. What is a typical traffic pattern for the product/platform? Are there any peak traffic days (a la 4/20 or Single's Day)
  10. Who are our primary customers?
  11. What does a production app instance consist of - container? orchestration? hardware?
  12. What version of language/framework are we running? How to check?
  13. Do we load test?
  14. How are features deprecated?
  15. What is the local development situation?
  16. What is the process to spin up a new datastore?
  17. Do we routinely pen test? Scan for vulnerabilities?
  18. How big is the on-call rotation?
  19. Is the primary on-call expected to take on sprint work?
  20. Who are the biggest customers in terms of usage/load/importance?
  21. What visibility does the Support team have into production?
  22. How do we build Docker images and what registry are we using?
  23. Are there communities of practice aka SIGs aka Brown Bag sessions?
  24. How do we fund projects for "unowned" communal tooling and libraries?
  25. How do we attribute financial cost of running services?

Any questions I missed? Let me know!


CAT TAX

bb Norman turkeyed on a chair next to an alligator plushie that is dwarfing him

Happy onboarding!

paigerduty