This isn't a course with lessons. It's a job. Here's how to approach it like a real junior hire.
General principles
1. Read the assignment carefully
Your manager writes in a casual chat style, but the task is real. Look for:
The deliverable they want (a query, a memo, a spec, code)
The deadline implication ("by end of day", "before standup")
Any constraints (use only the provided data, no external tools)
2. Download the data first
Every role has files in the sidebar. Download them before you start working. For Data Analysts: the warehouse mrg_dw.db and the export CSV are your raw materials.
3. Do the work offline, then paste your answer
Don't try to write SQL or long documents inside the chat box. Work in your preferred editor (VS Code, DB Browser, Google Docs), then paste the result back into the chat.
4. Be specific in your replies
Vague answers get sent back. "I looked at it" isn't enough. Show your work:
For SQL: paste the query AND explain what it does in one sentence
For analysis: state the finding, the evidence, and the business implication
For code: explain the approach, any trade-offs you considered
5. If it's wrong, fix it and resend
Auto-graded tasks tell you exactly what's wrong (wrong row count, missing data). For manager-reviewed tasks, they'll name the gap. Don't argue — just fix it and resend.
Role-specific guidance
Data Analyst
Working with the warehouse
Open mrg_dw.db in any SQLite client. Key tables you'll use:
SELECT name FROM sqlite_master WHERE type='table';
Always sanity-check your results. If a query returns 50,000 rows when you expected 50, something's wrong.
Tip: Auto-graded tasks accept the exact answer. If you get "FAIL", read the feedback — it tells you expected vs actual row counts.
Software Engineer
Code review culture
Your lead will review your code like a real senior engineer. Expect comments on:
Test coverage — did you write tests?
Error handling — what happens when input is bad?
Naming — are variables and functions clear?
Tip: Zip your code files and attach them to the chat if the response is long.
Product Manager
Writing PRDs and specs
Your documents should answer: Who is the user? What problem are we solving? How do we measure success? What does "done" look like?
Lead with the user story, not the solution
Include acceptance criteria (3-5 bullet points)
Flag open questions and risks
Marketing Analyst
Campaign and cohort analysis
You'll work with campaign spend, revenue, and customer cohort data. Key questions to answer:
Which channel has the lowest CAC?
Which cohort has the highest 90-day retention?
What budget reallocation would you recommend?
Tip: Show your calculations. "ROAS is 3.2x" is good. "ROAS is 3.2x because revenue $32k / spend $10k" is better.
The milestone review
Every ~2 weeks you'll hit a milestone. This is a bigger deliverable reviewed by a senior stakeholder. To pass:
Address the brief completely — don't skip sections
Write at least 200 words (managers reject one-liners)
Tie your work back to business impact
Getting un-stuck
If you're genuinely blocked:
Re-read the task — you probably missed a detail
Ask your manager in chat for a hint (costs a message)
Check this guide again
Look at the Downloads tab — sometimes hints are in the file descriptions