A world built for you
Your answers and documents shape the company, the team or the neighbourhood, so the practice fits the goal you actually have.
Fumu Studio · Beta
Practise the real thing before it counts.
Fumu builds a living practice world around your goal: a team to join or a neighbourhood to live in, with people who remember you, missions that build on each other, and feedback that points at your own work.
A world built around your goal
Feedback backed by evidence from your work
Private by default, deleted when you ask
A world that reacts to what you do.
Studio is not a question bank. You do the work your goal asks of you, in a place that remembers your choices and lets them matter.
Missions that build on each other
Design an API, build it, then handle the incident it causes. Earlier decisions change what happens later.
People who remember you
Talk to teammates, clerks and baristas. They react to what you said before and to how the work is going.
Feedback with evidence
Each finding quotes your work or names what you did, so you can see exactly what it is based on.
A clear next step
For every gap, Fumu suggests a practice mission, a course or a mentor, and checks later whether it helped.
Private by default
Your documents are stored encrypted. Studio only runs with your consent, and you can delete everything at any time.
From a goal to proof that you're ready.
Four steps, repeated as often as you need. Your skill levels carry over from one world to the next.
01
Set a goal
Choose what you're preparing for and answer a few questions. Add a resume or job description if you have one.
02
Live in the world
Fumu builds your world in about a minute. Work through its missions with the people in it.
03
See what to improve
Every submitted mission is assessed against a rubric, with the evidence for each finding.
04
Close the gap
Take a practice mission, a course or a mentor session, then show the improvement on a new task.
Goals you can practise
Start with one of these.
Each goal comes with its own world, missions and skills. More are on the way.
01
Solve a Business Problem as a Data Analyst
Investigate a real-world-style business question using a fixed synthetic dataset. Clarify the decision, check data quality, define and calculate the right metric, explore segments, challenge your findings, and present a recommendation others can act on. Includes dataset-based reasoning and SQL or calculation review; your queries are saved and reviewed, not run in the app.
- Challenging the conclusion
- Framing the decision
- Establishing data fitness
- Recommending a next step
02
Win Your First B2B Customer
Practise winning a first paying business customer. Choose a prospect, start a conversation, discover the real problem, understand how the company buys, propose a useful paid pilot, negotiate and agree on an honest next step. Includes simulated buyer conversations and commercial document practice; no real outreach, contract or payment happens.
- Understanding how the company buys
- Commitment and handover
- Choosing a credible first customer
- Discovering the real problem
03
Handle Difficult Customers Confidently
Practise customer conversations when things go wrong. Understand the complaint, investigate the facts, explain uncertainty, handle refund or escalation requests, and follow through without making promises you cannot keep. Work with a simulated customer and support team, with feedback grounded in your actions.
- Understanding and acknowledging the complaint
- Escalating with a clear next owner
- Investigating before concluding
- Explaining uncertainty and progress
04
Win and Deliver Your First Freelance Project
Practise taking a freelance opportunity from first conversation to final handover. Discover the client's needs, propose scope and price, deliver a small project, handle feedback and extra requests, and follow up on payment. Get feedback on your decisions, communication, and submitted work.
- Closing the delivery loop
- Managing feedback and scope
- Discovering the real need
- Delivering against the brief
05
Your First Weeks as a Backend Engineer
Join a backend team and own a small change from brief to handover. Clarify requirements, design and implement a reliable API change, respond to review, plan a release, investigate an incident, and explain what should improve next.
- Releasing and operating a change
- Working effectively with a team
- Designing reliable backend behaviour
- Investigating and mitigating incidents
06
Your First Weeks as a Data Engineer
Join a data team and make an existing pipeline trustworthy. Clarify source contracts, model order changes, handle retries and late data, design quality checks, plan a backfill, investigate a data incident, and hand over a dataset others can rely on. Includes SQL and source design and synthetic pipeline-evidence review; nothing you write runs against a database or scheduler.
- Safe backfills
- Contracts, grain and modeling
- Investigating a data incident
- Handing over a data product
07
Prepare for Your Next Job Interview
Practise a connected interview process tailored to your target role. Explain your experience, solve a work sample, handle follow-up questions, meet your potential team, and ask what matters to you. Get feedback grounded in your answers and a focused plan for your next interview.
- Evaluating the opportunity
- Explaining work with others
- Explaining contribution and results
- Handling challenge and uncertainty
08
Your First Weeks as a Platform Engineer
Join a platform team and help an application team ship through an existing platform. Review a change, improve delivery and observability, investigate an incident, plan recovery, and make the onboarding path easier for the next team. Includes configuration and source review and synthetic operational-evidence analysis; nothing you write is applied to live infrastructure.
- Delivering reversibly
- Making self-service usable
- Reviewing an infrastructure change
- Diagnosing an operational failure
09
Your First Weeks as a QA Engineer
Join a software team and help test a change from brief to release review. Prioritize risks, design meaningful checks, investigate failures, report defects, review automation, assess fixes, and explain what is safe, blocked, or still untested. Includes test and source design and synthetic execution-evidence review; your tests are reviewed, not run in the app.
- Choosing reliable automation
- Assessing fixes and related impact
- Reporting and triaging defects
- Investigating behaviour
10
Everyday Estonian
Practise everyday life in Estonia: meet neighbours, shop, arrange appointments, solve household problems, and handle simple service conversations. Ask for clarification, recover from misunderstandings, and become more independent in Estonian.
- Arranging and confirming plans
- Repairing misunderstandings
- Understanding essential details
- Starting everyday conversations
11
Product Design in Practice
Improve a real-world-style product flow from user problem to engineering handoff. Interpret research, compare interaction options, design states and recovery, write clear content, address accessibility needs, and use evidence to refine the experience. Get feedback grounded in your decisions and submitted work. Text-based design reasoning, screen specifications and reference-case evaluation; no design tool, prototype testing or accessibility audit.
- Reviewing implementation and next learning
- Handing decisions to engineering
- Framing the design task
- Writing and specifying inclusive interaction
12
Product Management in Practice
Take a product request through discovery, prioritization, scope negotiation, launch readiness, and a simulated pilot. Work with customers, sales, design, engineering, and support. Explain your trade-offs, respond when plans change, and use the results to decide whether to improve, expand, pause, or stop. Nothing is built or released; the research notes, estimates and pilot results are fixed and fictional.
- Aligning and adapting delivery
- Learning from customers
- Deciding whether a launch is ready
- Choosing what deserves investment
13
Use AI Effectively at Work
Use AI to complete a realistic workplace project. Choose useful tasks, provide the right context, turn information into a brief, check analysis, improve a message, compare options and measure whether the workflow actually helps. Practise with an AI work partner and fictional workplace documents; browsing, external app actions and third-party AI tools are not connected.
- Writing with AI for a reader
- Briefing and improving a result
- Giving the right context
- Checking AI output
14
Communicate Confidently at Work in English
Text-based workplace communication practice. Practise the English you need in an international team: clarify requests, give updates, contribute to meetings, handle disagreement, negotiate deadlines, and explain difficult news. Work through a connected project week and get feedback on how clearly you communicate and what others understand.
- Explaining work to another audience
- Clarifying work requests
- Confirming decisions and next steps
- Disagreeing constructively
Every finding points at your own work.
Studio's feedback is built to be questioned, not just accepted.
Evidence on every finding
A grade needs a quote from your work or an action you took. Without one, the finding is marked for review instead.
You can dispute it
If a finding looks wrong, say why. It is reviewed again, and a mentor settles what Fumu can't.
Your data stays yours
Studio asks before its AI model reads anything, keeps documents encrypted and deletes all of it when you ask.