Which onboarding track should I assign to this new hire?
Decision tree
Overview
Full decision path
Start: Q1
Q1 — What best describes your primary role?
- A: Engineering / Development → next question Q2 — Which area of engineering?
- B: Design / Product → next question Q3 — What is your primary focus?
- C: Sales / Marketing → next question Q4 — Which team?
- D: Finance / Operations → outcome Finance / Operations
- E: Executive / Leadership → outcome Leadership
Q2 — Which area of engineering?
- A: Frontend / Web → outcome Frontend Engineer
- B: Backend / API → outcome Backend Engineer
- C: DevOps / Infra → outcome DevOps / Infrastructure
- D: Data / ML → outcome Data / ML Engineer
Q3 — What is your primary focus?
- A: UI / Visual design → outcome Designer
- B: Product management → outcome Product Manager
- C: UX research → outcome UX Researcher
Q4 — Which team?
- A: Sales → outcome Sales
- B: Marketing → outcome Marketing
- C: Customer success → outcome Customer Success
Outcomes
- Frontend Engineer
(OUT_FE) - Reached from Q2 (A).
- Backend Engineer
(OUT_BE) - Reached from Q2 (B).
- DevOps / Infrastructure
(OUT_DEVOPS) - Reached from Q2 (C).
- Data / ML Engineer
(OUT_DATA) - Reached from Q2 (D).
- Designer
(OUT_DESIGN) - Reached from Q3 (A).
- Product Manager
(OUT_PM) - Reached from Q3 (B).
- UX Researcher
(OUT_UXR) - Reached from Q3 (C).
- Sales
(OUT_SALES) - Reached from Q4 (A).
- Marketing
(OUT_MKTG) - Reached from Q4 (B).
- Customer Success
(OUT_CS) - Reached from Q4 (C).
- Finance / Operations
(OUT_OPS) - Reached from Q1 (D).
- Leadership
(OUT_EXEC) - Reached from Q1 (E).
Machine-Readable JSON (Canonical Model)
View JSON
{
"_meta": {
"schema": "https://www.drawdecisiontree.com/decision-dag.schema.json",
"source": "https://www.drawdecisiontree.com",
"description": "DrawDecisionTree.com is a free tool for building, sharing, and embedding interactive decision trees. This file is the machine-readable export of a published decision tree. The `dsl` field contains the original source in the Decision DAG DSL; the `dag` schema is documented at the URL in `schema` above.",
"links": {
"interactive": "https://www.drawdecisiontree.com/trees/drawdecisiontree/onboarding-role",
"embed": "https://www.drawdecisiontree.com/embed/path/drawdecisiontree/onboarding-role",
"dsl_reference": "https://www.drawdecisiontree.com/decision-tree-dsl-reference",
"guides": "https://www.drawdecisiontree.com/guides",
"schema_docs": "https://www.drawdecisiontree.com/decision-dag.schema.json",
"author_trees": "https://www.drawdecisiontree.com/trees/drawdecisiontree"
},
"generated_at": "2026-07-03T21:08:41.983Z"
},
"author": {
"handle": "drawdecisiontree",
"first_name": "Andrew",
"last_name": null,
"avatar_url": "1d32d828-b6ca-40ec-bdd7-771fe7b9c36a/avatar-1778531481027.svg",
"display_name": "Andrew"
},
"file": {
"id": "ccf6e3b0-19d1-4211-9f0d-3f436a612234",
"name": "Which onboarding track should I assign to this new hire?",
"public_slug": "onboarding-role",
"updated_at": "2026-05-12T16:53:43.587978+00:00",
"url": "https://www.drawdecisiontree.com/trees/drawdecisiontree/onboarding-role",
"json_url": "https://www.drawdecisiontree.com/trees/drawdecisiontree/onboarding-role/tree.json",
"dsl_url": "https://www.drawdecisiontree.com/trees/drawdecisiontree/onboarding-role/tree.dag"
},
"meta": {
"description": null,
"mode": "decision",
"entry": "Q1",
"tags": [],
"image": null
},
"questions": [
{
"id": "Q1",
"text": "What best describes your primary role?"
},
{
"id": "Q2",
"text": "Which area of engineering?"
},
{
"id": "Q3",
"text": "What is your primary focus?"
},
{
"id": "Q4",
"text": "Which team?"
}
],
"outcomes": [
{
"id": "OUT_FE",
"label": "Frontend Engineer"
},
{
"id": "OUT_BE",
"label": "Backend Engineer"
},
{
"id": "OUT_DEVOPS",
"label": "DevOps / Infrastructure"
},
{
"id": "OUT_DATA",
"label": "Data / ML Engineer"
},
{
"id": "OUT_DESIGN",
"label": "Designer"
},
{
"id": "OUT_PM",
"label": "Product Manager"
},
{
"id": "OUT_UXR",
"label": "UX Researcher"
},
{
"id": "OUT_SALES",
"label": "Sales"
},
{
"id": "OUT_MKTG",
"label": "Marketing"
},
{
"id": "OUT_CS",
"label": "Customer Success"
},
{
"id": "OUT_OPS",
"label": "Finance / Operations"
},
{
"id": "OUT_EXEC",
"label": "Leadership"
}
],
"dsl": "dag: Which onboarding track should I assign to this new hire?\nversion: 1.0.0\nentry: Q1\n\nQ1: What best describes your primary role?\n A: Engineering / Development -> Q2\n B: Design / Product -> Q3\n C: Sales / Marketing -> Q4\n D: Finance / Operations -> [OUT_OPS]\n E: Executive / Leadership -> [OUT_EXEC]\n\nQ2: Which area of engineering?\n A: Frontend / Web -> [OUT_FE]\n B: Backend / API -> [OUT_BE]\n C: DevOps / Infra -> [OUT_DEVOPS]\n D: Data / ML -> [OUT_DATA]\n\nQ3: What is your primary focus?\n A: UI / Visual design -> [OUT_DESIGN]\n B: Product management -> [OUT_PM]\n C: UX research -> [OUT_UXR]\n\nQ4: Which team?\n A: Sales -> [OUT_SALES]\n B: Marketing -> [OUT_MKTG]\n C: Customer success -> [OUT_CS]\n\n[OUT_FE]: Frontend Engineer\n description: Access to design system, component library, and web repos.\n code: ROLE_FRONTEND\n\n[OUT_BE]: Backend Engineer\n description: Access to API repos, database tools, and internal services.\n code: ROLE_BACKEND\n\n[OUT_DEVOPS]: DevOps / Infrastructure\n description: Access to CI/CD pipelines, cloud console, and monitoring.\n code: ROLE_DEVOPS\n\n[OUT_DATA]: Data / ML Engineer\n description: Access to data warehouse, notebooks, and ML platform.\n code: ROLE_DATA\n\n[OUT_DESIGN]: Designer\n description: Access to Figma, design tokens, and the component library.\n code: ROLE_DESIGN\n\n[OUT_PM]: Product Manager\n description: Access to roadmap tools, analytics, and feature flag dashboards.\n code: ROLE_PM\n\n[OUT_UXR]: UX Researcher\n description: Access to research repositories, user interview tools, and analytics.\n code: ROLE_UXR\n\n[OUT_SALES]: Sales\n description: Access to CRM, deal room, and sales enablement materials.\n code: ROLE_SALES\n\n[OUT_MKTG]: Marketing\n description: Access to CMS, analytics, and campaign management tools.\n code: ROLE_MARKETING\n\n[OUT_CS]: Customer Success\n description: Access to support tooling, customer data, and onboarding playbooks.\n code: ROLE_CS\n\n[OUT_OPS]: Finance / Operations\n description: Access to financial systems, HR tools, and operational dashboards.\n code: ROLE_OPS\n\n[OUT_EXEC]: Leadership\n description: Access to executive dashboards, board materials, and all-team reports.\n code: ROLE_EXEC\n"
}DSL Representation
dag: Which onboarding track should I assign to this new hire?
version: 1.0.0
entry: Q1
Q1: What best describes your primary role?
A: Engineering / Development -> Q2
B: Design / Product -> Q3
C: Sales / Marketing -> Q4
D: Finance / Operations -> [OUT_OPS]
E: Executive / Leadership -> [OUT_EXEC]
Q2: Which area of engineering?
A: Frontend / Web -> [OUT_FE]
B: Backend / API -> [OUT_BE]
C: DevOps / Infra -> [OUT_DEVOPS]
D: Data / ML -> [OUT_DATA]
Q3: What is your primary focus?
A: UI / Visual design -> [OUT_DESIGN]
B: Product management -> [OUT_PM]
C: UX research -> [OUT_UXR]
Q4: Which team?
A: Sales -> [OUT_SALES]
B: Marketing -> [OUT_MKTG]
C: Customer success -> [OUT_CS]
[OUT_FE]: Frontend Engineer
description: Access to design system, component library, and web repos.
code: ROLE_FRONTEND
[OUT_BE]: Backend Engineer
description: Access to API repos, database tools, and internal services.
code: ROLE_BACKEND
[OUT_DEVOPS]: DevOps / Infrastructure
description: Access to CI/CD pipelines, cloud console, and monitoring.
code: ROLE_DEVOPS
[OUT_DATA]: Data / ML Engineer
description: Access to data warehouse, notebooks, and ML platform.
code: ROLE_DATA
[OUT_DESIGN]: Designer
description: Access to Figma, design tokens, and the component library.
code: ROLE_DESIGN
[OUT_PM]: Product Manager
description: Access to roadmap tools, analytics, and feature flag dashboards.
code: ROLE_PM
[OUT_UXR]: UX Researcher
description: Access to research repositories, user interview tools, and analytics.
code: ROLE_UXR
[OUT_SALES]: Sales
description: Access to CRM, deal room, and sales enablement materials.
code: ROLE_SALES
[OUT_MKTG]: Marketing
description: Access to CMS, analytics, and campaign management tools.
code: ROLE_MARKETING
[OUT_CS]: Customer Success
description: Access to support tooling, customer data, and onboarding playbooks.
code: ROLE_CS
[OUT_OPS]: Finance / Operations
description: Access to financial systems, HR tools, and operational dashboards.
code: ROLE_OPS
[OUT_EXEC]: Leadership
description: Access to executive dashboards, board materials, and all-team reports.
code: ROLE_EXEC
Machine Access
- Static JSON:
/trees/drawdecisiontree/onboarding-role/tree.json - Live JSON (SPA):
/json/drawdecisiontree/onboarding-role - Raw DSL:
/trees/drawdecisiontree/onboarding-role/tree.dag - Canonical HTML:
/trees/drawdecisiontree/onboarding-role
Questions in this decision tree
- What best describes your primary role?
- Which area of engineering?
- What is your primary focus?
- Which team?
Possible outcomes
- Frontend Engineer
- Backend Engineer
- DevOps / Infrastructure
- Data / ML Engineer
- Designer
- Product Manager
- UX Researcher
- Sales
- Marketing
- Customer Success
- Finance / Operations
- Leadership
How to use this decision tree
Click "Open interactive version" to step through the questions. Your answers narrow the tree until a recommended outcome is reached. You can also embed this tree on your own site.
More decision trees by Andrew
Which API design pattern is right for my project?
Determine the right API design style for your integration scenario.
CI/CD Pipeline Tool Selection
Choosing a CI/CD platform is a long-term infrastructure commitment — pipelines accumulate config, custom scripts, and team muscle memory that make switching painful. This tree eliminates tools that don't fit your source control host, infrastructure model, or team scale, leaving only the options genuinely viable for your situation.
Which cloud provider should I use — AWS, Azure, or Google Cloud?
Answer a few questions to identify the most suitable cloud platform for your workload.
Container Orchestration Platform Selection
Container orchestration is foundational infrastructure — the platform you choose shapes how you deploy, scale, network, and operate every service you run. This tree eliminates options that don't match your operational maturity, cloud provider commitment, and workload complexity, so you land on the platform that fits your team today without over-engineering for a scale you haven't reached.
How do I assess the health of a customer account?
Classify a customer's health score to guide proactive engagement and retention strategy. Use this tree during your regular account reviews or whenever a trigger event—such as a low NPS, a support spike, or a missed check-in—prompts a reassessment. The outcome drives the cadence and urgency of your next CSM action.
How should I escalate this customer issue?
Determine the appropriate escalation path when a customer issue exceeds normal CSM handling. This tree helps you move quickly and confidently when a situation is deteriorating, ensuring the right people are engaged at the right time. Use it the moment you sense an issue may outgrow your ability to resolve it alone.