Senior mobile game developer — iOS puzzle game, JavaScript + Capacitor, pre-launch polish

We are finishing an iOS puzzle game and need one experienced developer for the final stretch. The app is built and passes a large automated test suite on every change. This is polish and completion work, not a rebuild, and not a rescue. THE STACK Plain browser JavaScript (no framework, no bundler) running inside a Capacitor shell, with a small Swift host for StoreKit, GameKit and ads. If you have only used Unity, this is not a fit. THE WORK, in rough order 1. Accessibility pass on the interface: tap targets to Apple's minimum, text sizing, and support for the system Larger Text setting. 2. Analytics instrumentation: define and wire the events we need to read retention, session length and conversion after launch. 3. Content tooling: extend our level generator with additional objective types. 4. General hardening across the codebase. HOW WE WORK, and please read this part before applying Every change ships with an automated test that has been shown to FAIL before the fix and pass after it. We do not accept a green test that has never been red. Every claim in a report carries the file and line it was read from. If you find something outside the scope of your task you name it, you do not fix it. This is not unusual for us, it is how the whole project runs, and candidates who find it excessive should not apply. You will work in a private repository against a protected main branch, through pull requests. WHAT WE ARE LOOKING FOR Strong JavaScript. Real iOS shipping experience. Comfortable reading a large existing codebase written by other people and matching its conventions rather than reformatting it. TO APPLY Do not send a generic proposal; we will not read it. Answer these three, briefly: 1. Describe a bug you fixed where your first fix was wrong. What did the second one change, and how did you know the first was wrong? 2. How do you satisfy yourself that a test you have just written would actually catch the defect it is named after? 3. You are asked to change one function. You notice a separate, unrelated bug two lines below it. What do you do? Start with the word "opera" so we know you read this. Fixed weekly hours can be discussed. Details of the app under NDA after a first call.