Mobile Engineer (iOS)
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
Thus we need to decide which sections to include based on content.
We have:
- About the role: The first paragraph describing role. Could be "About the role". We'll include that.
- Responsibilities: "Key Responsibilities" bullet list.
- Qualifications: "Qualifications" bullet list.
- Skills: maybe "Tech Stack" could be considered Skills. Could also be "Skills". We'll include a Skills section for tech stack.
- Benefits: The posting mentions visa sponsorship, relocation support, maybe also "We offer visa sponsorship and can support relocation". That's a benefit. Also maybe "We’re proud to be a global team...". Not explicit benefits like health insurance, etc. But visa sponsorship and relocation are benefits. So we can include Benefits section with those points.
- Pay: Not mentioned. So omit.
- Schedule: Not mentioned (in-person role based in San Francisco). Could be schedule? Not explicit. So omit.
- Work Location & Environment: Could be part of About the role or separate. But we have a section for Work Location & Environment? Not in allowed headings list; allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should not create a custom heading like Work Location & Environment. Instead we can fold that info into About the role or Benefits? The location is "in-person role based in San Francisco". Could be part of About the role. We'll include that in About the role paragraph.
- "Why we are building this", "About Superpower", "Superpower OverviewCulture..." etc. Those are company description; could be part of About the role? Might be considered extra but we need to preserve ALL substantive information. However we cannot create arbitrary headings not in list. We could incorporate that content into About the role section as prose. That's allowed: we can have multiple paragraphs under About the role.
Thus we will have sections: About the role, Responsibilities, Qualifications, Skills, Benefits.
We need to use
for each section heading.
Inside each section, we need to use
for prose,
- for lists.
We must not repeat the job title as heading.
We must preserve all substantive information: responsibilities list, qualifications list, tech stack, benefits (visa sponsorship, relocation), location, company mission, etc.
We need to avoid boilerplate like cookie/navigation/legal/EEO etc. There's none.
We must not invent or summarize away detail.
Let's extract content.
Original text:
"The role As a Mobile Engineer at Superpower, you will own the quality and development of our iOS experience. You will collaborate with product, design, and engineering to build fast, intuitive experiences that help members understand their health and take action. This is a hands-on opportunity to shape the app’s architecture, build its core features, and take responsibility for the experience from development through App Store release. You will work across Swift, SwiftUI, and UIKit and React Native, Expo, and TypeScript, with strong hands-on expertise in both native iOS and React Native development. You will shape our mobile architecture, build native integrations, and choose the right approach for each experience based on performance, product quality, and development speed."
That's the role description.
Then "Key Responsibilities" list:
- Design and build mobile experiences in Swift and React Native for health results, biomarker data, chat, and other core member journeys.
- Collaborate with product, design, and clinical teams to make complex health information clear and useful.
- Own mobile architecture, reusable components, and the integration between Swift and React Native, including native capabilities such as HealthKit, authentication, notifications, and media access.
- Improve app performance, navigation, accessibility, and reliability across devices and network conditions.
- Own testing, observability, release tooling, and App Store delivery, with careful handling of sensitive health information.
- Work with web and backend engineers on shared data contracts, reusable logic, and development patterns that help the team ship across platforms.
Then "Qualifications":
- A strong record of shipping and maintaining consumer iOS applications, with clear ownership of the work and its impact on users.
- Deep experience with Swift, including native app architecture, concurrency, memory management, production debugging, and performance optimization.
- Deep experience with React Native, Expo, and TypeScript, including app architecture, state management, production debugging, and performance optimization.
- Strong experience with SwiftUI and UIKit, Apple’s frameworks, and building native modules that connect Swift with React Native.
- Strong understanding of app architecture, state management, networking, testing, and App Store release processes.
- Excellent product judgment and attention to interaction details, with the ability to balance quality and delivery speed.
- Demonstrated ability to work independently in a startup or small engineering team.
- An interest in healthcare, wellness, or longevity is a strong plus.
Then "Tech Stack Native iOS: Swift, SwiftUI, UIKit, Xcode Mobile Frameworks: React Native, Expo, TypeScript Native & Web Integration: HealthKit, Expo Modules, React Native WebView Product & Services: React, Node.js, Go, shared data contracts and packages Design & Ops: Figma, Linear, Notion, Slack"
We can present as a list or prose. Probably a list under Skills.
Then "Work Location & Environment This is an in-person role based in San Francisco. You will work closely with product, design, clinical, and engineering teammates in a small team with substantial ownership over what we build and how we build it."
Then "Why we are building this We believe better health gives people more freedom to do the things that matter to them. Understanding and managing your health should be simpler, more personal, and part of everyday life. Superpower is the product we’ve always wanted: a thoughtfully designed, all-in-one platform for understanding and improving our health."
Then "About Superpower Superpower is a new health system on a mission to extend and enhance human life. We started with lab testing, then data aggregation / digital twin, then an AI doctor, and now peptides. Over the past 6 months, we have grown 10x whilst halving CAC. Now we are gearing up for hyper growth. You can find more about us below: superpower.com/series-a"
Then "Superpower OverviewCulture at Superpower Company Philosophies We are all here to genuinely do our life’s best workInsanely high talent bar, never settling. A players only (see Steve Jobs)We live to work as much as we work to live. But we sustainably espouse the superpower ethos of putting health firstWe aim to set the gold standard for team health culture on the planet — live the ethos! Investors Forerunner (Top consumer healthcare VC in the world; early board members of Hims and Oura; Kirsten, founder of Forerunner, led our Series A)8VC (leading health and bio investor)Evan Moore (Founder of Doordash; Partner at Khosla Ventures)Cyan Bannister (early investor into Uber and SpaceX, former partner at Founder’s Fund, regarded as one of the top angels in the world)Balaji Srinivasan (ex-Coinbase CTO and angel, ex-General Partner at a16z)Arielle Zuckerberg (active angel, tech leader, relatively famous brother)Cameron & Tyler WinklevossSusa Ventures (tier 1 healthcare VC)Bond Capital (General Partner Jay Simons' early-stage fund within Bond)Long Journey Ventures (investor in Uber, Notion, Loom, Affirm etc.)InfluencersShaan Puri (angel and podcast host of my first million)Brooke Monke (50 million followers across socials)Logan PaulSteve AokiJustin Mares (founder of Truemed)Giannis AntetokounmpoKylian Mbappé We’re proud to be a global team and welcome talent from around the world. We offer visa sponsorship and can support relocation to the United States for the right candidates. Much of our team is international, and we’re committed to building a team of top-tier talent."
We need to preserve all substantive information. That includes the mission, culture, investors, influencers, visa sponsorship, relocation.
We can include that in About the role section as prose, or maybe we could add a separate section like "About the company" but not allowed headings. So we fold into About the role.
Thus About the role will contain multiple paragraphs: role description, location, why we are building this, about Superpower, culture, investors, influencers, visa sponsorship, relocation.
We must not create headings for those subtopics.
Now we need to output HTML fragment.
Structure:
About the role
... paragraphs ...
Responsibilities
- ...
...
Qualifications
- ...
...
Skills
- ...
...
Benefits
- Visa sponsorship
- Relocation support to the United States
We could also include "global team" etc but that's not a benefit per se. Could be part of About the role.
Make sure we preserve all details: mention "in-person role based in San Francisco". Include that in About the role.
Include "You will work closely with product, design, clinical, and engineering teammates in a small team with substantial ownership over what we build and how we build it." That's also part of About the role.
Include "Why we are building this" paragraph.
Include "About Superpower" paragraph.
Include "Superpower OverviewCulture at Superpower Company Philosophies..." paragraph.
Include investors list.
Include influencers list.
Include visa sponsorship and relocation.
We must not omit any of those.
We need to be careful not to break HTML: ensure proper escaping of special characters like &, <, >. The text includes ampersands, etc. We need to escape them as & etc. Also apostrophes are fine.
We'll need to escape any HTML special characters: &, <, >, ". Also maybe we have curly quotes ’ “ ” etc. Those are okay but better to replace with standard apostrophe? We'll keep as is; they are not HTML special. But we need to escape &.
Let's craft the About the role paragraph(s). Could be multiple elements under the same heading? The instruction: Use
for prose. It didn't say we cannot have multiple <
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. Thus we need to decide which sections to include based on content. We have: - About the role: The first paragraph describing role. Could be "About the role". We'll include that. - Responsibilities: "Key Responsibilities" bullet list. - Qualifications: "Qualifications" bullet list. - Skills: maybe "Tech Stack" could be considered Skills. Could also be "Skills". We'll include a Skills section for tech stack. - Benefits: The posting mentions visa sponsorship, relocation support, maybe also "We offer visa sponsorship and can support relocation". That's a benefit. Also maybe "We’re proud to be a global team...". Not explicit benefits like health insurance, etc. But visa sponsorship and relocation are benefits. So we can include Benefits section with those points. - Pay: Not mentioned. So omit. - Schedule: Not mentioned (in-person role based in San Francisco). Could be schedule? Not explicit. So omit. - Work Location & Environment: Could be part of About the role or separate. But we have a section for Work Location & Environment? Not in allowed headings list; allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should not create a custom heading like Work Location & Environment. Instead we can fold that info into About the role or Benefits? The location is "in-person role based in San Francisco". Could be part of About the role. We'll include that in About the role paragraph. - "Why we are building this", "About Superpower", "Superpower OverviewCulture..." etc. Those are company description; could be part of About the role? Might be considered extra but we need to preserve ALL substantive information. However we cannot create arbitrary headings not in list. We could incorporate that content into About the role section as prose. That's allowed: we can have multiple paragraphs under About the role. Thus we will have sections: About the role, Responsibilities, Qualifications, Skills, Benefits. We need to use
for each section heading. Inside each section, we need to use
for prose,
- for lists.
We must not repeat the job title as heading.
We must preserve all substantive information: responsibilities list, qualifications list, tech stack, benefits (visa sponsorship, relocation), location, company mission, etc.
We need to avoid boilerplate like cookie/navigation/legal/EEO etc. There's none.
We must not invent or summarize away detail.
Let's extract content.
Original text:
"The role As a Mobile Engineer at Superpower, you will own the quality and development of our iOS experience. You will collaborate with product, design, and engineering to build fast, intuitive experiences that help members understand their health and take action. This is a hands-on opportunity to shape the app’s architecture, build its core features, and take responsibility for the experience from development through App Store release. You will work across Swift, SwiftUI, and UIKit and React Native, Expo, and TypeScript, with strong hands-on expertise in both native iOS and React Native development. You will shape our mobile architecture, build native integrations, and choose the right approach for each experience based on performance, product quality, and development speed."
That's the role description.
Then "Key Responsibilities" list:
- Design and build mobile experiences in Swift and React Native for health results, biomarker data, chat, and other core member journeys.
- Collaborate with product, design, and clinical teams to make complex health information clear and useful.
- Own mobile architecture, reusable components, and the integration between Swift and React Native, including native capabilities such as HealthKit, authentication, notifications, and media access.
- Improve app performance, navigation, accessibility, and reliability across devices and network conditions.
- Own testing, observability, release tooling, and App Store delivery, with careful handling of sensitive health information.
- Work with web and backend engineers on shared data contracts, reusable logic, and development patterns that help the team ship across platforms.
Then "Qualifications":
- A strong record of shipping and maintaining consumer iOS applications, with clear ownership of the work and its impact on users.
- Deep experience with Swift, including native app architecture, concurrency, memory management, production debugging, and performance optimization.
- Deep experience with React Native, Expo, and TypeScript, including app architecture, state management, production debugging, and performance optimization.
- Strong experience with SwiftUI and UIKit, Apple’s frameworks, and building native modules that connect Swift with React Native.
- Strong understanding of app architecture, state management, networking, testing, and App Store release processes.
- Excellent product judgment and attention to interaction details, with the ability to balance quality and delivery speed.
- Demonstrated ability to work independently in a startup or small engineering team.
- An interest in healthcare, wellness, or longevity is a strong plus.
Then "Tech Stack Native iOS: Swift, SwiftUI, UIKit, Xcode Mobile Frameworks: React Native, Expo, TypeScript Native & Web Integration: HealthKit, Expo Modules, React Native WebView Product & Services: React, Node.js, Go, shared data contracts and packages Design & Ops: Figma, Linear, Notion, Slack"
We can present as a list or prose. Probably a list under Skills.
Then "Work Location & Environment This is an in-person role based in San Francisco. You will work closely with product, design, clinical, and engineering teammates in a small team with substantial ownership over what we build and how we build it."
Then "Why we are building this We believe better health gives people more freedom to do the things that matter to them. Understanding and managing your health should be simpler, more personal, and part of everyday life. Superpower is the product we’ve always wanted: a thoughtfully designed, all-in-one platform for understanding and improving our health."
Then "About Superpower Superpower is a new health system on a mission to extend and enhance human life. We started with lab testing, then data aggregation / digital twin, then an AI doctor, and now peptides. Over the past 6 months, we have grown 10x whilst halving CAC. Now we are gearing up for hyper growth. You can find more about us below: superpower.com/series-a"
Then "Superpower OverviewCulture at Superpower Company Philosophies We are all here to genuinely do our life’s best workInsanely high talent bar, never settling. A players only (see Steve Jobs)We live to work as much as we work to live. But we sustainably espouse the superpower ethos of putting health firstWe aim to set the gold standard for team health culture on the planet — live the ethos! Investors Forerunner (Top consumer healthcare VC in the world; early board members of Hims and Oura; Kirsten, founder of Forerunner, led our Series A)8VC (leading health and bio investor)Evan Moore (Founder of Doordash; Partner at Khosla Ventures)Cyan Bannister (early investor into Uber and SpaceX, former partner at Founder’s Fund, regarded as one of the top angels in the world)Balaji Srinivasan (ex-Coinbase CTO and angel, ex-General Partner at a16z)Arielle Zuckerberg (active angel, tech leader, relatively famous brother)Cameron & Tyler WinklevossSusa Ventures (tier 1 healthcare VC)Bond Capital (General Partner Jay Simons' early-stage fund within Bond)Long Journey Ventures (investor in Uber, Notion, Loom, Affirm etc.)InfluencersShaan Puri (angel and podcast host of my first million)Brooke Monke (50 million followers across socials)Logan PaulSteve AokiJustin Mares (founder of Truemed)Giannis AntetokounmpoKylian Mbappé We’re proud to be a global team and welcome talent from around the world. We offer visa sponsorship and can support relocation to the United States for the right candidates. Much of our team is international, and we’re committed to building a team of top-tier talent."
We need to preserve all substantive information. That includes the mission, culture, investors, influencers, visa sponsorship, relocation.
We can include that in About the role section as prose, or maybe we could add a separate section like "About the company" but not allowed headings. So we fold into About the role.
Thus About the role will contain multiple paragraphs: role description, location, why we are building this, about Superpower, culture, investors, influencers, visa sponsorship, relocation.
We must not create headings for those subtopics.
Now we need to output HTML fragment.
Structure:
About the role
... paragraphs ...
Responsibilities
- ... ...
Qualifications
- ... ...
Skills
- ... ...
Benefits
- Visa sponsorship
- Relocation support to the United States
elements under the same heading? The instruction: Use
for prose. It didn't say we cannot have multiple <