Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.nebulaengage.com/llms.txt

Use this file to discover all available pages before exploring further.

When you start a Nebula simulation, you don’t jump straight into the action. First, you go through a short AI-driven onboarding conversation that shapes everything about your session — your role, your difficulty level, and the case study you’ll work on. This conversation is handled by the onboarding coordinator: a named AI guide who asks about your background, listens to how you respond, and uses what it learns to set up a simulation that fits you.

​
What the onboarding coordinator does

The coordinator’s job is to gather just enough context about you to personalize your session without making the setup feel like a test. It doesn’t rely on a static questionnaire — it has a conversation, reads your responses, and makes inferences. By the end of onboarding, the coordinator has:
  • Assessed your experience level (student, junior, mid, senior, or executive)
  • Identified whether you’re approaching this as a student or a working professional
  • Suggested a difficulty level that matches your background
  • Offered three case study options for you to choose from
  • Assigned you a specific role within your selected company and domain
  • Optionally offered a brief baseline assessment to further calibrate difficulty
The coordinator’s name is generated fresh for each session, so it feels like a real person rather than a generic system prompt.

​
Onboarding stages

The coordinator moves through a defined sequence of stages. You won’t see these labels — the conversation flows naturally — but understanding what’s happening at each step can help you get the most out of it.
1

Greeting

The coordinator introduces itself, welcomes you to the company, and sets the tone for the conversation. This is intentionally low-pressure — it’s establishing rapport, not assessing you yet.
2

Experience assessment

The coordinator asks about your professional background. It’s listening for signals about your experience level: how long you’ve been working, what kinds of roles you’ve held, what you’re comfortable with.
3

Type detection

Based on what you’ve shared, the coordinator determines whether you’re approaching Nebula as a student (learning foundational skills) or as a professional (practicing or upskilling). This shapes the tone and framing of your session.
4

Difficulty suggestion

The coordinator proposes a difficulty level — beginner, intermediate, advanced, or expert — and explains its reasoning. You can confirm the suggestion or ask for a different level.
5

Case study selection

The coordinator presents three case study options, each with a title, description, estimated duration, and difficulty. You pick the one that fits your goals.
6

Role assignment

Based on your selected company, domain, and case study, the coordinator assigns you a specific role within the org. It explains why this role fits your context and what you’ll be accountable for.
7

Baseline assessment (optional)

If you want the system to further calibrate your difficulty, you can take a short baseline assessment — a handful of scenario-based questions relevant to your domain. This step is optional and skippable.
8

Complete

Onboarding wraps up. The coordinator hands off context to the simulation engine, your workspace is prepared, and you enter the virtual desktop.

​
What the coordinator infers

The coordinator doesn’t ask you to fill out a form. It draws inferences from the natural flow of conversation. Here’s what it’s paying attention to:
The coordinator listens for indicators of professional tenure, domain familiarity, and the kinds of problems you’ve worked on. It maps what it hears to one of five levels: student, junior, mid, senior, or executive.
It distinguishes between users who are studying toward a career (students) and those who are already working and looking to practice or advance (professionals). This shapes how scenarios are framed and what feedback emphasizes.
Difficulty is inferred from experience level and user type, then confirmed with you. If you take the optional baseline assessment, those results can also influence the final difficulty setting.

​
Choosing a case study

The coordinator presents exactly three case study options. Each option includes:
  • A title and short description of the scenario
  • The domain and difficulty level
  • An estimated duration
You pick the case study that best fits your goals. If you’re not sure, the coordinator can briefly explain why it suggested each option and which one it recommends given your background.
Your case study choice determines the core problem you’ll work on, the stakeholders you’ll deal with, and the objectives you’ll be evaluated against. Take a moment to read all three options before deciding.

​
Role assignment

Once you’ve selected a case study, the coordinator assigns you a role within your chosen company’s org structure. The role is scoped to your domain and matched to your difficulty level and experience. The coordinator explains:
  • What your role is and where you sit in the org
  • Why this role was assigned given your context
  • What your mandate is for the simulation
Your role determines your authority level, your reporting relationships, which personas you’ll interact with most, and what kinds of decisions fall within your purview.

​
The optional baseline assessment

After role assignment, the coordinator may offer a baseline assessment. This is a short set of scenario-based multiple-choice questions designed to probe your domain knowledge and judgment. Taking the assessment is optional. If you skip it, the simulation uses your inferred experience level and difficulty confirmation. If you take it, the results can fine-tune the difficulty calibration — pushing it up or down based on how you perform.
The baseline assessment is purely for calibration. It doesn’t affect your skill scores, XP, or progression profile — only the difficulty setting for the current session.