Senior iOS engineer, shipping great software since 2012.
I started my career as one of five engineers building Shazam — the app that let you point a phone at a speaker and find out what was playing. The recognition engine was a black box to me. My work was everything around it: making something probabilistic and invisible feel instant and trustworthy to people who had never heard the word fingerprint.
That turns out to be good preparation for now, when a lot of companies have a model and no real idea how to put a product around it.
Two ways to work together
Senior iOS engineer on your team
Hands-on Swift and SwiftUI work, shipping features and raising the bar for the people around me. I have also led mobile as fractional CTO and head of mobile, so I can take on as much ownership as the team needs.
- Feature delivery, from design to App Store
- Architecture, code review and mentoring
- Release process and App Store relationship
- Technical leadership when you need it
Something urgent and specific
An app that has stopped shipping, or was built by someone who is no longer around. I have done this repeatedly, including taking a full stack back from an offshore agency.
- Releases that keep failing App Store review
- Codebases nobody on the team understands
- Crash rates and performance regressions
- Extracting a product from an outside vendor
Shipping great software since 2012, mostly solo or in small teams
Let’s start with a short look at what you have
Nobody should commit to six months of anything with someone they have not worked with. A Mobile Health Check, scoped and quoted at a fixed price after you tell me about the project, gets you a written assessment — architecture, release process, crash rate, App Store exposure, and what I would do about it, whether or not we carry on afterwards.