Lead Software Engineer (Native Mobile AI Engineering)

We need to output HTML fragment with sections: About the role? Actually the posting includes a lot of intro about company, but we should not repeat job title as heading. We need to include sections only when there is real specific content. Likely sections: About the role (maybe role summary), Responsibilities, Requirements (Qualifications), Skills (Tools and Technologies), Benefits, Pay, Schedule (Work Flexibility). Also maybe "Who You Are" could be part of Qualifications? But we can treat as part of Requirements? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose appropriate headings. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also remove FINRA Requirements? That's maybe not boilerplate but it's a requirement; but it's about FINRA licenses not required. Might be considered minor metadata? It says "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." FINRA requirement is not a job ID; it's a requirement about licenses. Might be kept under Requirements? But it's a statement that FINRA licenses are not required and will not be supported. That's substantive? Probably we can include under Requirements as a note. We also need to remove "Commitment to Diversity, Equity, and Inclusion" and "Learn More About Our Benefits." and "T. Rowe Price is an equal opportunity employer..." That's EEO boilerplate, remove. Also remove "Why Join Us" maybe? That's not a standard heading but could be considered part of Benefits? But we can keep as a paragraph under Benefits? However "Why Join Us" contains substantive info about opportunity to define AI applied to native mobile engineering. That's not boilerplate; it's role description. Could be part of About the role or Responsibilities? Might be better to include as a paragraph under About the role. We need to preserve all substantive information: role summary, responsibilities list, qualifications, preferred experience, who you are, tools and technologies, benefits, pay, schedule (work flexibility). Also maybe "Work Flexibility" is schedule. We must not create sections with filler like "commensurate with experience". We have actual pay ranges. We need to output only HTML fragment, no /, no markdown. We'll structure:

About the role

Role summary paragraph(s).

Responsibilities

• ...

Requirements

• ...

(including required qualifications) Maybe also

Preferred Qualifications

but instruction only lists Qualifications, Skills, Benefits, Pay, Schedule. Could combine preferred under Requirements or Skills? But we have a separate "Preferred Experience" section. Could treat as part of Requirements (maybe as a sublist). But we need to preserve all info; we can include a

Preferred Qualifications

if we want, but instruction says use those headings as examples, not strict list. It says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those headings; we can also use others if needed? It says e.g., not exclusive. Safer to stick to those. We can put preferred experience under Requirements as a note. Skills: Tools and Technologies. Benefits: list of benefits. Pay: base salary ranges. Schedule: Work Flexibility. We also need to include maybe "Who You Are" as part of Requirements? Could be a paragraph under Requirements. Let's extract content. Company intro: At T. Rowe Price, we identify... We can include as About the role? Actually About the role should describe the role, not company. But we can include a brief About the role paragraph that includes role summary and maybe company context. The instruction: do NOT repeat the job title as a heading. So we can have About the role heading with paragraph(s) describing role and maybe company. Let's craft:

About the role

At T. Rowe Price, we identify and actively invest in opportunities to help people thrive in an evolving world. As a premier global asset management organization with more than 85 years of experience, we provide investment solutions and a broad range of equity, fixed income, and multi-asset capabilities to individuals, advisors, institutions, and retirement plan sponsors. We take an active, independent approach to investing, offering our dynamic perspective and meaningful partnership so our clients can feel more confident. We believe doing the right thing for our clients and our associates is good business. With a career at the firm, you can expect opportunities to create real impact at work and in your community. You’ll enjoy resources to support your career path, as well as compensation, benefits, and flexibility to enrich your life. Here, you’ll find a collaborative culture that respects and values differences and colleagues who share a spirit of generosity. Join us for the opportunity to grow and make a difference in ways that matter to you.

Role Summary: We are seeking an experienced, hands-on technology leader to shape how AI-enabled software engineering evolves across our mobile organization. This role will focus on designing, building, and scaling AI-native engineering workflows that improve how native mobile applications are architected, developed, tested, and released. The ideal candidate brings deep expertise in native mobile engineering, strong software architecture fundamentals, and practical experience building AI-assisted or agentic engineering systems. This person will partner closely with engineering, architecture, product, design, security, and platform teams to modernize mobile development practices and accelerate the path from requirements and design intent to production-ready software. This Role Sits At The Intersection Of Native mobile engineering leadership AI-enabled software development workflows Spec-driven engineering and technical design Agentic workflow design and orchestration Engineering quality, testing, and release automation Cross-functional technology leadership

But we might be duplicating. Better to keep role summary as a paragraph under About the role, and not repeat the company intro? The instruction says preserve ALL substantive information; we can keep company intro as part of About the role. It's substantive. Now Responsibilities: list each bullet. We need to extract responsibilities bullet points from the text. Responsibilities section includes: - Lead AI-Native Engineering for Mobile: Lead technical execution across one or more native mobile domains, partnering with engineering, architecture, product, design, security, and platform stakeholders - Translate business and product requirements into engineering-ready technical designs, implementation plans, and scalable mobile solutions - Drive high-quality engineering outcomes aligned with architecture standards, platform strategy, security requirements, and release goals - Apply AI across the software development lifecycle to improve quality, speed, consistency, and maintainability - Serve as a hands-on technical leader who defines engineering patterns and contributes to implementation - Design And Build Agentic AI Engineering Workflows: Design, build, and operationalize AI and agentic workflows that improve: - Technical analysis and decomposition - Engineering specification generation - Design-to-engineering translation - Code generation and review support - Test case generation and validation - Release readiness and deployment workflows - Documentation and engineering knowledge capture - Develop reusable engineering assets, including: - Prompt and context libraries - Agent instructions and workflow templates - Structured technical specification standards - Validation frameworks for AI-assisted outputs - Reusable native mobile implementation and testing patterns - Establish mechanisms for: - Human-in-the-loop review and engineering quality control - Workflow evaluation and continuous improvement - Performance tuning and optimization of AI-enabled systems - Traceability across AI-generated outputs, engineering decisions, and release artifacts - Modernize Native Mobile Engineering Workflows: Improve how teams move from requirements and design artifacts to engineering-ready specifications and implementation - Establish and scale spec-driven engineering practices for iOS and Android development - Integrate tools such as GitHub, CI/CD pipelines, Confluence, Figma, Jira, and AI platforms into repeatable development workflows - Strengthen design-to-code handoffs and improve engineering readiness across the delivery lifecycle - Advance automation across coding, testing, validation, and release processes - Improve software quality, observability, telemetry, and release confidence through AI-enabled engineering practices - Drive AI-Enabled Engineering Transformation: Identify opportunities to fundamentally improve how engineering work is performed through AI, not just accelerate isolated tasks - Pilot, evaluate, and scale AI-enabled engineering capabilities across native mobile teams - Assess emerging AI tools, coding assistants, frameworks, and orchestration patterns for enterprise use - Help define best practices for safe, scalable, and effective AI adoption in software engineering - Contribute to the broader engineering strategy for AI-assisted development, workflow modernization, and technical enablement - Partner Across Teams: Collaborate closely with mobile engineers, architects, platform teams, product managers, designers, and business stakeholders - Communicate complex technical concepts clearly to technical and non-technical audiences - Align engineering execution with business priorities, technical strategy, risk controls, and user experience goals - Influence engineering standards and ways of working through technical depth, credibility, and hands-on leadership We need to put each as

. Might be many; we can keep them as separate

items, but some have sub-bullets. We could flatten: each top-level bullet as

and include sub-points as separate

nested? The instruction: Use

• for any list of duties/requirements/benefits. It doesn't forbid nested lists. We can do nested
  • inside. Simplify: produce a flat list of responsibilities, each as
  • with the full sentence. Could be long but okay. We'll produce each responsibility as a
  • . For sub-bullets we can incorporate into the main
  • text separated by semicolons. But to preserve detail, we might keep sub-bullets as nested
    . That's okay. Let's do:

    Responsibilities

    • Lead AI-Native Engineering for Mobile: Lead technical execution across one or more native mobile domains, partnering with engineering, architecture, product, design, security, and platform stakeholders
    • Translate business and product requirements into engineering-ready technical designs, implementation plans, and scalable mobile solutions
    • Drive high-quality engineering outcomes aligned with architecture standards, platform strategy, security requirements, and release goals
    • Apply AI across the software development lifecycle to improve quality, speed, consistency, and maintainability
    • Serve as a hands-on technical leader who defines engineering patterns and contributes to implementation
    • Design and build agentic AI engineering workflows that improve:
      • Technical analysis and decomposition
      • Engineering specification generation
      • Design-to-engineering translation
      • Code generation and review support
      • Test case generation and validation
      • Release readiness and deployment workflows
      • Documentation and engineering knowledge capture
    • Develop reusable engineering assets, including:
      • Prompt and context libraries
      • Agent instructions and workflow templates
      • Structured technical specification standards
      • Validation frameworks for AI-assisted outputs
      • Reusable native mobile implementation and testing patterns
    • Establish mechanisms for:
      • Human-in-the-loop review and engineering quality control
      • Workflow evaluation and continuous improvement
      • Performance tuning and optimization of AI-enabled systems
      • Traceability across AI-generated outputs, engineering decisions, and release artifacts
    • Modernize native mobile engineering workflows:
      • Improve how teams move from requirements and design artifacts to engineering-ready specifications and