“Go or no-go for release 5.4” is a release captain (senior software engineer) job simulation on FinderK.
You work at Orla Books, an original fictional company, and complete 3 assignments in about 80 minutes.
It is for anyone who wants to practice release captain (senior software engineer) work. No previous work experience is required.
Role
Release captain (senior software engineer)
Industry
Software engineering
Level
Mid-level
Time
About 80 minutes, 3 assignments
Access
Included in Plus
Created by
FinderK
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.
Read the full brief
You are the release captain for a bookkeeping company's four-weekly release. The dashboards look mostly green. Underneath, a migration runs seventeen minutes past its window, Android crashes on one screen on older phones, a test was quarantined three days before the branch cut and a known bug has no sign-off. Thousands of customers lose their bank feeds if the new connector is not live by 31 October, and marketing has an email booked for Thursday. You score readiness against the policy, write the decision note and the exceptions you need, then plan the rollout and tell support and marketing. Automated checks confirm your figures and saved work; your judgement is reviewed against the standard for the role.
What is Orla Books?
Orla Books is a fictional maker of bookkeeping software for about 41,000 small businesses, with a web app and iOS and Android apps. Releases go out every four weeks on a release train, with a senior engineer acting as release captain. This case runs from Tuesday 13 to Wednesday 14 October 2026. All times are UTC. The captain decides readiness and the rollout plan within the release policy; only the Head of engineering approves exceptions.
Who do you play?
You are the release captain, release 5.4 in the Engineering team.
You are a senior software engineer acting as release captain for 5.4. You judge readiness against the release policy, recommend go or no-go, and set the rollout plan and its gates. Only Ines Moreau can approve an exception to the policy, and only those it allows. Marketing timing is agreed by Rafael with marketing under the communications runbook.
What will you do?
1. Score readiness against the go criteria
25 minutes
2. Write the decision note and ask for exceptions
30 minutes
3. Book the rollout and tell support and marketing
Rafael Dominguez, product owner, bank feeds and invoicing
Amara Nwosu, customer support lead
These coworkers are fictional. They may make mistakes, so compare their suggestions with the evidence.
Frequently asked questions
How long does “Go or no-go for release 5.4” take?
About 80 minutes, across 3 assignments. When the time is up, you get 10 minutes to round up and submit. Pausing stops the clock.
Is “Go or no-go for release 5.4” free?
No. It is included in FinderK Plus. With a free account you can also do it without grading.
Do I need release captain (senior software engineer) experience?
No. No previous work experience is required. The listed level is mid-level.
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 Orla Books a real company?
No. Orla Books is an original fictional company made for practice. Its coworkers may make mistakes, so check their suggestions against the evidence.
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.
Skills: Check code against the rule it implements, not its own tests; Work out expected money values exactly from a policy; Write review comments an author can act on; Hold a safety decision under release pressure
Fog has held twelve morning flights and three crews whose duty limits are running out. Build a recovery plan that stays inside the limits without leaning on captains' discretion, look after the passengers, and replan when an island airport says it will close early.
Skills: Rebuild a flying programme within crew duty limits; Choose which service to protect when not all can run; Refuse to plan on discretion under pressure; Arrange passenger care and priority help through the right team; Replan quickly when a new constraint arrives
A client's finance director has told his board that closing a depot will save 3.04 million pounds a year. Rebuild the savings from the client's own data, tell the steering committee the true number in a deck, and correct it again when a depot manager's figure turns out to be wrong.
Skills: Separate costs that end from costs that move; Build a savings and payback model from client data; Present an unwelcome number answer first; Handle a client sponsor's expectations with evidence; Revise analysis openly when data changes
Environmental compliance officer at Halbrook Dairies
About 75 minutes. Included in Plus.
A monthly ammonia result is above the permit limit. Decide whether the permit has actually been breached, get a notification signed before the clock runs out, and handle a report of dead fish downstream without guessing or denying.
Skills: Assess compliance against a permit's statistical limits; Separate records from what people remember; Meet a legal notification deadline under pressure; Report facts without speculating about cause; Handle a public pollution report within the rules