How to review your take-home iOS app

The last hour on a take-home is often worth the most. A deliberate self-review catches the exact things a reviewer flags first.

A self-review checklist

Read the code as a stranger would: is the structure obvious, are names meaningful, is there dead code or commented-out cruft to remove. Confirm the app builds cleanly with no warnings, handles empty, loading, and error states, and does not crash on bad input. Verify you actually met the brief's requirements rather than an adjacent version of them.

The finishing touches

Make sure core logic has tests and that they pass, add a concise README explaining decisions and trade-offs, and note anything you deliberately left out and why. Check the git history is tidy and the project runs from a clean checkout. These finishing touches are what move a submission from acceptable to clearly senior.

Go deeper than a summary

Share Your Screen works topics like this through in full: 75 solved Swift problems with tests, 9 real case studies, and 7 annotated mock interviews, so you rehearse the live round instead of just reading about it.

Get the book

Frequently asked

What should I check before submitting a take-home?

That it builds warning-free, meets the brief, handles empty and error states, has tests on core logic, and ships with a short decisions README.

Should I mention what I left out?

Yes. Noting deliberate cuts and trade-offs in the README shows scoping judgment and reads as more senior than pretending the work is exhaustive.