Senior Mobile Software Architect
for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should not repeat job title as heading. We should not include Job ID etc. We should only include sections where there is real specific content. We must not include filler like "commensurate with experience". We need to preserve all substantive info.
We need to decide which headings to use: The list given: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map content accordingly.
- About the role: could be Overview + Intro to Position combined.
- Responsibilities: the Responsibilities section.
- Requirements: maybe Minimum Qualifications? Or Requirements could be Minimum Qualifications.
- Qualifications: maybe Preferred Qualifications.
- Skills: Required Skills/Competencies.
- Benefits: Benefits section.
- Pay: Compensation/Salary Range.
- Schedule: Work Location & Requirements? Actually schedule is not present; we have Work Location & Requirements, Job Type (full-time). There's no explicit schedule like hours. Could we create a Schedule section? The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. The posting does state Compensation (salary range) and Benefits. It does not state schedule explicitly (like typical work hours). It does mention full-time, exempt, remote-permitted, travel. That's more about work location and job type. There's no explicit schedule like "Monday-Friday 9-5". So we should not create a Schedule section.
Thus we will include: About the role, Responsibilities, Requirements (minimum qualifications), Qualifications (preferred qualifications), Skills (required skills/competencies), Benefits, Pay.
We must not include headings with empty content.
We need to use - for any list of duties/requirements/benefits, and
for prose.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the details.
We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove lines like "The above duties and responsibilities are not an exhaustive list..." maybe that's boilerplate? It's a generic disclaimer; could be considered boilerplate. The instruction: remove duplicated lines, and application instructions. The line "The above duties and responsibilities are not an exhaustive list..." is a generic disclaimer; maybe we should remove it as it's not substantive? It's not specific content; it's a generic statement. Probably remove.
Also remove duplicated lines like "The range displayed reflects the minimum and maximum salaries NPR expects to provide for new hires for the position across all US locations." appears twice; we should keep only once.
Also remove EEO boilerplate at end.
Also remove "Does this sound like you? If so, we want to hear from you." (application instruction). Also remove "Want more NPR? Explore the stories..." etc.
Also remove "NPR Pay Range $184,758.33—$205,933.12 USD" maybe duplicate of compensation; we can keep one.
We need to format.
Let's extract content:
Overview: "A thriving, mission-driven multimedia organization, NPR produces award-winning news, information, and music programming in partnership with hundreds of independent public radio stations across the nation. The NPR audience values information, creativity, curiosity, and social responsibility – and our employees do too. We are innovators and leaders in diverse fields, from journalism and digital media to IT and development. Every day, our employees and member stations touch the lives of millions worldwide. Across our organization, we’re building a workplace where collaboration is essential, diverse voices are heard, and inclusion is the key to our success. We are committed to doing the right thing in our journalism and in every role at NPR. This means that integrity, adherence to our ethical standards, and compliance with legal obligations are fundamental responsibilities for every employee at NPR."
Intro to Position: "A Software Architect exemplifies technical expertise and excellence at NPR. Working alongside engineering leadership and cross-functional discipline teams, you will guide strategic technology decisions, design scalable solutions, and build robust pipelines, services, and tools that support NPR and our Member Station Network. In this role, you will lead technology strategy across our most complex engineering initiatives—those impacting multiple product lines, distributed systems, and mobile platforms simultaneously. Responsible for end-to-end architecture from platform services to client applications and downstream data pipelines, you will balance system performance, developer velocity, data privacy, and cost-efficiency to deliver exceptional public media experiences at scale."
We can combine Overview + Intro to Position as About the role.
Responsibilities: list bullet points under headings: Architectural Strategy & System Design, Cross-Team Collaboration & Governance, Operational Excellence & Mentorship. Each has sub-bullets.
We need to preserve all details. We'll create
- for each duty. Could nest? Probably just flat list items with the detailed sentences.
We'll extract each bullet:
Under Architectural Strategy & System Design:
- Architect Unified Mobile & Cross-Platform Systems: Define and implement shared architectural patterns and modular design systems across native iOS and Android codebases and cross-platform integrations to maximize code reuse and development velocity.
- Design Scalable Personalization & Delivery Pipelines: Lead platform-to-client architecture for personalized content delivery, supporting high-traffic, localized media experiences across owned digital properties and member station networks.
- Drive Technology Standards & Evaluation: Conduct technical evaluations for custom builds versus vendor solutions; introduce modern technologies and establish architectural standards across divisions.
Under Cross-Team Collaboration & Governance:
- Lead Multi-Team Engineering Initiatives: Provide technical oversight and direction across cross-divisional product roadmaps, project proposals, and OKR planning cycles for multi-team initiatives.
- Establish Quality & Code Governance: Conduct architectural proposals and code reviews, providing substantive feedback on system designs, security protocols, workflows, and peer-written software.
- Integrate Compliance & Cost Controls: Architect solutions with explicit focus on privacy compliance (GDPR/CPRA), security standards, CDN caching strategies, and cloud cost optimization frameworks.
Under Operational Excellence & Mentorship:
- Support Deployment & Operational Resilience: Participate in automated deployments across QA, UAT, and production environments; join the developer on-call rotation to diagnose and resolve critical incidents.
- Contribute High-Quality Code: Author documented, resilient code and reusable core libraries aligned with department standards and sprint commitments.
- Foster Technical Mentorship & Team Growth: Assist in onboarding, training, and interviewing software engineering staff, advocating for efficient agile processes and inclusive team practices.
We'll keep these as list items.
Minimum Qualifications: list bullet points:
- Multi-Team System Architecture: 7+ years of progressive software engineering experience, including demonstrated success designing and leading technical architecture for complex, multi-team platform environments.
- Native Mobile Engineering Expertise: Deep technical proficiency in native mobile architecture (iOS and Android) using languages such as Swift, Kotlin, Java, or Objective-C.
- Scalable Platform & API Design: Proven track record designing high-traffic, resilient distributed systems, RESTful/GraphQL APIs, and client-server integration patterns.
- Media Delivery & Infrastructure: Practical experience architecting media playback, streaming protocols, CDN configurations, and cloud infrastructure ecosystems (e.g., AWS or GCP).
- Data Privacy & Cost Optimization: Hands-on experience integrating data privacy and compliance standards (GDPR, CPRA) alongside cloud cost optimization frameworks in high-availability environments.
- CI/CD & Quality Automation: Demonstrated experience with modern version control systems (Git), continuous integration pipelines, and automated testing frameworks.
Preferred Qualifications:
- Polyglot Backend Systems: Familiarity with modern backend languages such as Go or PHP in event-driven or microservice architectures.
- Advanced Caching & Open Source: Experience optimizing edge media caches, working with relational databases/SQL, or contributing to open-source software initiatives.
Required Skills/Competencies:
- Cross-Functional Technical Governance: Ability to translate complex business and product requirements into clear, practical architectural designs accepted across multiple engineering teams.
- Technical Mentorship & Code Quality Advocacy: Strong commitment to promoting engineering best practices, conducting empathetic code reviews, and elevating overall code quality.
- Operational Resilience & Diagnostic Vision: Ability to systematically isolate, diagnose, and resolve production incidents under high-urgency conditions during on-call rotation.
- Structured Stakeholder Communication: Exceptional written and verbal communication skills to present software architecture proposals, trade-offs, and technical roadmaps to non-technical stakeholders.
- Mission-Driven Innovation: Passion for leveraging modern technology to advance public media, accessibility, and audience engagement.
Education Requirements:
- Bachelor’s degree in Computer Science, Software Engineering, Information Technology, or a related field, OR equivalent practical work experience demonstrating equivalent technical architecture capability.
Work Location & Requirements:
- NPR Remote-Permitted: This is a remote-permitted role. This role is based out of our Washington, D.C. office, but the employee may choose to work on a remote basis from a location that NPR approves. You will have the option of working (a) remotely from a location of your choosing within the United States that is supported by NPR; (b) on-site at an NPR facility, based on the availability of desks and approval from NPR; or (c) a combination of both. Regardless of where you choose to work from, you may be expected to travel to other locations from time to time to perform the duties of your position.
Job Type:
- This is a full-time, exempt position.
Compensation:
- Salary Range: The U.S.-based anticipated salary range for this opportunity is $184,758.33 - $205,933.12 plus benefits. The range displayed reflects the minimum and maximum salaries NPR expects to provide for new hires for the position across all US locations.
Benefits:
- NPR Benefits: NPR provides comprehensive benefits for employees and dependents. Regular, full-time employees scheduled to work 30 hours or more per week are eligible to enroll in NPR’s benefits options. Benefits include access to health and wellness, paid time off, and financial well-being. Plan options include medical, dental, vision, life/ accidental death and dismemberment, long-term disability, short-term disability, and voluntary retirement savings to all eligible NPR employees.
We should not duplicate the salary range line.
We need to output HTML fragment only.
We'll structure:
About the role
Overview paragraph(s) + Intro to Position paragraph(s). Could combine into one or two
elements.
We'll put Overview as one
, Intro as another
.
Then
Responsibilities
- ... each bullet as
- .
Then Requirements
(minimum qualifications)
...
Then Qualifications
(preferred qualifications)
...
Then Skills
(required skills/competencies)
...
Then Benefits
... benefits paragraph.
Then Pay
... salary range paragraph.
We might also include Work Location & Requirements and Job Type as maybe not required headings; but we could incorporate them into About the role or a separate section like "Work Location". However the instruction says use headings from list; we can add extra headings if needed? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should prefer those. However we could include Work Location & Requirements as a paragraph under About the role
for prose. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the details. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove lines like "The above duties and responsibilities are not an exhaustive list..." maybe that's boilerplate? It's a generic disclaimer; could be considered boilerplate. The instruction: remove duplicated lines, and application instructions. The line "The above duties and responsibilities are not an exhaustive list..." is a generic disclaimer; maybe we should remove it as it's not substantive? It's not specific content; it's a generic statement. Probably remove. Also remove duplicated lines like "The range displayed reflects the minimum and maximum salaries NPR expects to provide for new hires for the position across all US locations." appears twice; we should keep only once. Also remove EEO boilerplate at end. Also remove "Does this sound like you? If so, we want to hear from you." (application instruction). Also remove "Want more NPR? Explore the stories..." etc. Also remove "NPR Pay Range $184,758.33—$205,933.12 USD" maybe duplicate of compensation; we can keep one. We need to format. Let's extract content: Overview: "A thriving, mission-driven multimedia organization, NPR produces award-winning news, information, and music programming in partnership with hundreds of independent public radio stations across the nation. The NPR audience values information, creativity, curiosity, and social responsibility – and our employees do too. We are innovators and leaders in diverse fields, from journalism and digital media to IT and development. Every day, our employees and member stations touch the lives of millions worldwide. Across our organization, we’re building a workplace where collaboration is essential, diverse voices are heard, and inclusion is the key to our success. We are committed to doing the right thing in our journalism and in every role at NPR. This means that integrity, adherence to our ethical standards, and compliance with legal obligations are fundamental responsibilities for every employee at NPR." Intro to Position: "A Software Architect exemplifies technical expertise and excellence at NPR. Working alongside engineering leadership and cross-functional discipline teams, you will guide strategic technology decisions, design scalable solutions, and build robust pipelines, services, and tools that support NPR and our Member Station Network. In this role, you will lead technology strategy across our most complex engineering initiatives—those impacting multiple product lines, distributed systems, and mobile platforms simultaneously. Responsible for end-to-end architecture from platform services to client applications and downstream data pipelines, you will balance system performance, developer velocity, data privacy, and cost-efficiency to deliver exceptional public media experiences at scale." We can combine Overview + Intro to Position as About the role. Responsibilities: list bullet points under headings: Architectural Strategy & System Design, Cross-Team Collaboration & Governance, Operational Excellence & Mentorship. Each has sub-bullets. We need to preserve all details. We'll create
- for each duty. Could nest? Probably just flat list items with the detailed sentences.
We'll extract each bullet:
Under Architectural Strategy & System Design:
- Architect Unified Mobile & Cross-Platform Systems: Define and implement shared architectural patterns and modular design systems across native iOS and Android codebases and cross-platform integrations to maximize code reuse and development velocity.
- Design Scalable Personalization & Delivery Pipelines: Lead platform-to-client architecture for personalized content delivery, supporting high-traffic, localized media experiences across owned digital properties and member station networks.
- Drive Technology Standards & Evaluation: Conduct technical evaluations for custom builds versus vendor solutions; introduce modern technologies and establish architectural standards across divisions.
Under Cross-Team Collaboration & Governance:
- Lead Multi-Team Engineering Initiatives: Provide technical oversight and direction across cross-divisional product roadmaps, project proposals, and OKR planning cycles for multi-team initiatives.
- Establish Quality & Code Governance: Conduct architectural proposals and code reviews, providing substantive feedback on system designs, security protocols, workflows, and peer-written software.
- Integrate Compliance & Cost Controls: Architect solutions with explicit focus on privacy compliance (GDPR/CPRA), security standards, CDN caching strategies, and cloud cost optimization frameworks.
Under Operational Excellence & Mentorship:
- Support Deployment & Operational Resilience: Participate in automated deployments across QA, UAT, and production environments; join the developer on-call rotation to diagnose and resolve critical incidents.
- Contribute High-Quality Code: Author documented, resilient code and reusable core libraries aligned with department standards and sprint commitments.
- Foster Technical Mentorship & Team Growth: Assist in onboarding, training, and interviewing software engineering staff, advocating for efficient agile processes and inclusive team practices.
We'll keep these as list items.
Minimum Qualifications: list bullet points:
- Multi-Team System Architecture: 7+ years of progressive software engineering experience, including demonstrated success designing and leading technical architecture for complex, multi-team platform environments.
- Native Mobile Engineering Expertise: Deep technical proficiency in native mobile architecture (iOS and Android) using languages such as Swift, Kotlin, Java, or Objective-C.
- Scalable Platform & API Design: Proven track record designing high-traffic, resilient distributed systems, RESTful/GraphQL APIs, and client-server integration patterns.
- Media Delivery & Infrastructure: Practical experience architecting media playback, streaming protocols, CDN configurations, and cloud infrastructure ecosystems (e.g., AWS or GCP).
- Data Privacy & Cost Optimization: Hands-on experience integrating data privacy and compliance standards (GDPR, CPRA) alongside cloud cost optimization frameworks in high-availability environments.
- CI/CD & Quality Automation: Demonstrated experience with modern version control systems (Git), continuous integration pipelines, and automated testing frameworks.
Preferred Qualifications:
- Polyglot Backend Systems: Familiarity with modern backend languages such as Go or PHP in event-driven or microservice architectures.
- Advanced Caching & Open Source: Experience optimizing edge media caches, working with relational databases/SQL, or contributing to open-source software initiatives.
Required Skills/Competencies:
- Cross-Functional Technical Governance: Ability to translate complex business and product requirements into clear, practical architectural designs accepted across multiple engineering teams.
- Technical Mentorship & Code Quality Advocacy: Strong commitment to promoting engineering best practices, conducting empathetic code reviews, and elevating overall code quality.
- Operational Resilience & Diagnostic Vision: Ability to systematically isolate, diagnose, and resolve production incidents under high-urgency conditions during on-call rotation.
- Structured Stakeholder Communication: Exceptional written and verbal communication skills to present software architecture proposals, trade-offs, and technical roadmaps to non-technical stakeholders.
- Mission-Driven Innovation: Passion for leveraging modern technology to advance public media, accessibility, and audience engagement.
Education Requirements:
- Bachelor’s degree in Computer Science, Software Engineering, Information Technology, or a related field, OR equivalent practical work experience demonstrating equivalent technical architecture capability.
Work Location & Requirements:
- NPR Remote-Permitted: This is a remote-permitted role. This role is based out of our Washington, D.C. office, but the employee may choose to work on a remote basis from a location that NPR approves. You will have the option of working (a) remotely from a location of your choosing within the United States that is supported by NPR; (b) on-site at an NPR facility, based on the availability of desks and approval from NPR; or (c) a combination of both. Regardless of where you choose to work from, you may be expected to travel to other locations from time to time to perform the duties of your position.
Job Type:
- This is a full-time, exempt position.
Compensation:
- Salary Range: The U.S.-based anticipated salary range for this opportunity is $184,758.33 - $205,933.12 plus benefits. The range displayed reflects the minimum and maximum salaries NPR expects to provide for new hires for the position across all US locations.
Benefits:
- NPR Benefits: NPR provides comprehensive benefits for employees and dependents. Regular, full-time employees scheduled to work 30 hours or more per week are eligible to enroll in NPR’s benefits options. Benefits include access to health and wellness, paid time off, and financial well-being. Plan options include medical, dental, vision, life/ accidental death and dismemberment, long-term disability, short-term disability, and voluntary retirement savings to all eligible NPR employees.
We should not duplicate the salary range line.
We need to output HTML fragment only.
We'll structure:
About the role
Overview paragraph(s) + Intro to Position paragraph(s). Could combine into one or two
elements. We'll put Overview as one
, Intro as another
. Then
Responsibilities
- ... each bullet as
- .
Requirements
(minimum qualifications)- ...
Qualifications
(preferred qualifications)- ...
Skills
(required skills/competencies)- ...
Benefits
... benefits paragraph.
ThenPay
... salary range paragraph.
We might also include Work Location & Requirements and Job Type as maybe not required headings; but we could incorporate them into About the role or a separate section like "Work Location". However the instruction says use headings from list; we can add extra headings if needed? It says usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should prefer those. However we could include Work Location & Requirements as a paragraph under About the role