“Review the partial refund change” is a software engineer job simulation on FinderK.
You work at Gatehouse Tickets, an original fictional company, and complete 3 assignments in about 60 minutes.
It is for anyone who wants to practice software engineer work. No previous work experience is required.
Role
Software engineer
Industry
Software engineering
Level
Early career
Time
About 60 minutes, 3 assignments
Access
Included in Plus
Created by
FinderK
A colleague's change will issue partial refunds to thousands of festival customers, and all its tests pass because they check the code against itself. Work out the right refunds from the finance policy, review the change, and hold the line on a money bug when the release date is used as pressure.
Read the full brief
You are a software engineer in the payments team of an online ticket seller. A teammate has written code to issue partial refunds when part of an event is cancelled, and the product manager wants it in Friday's release for a festival that may lose a night to weather. The tests pass, but they only repeat the code's own output. You work out the refunds the finance policy requires for each test case, write review comments the author can act on, and then re-review a second version that fixes two problems and introduces a third. Automated checks confirm your figures and saved work; your judgement is reviewed against the standard for the role.
What is Gatehouse Tickets?
Gatehouse Tickets is a fictional online ticket seller for concerts, festivals and theatre. Its payments team is adding automatic partial refunds for partly cancelled events, and a pull request is up for review before the Friday release. This case runs from Monday 9 to Thursday 12 November 2026. Amounts are in pounds. A reviewer approves or requests changes; payments changes need two approvals including a senior engineer; product decides what is in a release, engineering decides what is safe to merge.
Who do you play?
You are the software engineer in the Payments team.
You review pull requests in the payments and refunds services. Payments changes need two approvals, one from a senior engineer; your approval counts only with a senior's. You may approve, request changes or comment. Dylan Moss decides what is in a release; engineering decides what is safe to merge; finance owns the refunds policy.
Kenji Arai, software engineer, author of pull request 482
Dylan Moss, product manager
Beatrice Owusu, finance operations lead
These coworkers are fictional. They may make mistakes, so compare their suggestions with the evidence.
Frequently asked questions
How long does “Review the partial refund change” take?
About 60 minutes, across 3 assignments. When the time is up, you get 10 minutes to round up and submit. Pausing stops the clock.
Is “Review the partial refund change” free?
No. It is included in FinderK Plus. With a free account you can also do it without grading.
Do I need software engineer experience?
No. No previous work experience is required. The listed level is early career.
What do I get when I finish?
You get feedback on each assignment you submit. Completing all required assignments earns a completion certificate. It records participation and is not professional accreditation.
Is Gatehouse Tickets a real company?
No. Gatehouse Tickets is an original fictional company made for practice. Its coworkers may make mistakes, so check their suggestions against the evidence.
Release captain (senior software engineer) at Orla Books
About 80 minutes. Included in Plus.
Release 5.4 must get a new bank feed connector live before an aggregator switches off its old interface on 31 October, but Android crashes, a slow migration and a quarantined test stand in the way. Judge readiness, recommend a plan and roll it out without over-promising.
Skills: Judge release readiness against written criteria and evidence; Separate what a dashboard shows from what the policy counts; Recommend a release plan that protects a hard external deadline; Ask for only the exceptions the policy allows, with reasons; Plan a staged rollout and the communications that depend on it
Six customers wrote in overnight after a bad delivery day. Sort the queue, apply the credit policy, reply honestly to an angry customer and escalate a food safety report with the facts.
Skills: Sort a support queue by urgency and impact; Apply a credit policy and approval limits; Write an honest customer reply under pressure; Escalate a food safety report with the facts
Nurse in charge, night shift at St Aldhelm's Hospital
About 54 minutes. Included in Plus.
A registered nurse has called in sick and a confused patient now needs someone with him all night. Work out what the ward needs, get cover through the escalation route, and allocate the night safely.
Skills: Calculate safe staffing from patients' care levels; Escalate a staffing gap in writing with SBAR; Allocate patients within load and competency limits; Plan for the time before cover arrives
Payroll closes at noon tomorrow. Check a week of extra hours against timesheets, approvals and the policy, answer a worried colleague honestly, and give your manager the exceptions she must decide.
Skills: Check extra hours against timesheets, approvals and policy; Calculate normal and time and a half pay correctly; Explain held pay honestly to the person affected; Keep decisions within payroll authority and escalate the rest