Senior Staff iOS Engineer

Block•Bay Area, CA, United States of America, CA

7d•$263,600 - $395,400•Remote

About The Position

The role focuses on building native foundations that support seller-facing software across multiple teams. The engineer will set direction for iOS architecture, performance, reliability, security, and developer experience. This involves identifying and addressing important, unowned problems, proving directions through hands-on work, and creating programs for other teams to join. The goal is to create leverage through clear interfaces, documentation, and developing new technical leaders, rather than being a permanent bottleneck.

Requirements

12+ years of professional software engineering experience.
8+ years in roles where mobile engineering was a primary responsibility, including 4+ years building native iOS products.
Deep expertise across modern and legacy iOS frameworks, Swift, and Objective-C.
Experience creating foundational systems, shared frameworks, or developer tooling used across multiple teams.
A record of leading strategic, multi-quarter initiatives with broad adoption and durable impact.
Experience connecting platform strategy to customer-facing and multi-tenant SaaS products that support business operations.
Strong systems thinking, technical communication, mentoring, and organizational influence.
Self-directed and actively gather the context, data, and domain expertise needed to make sound decisions.
Move independently within your scope and seek alignment when decisions affect other teams or create long-term commitments.
Use AI tools to investigate and deliver at greater scale. Verify the work and remain accountable for security, reliability, and customer trust.
Measure success through adoption and seller or customer outcomes, not the production of frameworks or documents.

Responsibilities

Find and frame systemic iOS problems that do not yet have clear ownership.
Define strategy, architecture, standards, and measures of success across teams and applications.
Build prototypes, reference implementations, and the critical path needed to prove the direction.
Lead multi-quarter migrations and foundational initiatives through broad adoption.
Establish durable practices for quality, testing, observability, release safety, and maintainability.
Develop senior engineers and create an ownership model that does not depend on you as a permanent bottleneck.