The ContextMost of Poke lives in messaging without an app download. But iOS is its own surface area: iMessage extensions, Shortcuts, widgets, Live Activities, lock screen, App Intents, and the native experiences that messaging alone cannot reach. We need an engineer who can own this surface end to end and push it as far as Apple's APIs allow.
We don't really care about experience or pedigree, we only care about slope, technical depth, obsession with craft, and how well you can build alongside us. Our current team is strongly connected and talent-dense, with backgrounds from Jane Street, MIT/Stanford research, and International Olympiads.
The RoleWe hire across many strengths under one title. You are a T-shaped engineer who can navigate the whole stack, but you are uniquely experienced in at least one of these areas:
- Native product surfaces: The user-facing flows that messaging cannot deliver. Compose interfaces, capture flows, rich previews, anything that needs a real screen.
- System and platform integrations: HealthKit, Calendar, Contacts, Location, Photos, Shortcuts, App Intents. Anything entitled, anything that talks to Apple.
- Parent app architecture: Settings, account, automations, notifications, push, background processing, the structure that lets every other piece fit.
- Apple platform craft: SwiftUI, performance, accessibility, signing, capabilities, App Store review strategy.
What we're looking for- Rigor under pressure. You move between product and debugging. You can stabilize melting systems while still shipping features.
- Apple platform mastery: You have shipped consumer iOS apps at scale. You know what Apple's APIs actually do versus what the docs claim.
- Platform thinking. You think in primitives, not just features. You build solutions that solve today's product needs while unlocking ten future use cases.
- Low ego. The talent bar is high, but no important problem is beneath us.
Something ElseIf your most interesting work is not in your resume, send what is. Include a link to your GitHub, a project you're proud of, App Store links, or a breakdown of the hardest iOS problem you have solved.
