Skip to main content

Day 1 - Day 3 Onboarding (Junior Fast Track)

Quick Summary

Target 3 for today: juniors can read the main flow, understand the risks, and safely handle light maintenance tasks. Focus: understand first, then execute.

🎯 Final Outcome (Day 3)​

  • Can explain the flow SPB → PO → Payment without looking at the code.
  • Can map small changes to affected files/modules.
  • Can carry out pre/post change verification with a checklist.
  • Know when to escalate (don't be reckless in high-risk areas).

Day 1 — System Orientation​

Focus​

Understand the system map and core terms.

Required reading​

  1. Overview
  2. Architecture
  3. Domain Model
  4. Business Flows

Practice​

  • Make 1 page notes: "Who are the main actors + most critical status".
  • Mark at least 3 areas that are still ambiguous to the Verification Matrix.

Exit criteria Day 1​

  • Can answer: which roles can approve SPB/PO/payment.

Day 2 — API & Data Safety​

Focus​

Understand how to read endpoints + impact on database.

Required reading​

  1. API Reference
  2. API Examples
  3. Database Viewer
  4. Change Data Playbook

Practice​

  • Trace 1 endpoint from route → controller → impact data.
  • Write 1 draft of a simple rollback plan.

Exit criteria Day 2​

  • Can explain the impact of API changes to UI and data.

Day 3 — Operational & Incident Readiness​

Focus​

Practice safe maintenance flow and technical communication.

Required reading​

  1. Onboarding Checklist
  2. Common Maintenance Tasks
  3. Troubleshooting
  4. Deployment Runbook

Practice​

  • Simulation of 1 maintenance task + 1 rollback scenario in staging.
  • Write a short handover note (task, impact, verification, rollback).

Exit criteria Day 3​

  • Can execute low-risk tasks with minimal supervision.

Red Flags (Must Escalate)​

  • Touching final payment / financial approval.
  • Schema changes without senior migration review.
  • Runtime is different from docs assumptions (see VM-* in matrix).
  • Incident > 60 minutes without clear root cause.

Verification Notes​

  • Status: Partial
  • Scope: The learning path has been prepared, the actual duration of onboarding may vary depending on the baseline engineer.
  • Action: After 2-3 batches of onboarding, update time estimates based on actual data.