Technical leadership through architecture evolution. Senior iOS engineers are hired to solve problems that do not have Stack Overflow answers. Your CV should document architectural evolutions you have led: "Designed and implemented modular architecture supporting 50+ engineers, reducing merge conflicts by 70% and enabling weekly releases." Or: "Migrated 2M+ DAU app from UIKit to SwiftUI over 18 months, maintaining 99.9% crash-free rate throughout transition." These are not features-you are documenting organizational transformation.

Mentorship and team velocity multipliers. At senior level, your impact is measured through others. Quantify mentorship outcomes: "Mentored 4 engineers from junior to mid-level, 2 of whom were promoted within 12 months." Or: "Established code review culture reducing bug escape rate by 45% and improving knowledge sharing." Document technical onboarding programs you built, architecture decision records (ADRs) you instituted, or internal tech talks you delivered. Your individual output matters less than your organizational leverage.

Platform-level infrastructure contributions. Senior engineers build what others use. Highlight platform work: "Built internal analytics SDK adopted by 8 iOS teams, processing 50M+ events daily with less than 0.1% data loss." Or: "Designed networking layer with automatic retry, caching, and offline support, reducing API failure user impact by 80%." These demonstrate you think at SDK/API level, not just ViewController level. Include performance characteristics: latency, throughput, reliability SLA commitments.

Strategic technical decision-making with trade-off analysis. Show you can navigate ambiguity: "Evaluated SwiftUI vs. React Native for new product line, prototyping both and presenting trade-off analysis to executive team. Decision saved estimated $2M in long-term maintenance." Or: "Advocated for and led migration to Combine, reducing callback complexity and improving async code readability-adopted team-wide within 6 months." The key is showing decision process, not just outcomes.

App Store business impact and user metrics fluency. Senior iOS engineers speak business metrics. Move beyond technical stats to user and revenue impact: "App Store optimization (screenshots, keywords, ratings response) contributed to 40% increase in organic downloads." Or: "Push notification strategy implementation improved D7 retention from 23% to 38%, directly impacting LTV calculations." Or: "Reduced app size by 35MB through asset optimization, improving download completion rate by 15% in emerging markets." These connect your technical work to P&L.

Still measuring output in features shipped.

Why it fails: Senior engineers who list "Shipped 50+ features, closed 200+ tickets, released 10 app versions" are measuring junior metrics. At senior level, your value is organizational impact-how you multiplied team output, reduced systemic risk, or enabled capabilities that did not exist before. Feature counts suggest you have not evolved beyond individual contributor thinking.

How to fix: Reframe around enablement and transformation: "Architected modularization strategy enabling 8 teams to ship independently, reducing integration time from 2 weeks to 2 days." Or: "Built internal analytics SDK adopted across organization, eliminating duplicate implementations and standardizing data quality." Or: "Mentored team of 6 to adopt Combine, reducing callback complexity and improving code review velocity by 30%." Measure what you enabled, not what you built.

No documentation of technical decision-making process.

Why it fails: Senior engineers are hired for judgment, not just execution. CVs that only show outcomes ("Migrated to SwiftUI, improved performance") miss the critical piece: how you evaluated options, what trade-offs you considered, and why you chose the path you did. This signals reactive implementation versus strategic thinking.

How to fix: Include decision narratives: "Evaluated SwiftUI vs. UIKit for new product line, prototyping both and presenting trade-off analysis to leadership. SwiftUI selected for 40% faster development velocity, with migration plan for existing features." Or: "Advocated for GraphQL adoption over REST, documenting performance gains (60% payload reduction) and caching complexity trade-offs. Led pilot implementation proving viability." Show your thinking, not just your doing.

Missing business impact translation.

Why it fails: "Reduced memory usage by 40%" is a technical win. But "Reduced memory usage by 40%, enabling app to run on iPhone 8 and expanding addressable market by 15M users" is a business win. Senior engineers who cannot connect technical work to business outcomes struggle to get buy-in for initiatives and miss promotion cases.

How to fix: Every technical achievement needs business context: "Improved app launch time from 3.2s to 1.1s, reducing abandonment and contributing to 12% increase in D1 retention." Or: "Reduced app binary size by 28MB, improving download completion rate by 18% in emerging markets and supporting international expansion goals." Or: "Implemented A/B testing framework, enabling product team to run 50+ experiments/quarter and optimize conversion funnels." Translate technical to business fluently.

Your conference talks are your CV's opening act.

Senior iOS engineers operate in a reputation economy. A talk at try! Swift or iOSDevUK with 10K+ views signals expertise faster than any bullet point. If you have spoken at conferences, lead with it: "Speaker at [Conference] on [Topic]-recording viewed 15K+ times." If you have not spoken, start with meetup talks or internal tech presentations. The goal is provable thought leadership, not just claimed expertise. Your public technical voice becomes your hiring signal.

Mentorship outcomes beat individual output.

At senior level, "I shipped features" is baseline expectation. "I grew 3 engineers to promotion and reduced team attrition by 50%" is leadership. Document mentorship with specifics: "Mentored 2 junior engineers to mid-level promotion within 12 months through weekly 1:1s and structured learning plans." Or: "Established code review culture that reduced bug escape rate by 40% and improved knowledge sharing across 8-person team." Your legacy is the team you build, not just the code you write.

Navigate the "referral economy" strategically.

Senior iOS roles at top companies (Meta, Apple, Google, Spotify, Airbnb) are filled 70%+ through referrals. Your CV's job is not just to impress-it is to arm advocates who can forward you. Write your CV so a senior engineer can glance at it and say "This person knows their stuff" in 10 seconds. Clear metrics, recognizable technologies, and quantified impact make you referral-worthy. Then activate your network: former colleagues, conference contacts, open-source collaborators. The best senior roles never hit job boards.