The Onboarding Demo

The Challenge

This is not a product-knowledge test. There is no scenario packet, no ticket queue, no fictional company to learn. Here is the prompt:

Pick any software you know well: a tool you use every day in your current role, software you love, or a free account you set up this week. Not Levelpath; we are not testing what you know about us. Now imagine a company just bought it. A team of six is about to use it for the first time next week. They did not choose it. Nobody on the team has opened it. You have one onboarding session to get them from zero to doing one thing with it on their own.

Run that session. Show them why it is worth their time, walk them through one thing they will do every week, and leave them able to do it without you.

That's it. The rest is yours. Make as many assumptions as you need about who the team is and what they do. Onboarding a sales team onto a CRM and onboarding a family onto a shared calendar app are on equal footing. We care about how you bring new users into a product, not which product you pick.

Why This Is the Challenge

Levelpath's customers are lean procurement teams who buy to get more throughput without more headcount. That only happens if the people across the company who have to use the tool actually do. A Customer Engagement Specialist's job is to get them there. The head of procurement buys Levelpath. Requesters across the company use it through the AI Front Door; approvers in IT, legal and finance act on it. But the person a Customer Engagement Specialist spends the most time with is the customer's power user (usually a procurement operations manager or analyst) who owns the platform after go-live: the admin settings, the intake forms and routing rules, the permissions, and the rollout to everyone else. If that person is set up for success, procurement's throughput goes up.

Constraints to Consider

• Time-box: spend no more than 40 minutes total (roughly 15 to prepare, 10 on the quick-start, 10 to 12 to record). We are evaluating what you can onboard under real constraints, not what you can produce with unlimited time.
• Live on screen. The demo must be in the real product, on your screen, during the recording. Slides and screenshots alone do not count. You can only assert what you can show.
• One thing, to completion. The team should see the start state, every step, and the result. We would rather see one thing taught fully than five features toured. Scope aggressively.
• Teach the team, not us. Speak to them as people who did not ask for a new tool. Nothing in the video should be addressed to an evaluator.

How We Assess Communication

Communication clarity matters for this role. We assess structure, audience awareness, and ability to explain something plainly, not presentation style or accent.

Submission: Upload each deliverable as a separate file directly on the Provn platform: your one-page quick-start and your video (MP4 or MOV).