A résumé entry you can adapt
Use this structure for a completed simulation: “[Company] [topic] Job Simulation on Forage | [Month Year completed].” Add one bullet describing the task you actually completed. Forage recommends a Certifications section; follow the application’s instructions.
For example, a fictional completed task might read: “Compared two pricing scenarios in a spreadsheet and explained how the assumptions changed the recommendation.” Use that wording only if it describes your own task. List a separate independent project separately, and label unfinished work as in progress.
Use a heading that makes the relationship clear
Use a heading that makes the relationship clear
Forage simulations are free, open-access and self-paced. You complete tasks, compare your work with model answers and receive a completion certificate. That is practice with an employer-designed scenario, not employment with the employer.
| Question | Answer |
|---|---|
| Format | Free, open-access, self-paced job simulations. |
| Employment | A simulation is neither employer employment nor an internship application. |
| Completed résumé label | Provider recommends Certifications: company name, Job Simulation on Forage, completion month/year. |
| In progress | Describe progress honestly; do not claim a completion certificate you have not earned. |
| Evidence | Describe your actual tasks and separate any independent extension from the simulation. |
Forage’s résumé article recommends a Certifications section and a label that identifies the company, Job Simulation on Forage, and completion month and year. An adaptable entry is “[Company] [topic] Job Simulation on Forage | [Month Year completed],” followed by the task you actually did. Do not title the entry “Intern at [Company]” unless you separately held that role.
A completion certificate records finishing the simulation; it does not establish employer employment, a professional licence or admission to an internship. If a form asks for employment history, do not use the featured company as your employer for this activity. Explain it in an appropriate training, projects or additional-information field when one is available.
Choose one task you need for a real application
Choose one task you need for a real application
Read a target internship posting and choose an unfamiliar task: checking a dataset, investigating a defect, comparing scenarios or presenting a recommendation. Read the simulation's task outline to see whether you will practice that task. A recognizable brand is less useful than relevant work you can explain.
Try the task before studying the model answer. Keep your first attempt and note one correction. Then reproduce the method on a small separate example without the answer beside you. This distinguishes recognizing a good solution from being able to produce one.
Choose a simulation whose actual task outline relates to the posting, then set a finish point: a checked analysis, a tested change or a recommendation you can explain. A provider’s estimated duration helps plan your time; it is not an employment schedule. Stop after one useful task and assess what you learned before committing to several more.
Keep a short evidence log with the task, your first approach, what the model answer changed, and what you can now do independently. This is your preparation method, not a Forage completion rule. It gives you something specific to discuss when an interviewer asks how you learned the skill.
An independent example: the average rate can be wrong
An independent example: the average rate can be wrong
This is an original exercise using invented counts, not a Forage assignment. A subscription business has three customer groups. Which has the highest cancellation rate, and what is the rate for the whole business?
- B has the highest observed rate: 14 ÷ 40 = 35%.
- A has the most cancellations: 20. The highest rate and largest number are different questions.
- The overall rate is 40 ÷ 140 = 28.6%, not the unweighted average of 25%, 35% and 30%, which is 30%. The groups have different sizes.
| Group | Customers | Cancellations | Cancellation rate |
|---|---|---|---|
| A | 80 | 20 | 25% |
| B | 40 | 14 | 35% |
| C | 20 | 6 | 30% |
| Total | 140 | 40 | 28.6% rounded |
Turn the calculation into a project, not a business-impact claim
Turn the calculation into a project, not a business-impact claim
Write a one-page memo showing the denominators, the calculation and one question to investigate. For example, do the groups differ in contract length or time since signup? The counts show where to look; they do not establish why customers canceled or what an intervention would achieve.
Keep this independent extension separate from the simulation. A heading could be ‘Subscription cancellation analysis | Independent project, synthetic data.’ A matching bullet is: ‘Analyzed cancellation counts for 140 fictional customers; reconciled the overall rate and compared high-rate versus high-volume groups.’ These are aggregate counts, not evidence that you worked with 140 individual customer records.
For the actual simulation, write a different bullet about its real task: ‘Compared operating scenarios in a simulated business case and explained how the recommendation changed with the cost assumption.’ Use it only if that describes your work, and follow the provider's rules on sharing task materials.
For a completed simulation, keep the certificate and verify the title and completion date before writing the entry. Choose one or two relevant task descriptions rather than a certificate count. If you checked a calculation or revised a recommendation, say what you checked or changed. Do not claim a reduction in costs or an employer decision unless the activity actually establishes it.
If the simulation is still in progress, do not use a completion date or list a certificate you have not earned. Our editorial suggestion is a plainly labeled training or project entry with “in progress” and only the task already completed. You may also omit it until finished. Enrollment alone is weak evidence for an application that needs a finished example.
| Status | How to describe it |
|---|---|
| Enrolled; no task finished | Keep it in your learning plan, or state enrollment accurately if asked; do not claim completion. |
| Some work completed; simulation in progress | Label it in progress and describe only the task you finished; no earned-certificate claim. |
| Simulation completed | Name the simulation, Forage and completion month/year; include a task you can explain. |
| Your own follow-up project | Use a separate independent-project label and identify invented or public data accurately. |
Decide whether another simulation adds anything
Decide whether another simulation adds anything
Before taking another, explain your existing project without the model answer: what did you decide, what did you check and what would change your recommendation? If you cannot answer, revisit that work. If you can, choose a new exercise only when it tests a different skill or helps answer a genuine career question.
Keep a relevant paid job, substantial course project or volunteer responsibility on the résumé when it provides stronger evidence. Do not crowd it out merely to fit more employer logos. Use the simulation to support an application, and complete the employer's actual application separately.
Where should the independent extension go? A Projects section makes sense when you have a separate output and can explain your own decisions. Keep the original simulation in the provider-recommended Certifications section if it is relevant. Avoid repeating the same task under two headings as though it were two experiences.
Before an interview, rehearse a short explanation: the scenario, your own attempt, one correction and the limit of the result. If you can calculate the fictional cancellation rate but cannot explain why the unweighted average is wrong, return to the denominator check. That explanation provides stronger evidence of learning than saying you completed several branded programs.