Work through a fictional company project. Each day has a saved brief, source files and acceptance criteria. The people and datasets are simulated; your deliverables and revision record are real.
General principles
1. Read the assignment carefully
Open Today’s task for the complete versioned brief. The manager’s chat is a short kickoff. Check:
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. Work in your editor, then submit for review
Work in your preferred editor, then open Today’s task and paste or attach the deliverable. Use Submit for review when it is ready. Ordinary chat is for questions and does not mark work accepted.
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
Read the criterion, quoted evidence and requested change in the review. If the review is wrong, challenge it in chat with the source row, query or test that demonstrates the disagreement. Keep both versions and submit the corrected evidence; you do not have to agree with an unsupported claim.
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: Attach source code and tests in Today’s task. ZIP, PY, SQL, CSV, TXT, MD, JSON, YAML, SQLite, XLSX, PDF and DOCX are supported, up to 20 MiB per file and 50 MiB expanded. Inspect extraction warnings. Local test logs are submitted evidence; they are not a claim that the platform executed your code.
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.
Daily and milestone reviews
Each day stays open until its deliverable is accepted. A blocked attempt to start the next day does not use up today’s start. Once accepted, the next task opens on the next working day. Portfolio progress counts accepted tasks separately from days opened and the interview result.
At set points in your role you'll hit a milestone. This is a substantial deliverable reviewed by a senior stakeholder. To pass:
Address the brief completely, don't skip sections
Supply the evidence each criterion needs. There is no word-count requirement.
All named reviewers must accept the same task version and artifact hash.
Tie your work back to business impact
Getting un-stuck
If you are blocked:
Name the missing fact, broken file or conflicting requirement.
Ask your manager in chat for a hint (costs a message)
Tag the relevant teammate. All teammates are listed in the sidebar.
If review could not complete, use Retry saved review. Failed reviews caused by unavailable services do not consume your message allowance.