Architectural decisions are your currency. At the middle level, you should speak fluently about patterns you have implemented, not just used. "Refactored MVC codebase to MVVM+Coordinator, reducing view controller bloat by 40% and improving testability" demonstrates ownership of complexity. Detail specific architectural challenges: modularization with dynamic frameworks, dependency injection containers (Swinject, Needle), clean architecture boundaries. Your CV should read like a technical case study, not a skills grocery list.

CI/CD pipeline ownership signals seniority trajectory. Middle engineers who understand the full delivery pipeline are rare and valuable. Document your experience with: Xcode Cloud, Bitrise, GitHub Actions, or Fastlane automation. Specific wins: "Reduced App Store submission time from 3 days to 4 hours via Fastlane scripts and automated screenshot generation." Or: "Implemented automated UI testing in CI, catching 15+ regressions pre-release." These demonstrate you think beyond feature code to delivery excellence.

Performance optimization with Instruments mastery. Go beyond "used Instruments" to specific technical achievements: "Reduced memory footprint by 35% through Core Data batch processing optimization, identified via Allocations instrument." Or: "Eliminated main thread stalls by offloading image processing to background queues, improving scroll performance by 60fps consistency." Include before/after metrics whenever possible-hiring managers at top shops (Uber, Airbnb, Spotify) speak this language natively.

Cross-functional impact beyond code. Middle engineers are expected to influence product and design, not just implement tickets. Document instances where you: proposed technical solutions that simplified UX, identified edge cases that saved sprints of work, mentored juniors through code reviews, or contributed to technical RFCs. "Collaborated with product to scope MVVP approach, reducing initial development time by 3 weeks while maintaining core user value" shows strategic thinking.

Swift Package Manager and modularization expertise. Modern iOS teams are moving away from CocoaPods monoliths. Demonstrate your modularization experience: "Led migration from single-target app to 12-module architecture using SPM, reducing build times by 50% and enabling parallel feature development." Or: "Published 5 internal Swift Packages for networking, analytics, and UI components, adopted across 3 iOS teams." This signals you are building for scale, not just shipping features.

Staying in feature-implementation language.

Why it fails: Middle engineers who describe work as "Implemented login screen, built settings page, added profile feature" are indistinguishable from juniors. At 2-5 years experience, you should own outcomes, not just output. "Implemented" suggests you were handed specs and executed-middle engineers should influence scope and approach.

How to fix: Reframe around ownership and impact: "Owned authentication flow, reducing login abandonment by 25% through biometric integration and error state optimization." Or: "Led settings architecture redesign, enabling 12 new preference toggles without view controller bloat." Use verbs like owned, led, redesigned, optimized, architected-not just built or implemented.

Generic architecture claims without specifics.

Why it fails: "Experience with MVVM, VIPER, Clean Architecture" tells hiring managers nothing. Everyone lists patterns they have heard of. Without specifics, you signal shallow exposure-perhaps reading articles without implementing at scale.

How to fix: Document specific architectural decisions and trade-offs: "Migrated 15-view-controller flow from MVC to MVVM+Coordinator, reducing line count by 30% and enabling unit testing for business logic." Or: "Evaluated VIPER vs. Clean Architecture for new feature, chose VIPER for team familiarity-documented decision in ADR for future reference." Show you think about architecture, not just follow patterns.

No evidence of cross-functional collaboration.

Why it fails: Middle engineers work in the gap between design, product, and engineering. CVs that only mention coding suggest you operate in isolation-red flag for team dynamics. Modern iOS development requires negotiating trade-offs with designers, scoping with PMs, and aligning with backend teams.

How to fix: Document collaboration explicitly: "Partnered with design to refine animation specs, proposing reduced-motion alternatives for accessibility compliance." Or: "Collaborated with backend to design GraphQL schema, reducing over-fetching and improving load times by 40%." Or: "Led technical scoping sessions with product, identifying 3 edge cases that saved 2 sprints of rework." Show you work across boundaries, not just in Xcode.

Quantify the "invisible ceiling" escape.

Middle engineers face a brutal market position: too expensive for junior work, not yet trusted with senior decisions. Your CV must prove you have crossed the threshold into ownership. Do not say "worked on architecture"-say "owned authentication module serving 500K+ DAU with 99.9% uptime." Do not say "improved performance"-say "reduced API response time by 45%, eliminating user-reported lag in critical flows." Numbers signal you think in outcomes, not tasks. They are your escape ladder from the middle tier.

Show you can navigate legacy without rewriting it.

Every iOS team has legacy code-Objective-C bridges, outdated patterns, technical debt. Middle engineers who claim "only worked with modern Swift/SwiftUI" signal they will struggle in real codebases. Instead, show legacy navigation skills: "Maintained and extended Objective-C networking layer while gradually migrating to Swift, ensuring zero downtime during 6-month transition." Or: "Refactored 3-year-old view controllers without breaking existing functionality, adding unit coverage for future safety." Teams hire engineers who improve what exists, not just build from scratch.

Your network is your job search accelerator.

At 2-5 years, referrals matter more than applications. The best middle iOS roles are filled through team member recommendations before they hit job boards. Your CV should support network activation: clear narrative, quantified wins, and LinkedIn-optimized headline. When a senior engineer forwards your CV with "This person reduced our crash rate by 40%-worth talking to," you skip the ATS entirely. Build relationships at meetups, contribute to discussions on iOS Twitter/Mastodon, and make your expertise discoverable.