Principal Engineer - Mobile

Job Summary:

The Principal Engineer - Mobile operates at the intersection of deep technical execution and broad organizational influence. This role will resolve the hardest architectural questions, set the AI-native engineering bar, and ensure that iHerb's platform decisions compound over time rather than accumulate debt. Reporting to the VP of Engineering this role collaborates closely with peer Principals, Engineering Managers, and peer VPs across the organization.

This role owns the end-to-end technical strategy for iHerb's mobile platform, covering iOS and Android apps used by millions of customers globally. You will lead the mobile modernization effort, drive platform and architecture decisions, and set the technical bar for the Mobile team.

Job Expectations:

• Define and own the mobile platform architecture: platform choices, app structure, shared component strategy, and native versus cross-platform patterns.
• Lead the technical scoping and execution of the mobile modernization effort, coordinating with the Mobile EM and cross-functional partners.
• Hands-on contributor: write production mobile code, build proofs of concept, and validate architecture through working software.
• Set and enforce technical standards for the Mobile team; drive code reviews and architecture reviews.
• Evaluate and decide on cross-platform frameworks where appropriate, based on engineering tradeoffs and long-term maintainability.
• Contribute mobile-specific patterns and lessons into iHerb's shared AI-driven SDLC golden path.
• Drive the hardest cross-cutting technical decisions across multiple teams and shared platform services.
• Establish and evolve iHerb's AI-driven SDLC golden path: shared standards, Claude Code skills, guardrails, and automation patterns.
• Lead complex multi-team technical efforts by coordinating architecture reviews, aligning peer Principals and EMs, and resolving competing approaches.
• Mentor and raise the technical bar across the engineering organization through code review, architecture review, and direct coaching of senior engineers.
• Represent engineering in cross-functional conversations with product, data science, security, and infrastructure.
• Feed architectural decisions into the shared knowledge base so institutional knowledge compounds across the organization.

Knowledge, Skills and Abilities:

Required:

• AI-driven SDLC (required): demonstrated use of AI-assisted development tools such as Claude Code, GitHub Copilot, or Cursor to ship production systems. Can articulate workflow changes, quality tradeoffs, and guardrail strategies.
• Architecture at scale: experience designing and evolving large-scale distributed systems across multiple teams and years: APIs, data pipelines, event-driven architectures, or high-traffic platforms.
• Cross-org technical leadership: track record of driving architectural standards, technical roadmaps, or platform initiatives that span multiple teams or organizations.
• Engineering quality mindset: deeply held opinions on code quality, observability, CI/CD, test automation, and maintaining velocity without accumulating debt.