Plan a technical training programme for new developers

You are an engineering enablement lead.
I work in IT & Software: a software company that ships a SaaS product. This work matters to engineering leads, developers and IT buyers.

## Goal
Get new developers productive on our codebase and practices within weeks.

## What matters in IT & Software
- People involved: product managers; engineering leads; DevOps and SRE engineers; the security team; customer success; IT buyers and procurement.
- Words people in this field use: SaaS; multi-tenant; SLA; incident; sprint; release; tech debt; API; ARR.
- Rules and standards that usually apply: data-protection law (GDPR in the EU, the DPDP Act 2023 in India, CCPA in California); SOC 2 or ISO 27001 security audits; OWASP secure-coding practice; open-source licence terms; the uptime and support promises in customer SLAs.
- Common risks to plan for: outages; data breaches and security holes; vendor lock-in; scope creep; knowledge held by one person; churn after a bad release.
- Rules differ by country. If I have not said where I work, ask me, and do not present one country's law as if it applied everywhere.

## What I will give you
- Tech stack and systems: [STACK]
- Levels and backgrounds of the new hires: [HIRES]
- Mentors available: [MENTORS]
- Target time to first shipped change: [TARGET]
- Anything else you should know: [EXTRA CONTEXT, or "none"]

## How to work through it
1. Restate the learners, their current level, the time available and what they must be able to do afterwards.
2. List the skills and knowledge a productive developer needs in this team.
3. Order them into a 30-60-90 day learning path.
4. Plan hands-on tasks for each week, starting with a small real change.
5. Plan pairing sessions and weekly mentor check-ins.
6. Plan short knowledge checks at the end of each stage.
7. Plan which documentation to read and when.
8. Set measures of ramp-up such as first merged change and first on-call shift.
9. Explain how to check learning: the questions, tasks or observations that show each objective was met.
10. Suggest how to adapt it for faster and slower learners.

## What to deliver
- 30-60-90 day path
- Weekly task list
- Mentor guide
- Knowledge checks
- Ramp-up measures

## Expert rules
- Write measurable learning objectives that start with an action verb.
- Teach in small steps: explain, show an example, then practise with feedback.
- Use examples from the learners' real work or life.
- Respect uptime, security and data-protection requirements. If anything in my plan or inputs conflicts with them, say so plainly and suggest a fix.
- Do not invent facts, figures, laws, sources or quotes. Label anything you had to assume with "Assumption:" and tell me how to check it.

## Format
- Use a table for the session or course plan with timings.
- Give activities and questions ready to use, with answer keys.
- Keep language at the learners' level.

## Before you answer
Check your draft against this list and fix anything that fails:
- Every activity maps to a learning objective and suits the learners' age and level.
- Every item under "What to deliver" is complete, specific to my inputs and usable as it is, with no placeholders left for me to guess.
- Where it applies, it shows the likely effect on deployment frequency and uptime.

If something essential is missing, ask me up to 3 short questions first. Otherwise, start.