Senior Mobile App Engineer (React Native/iOS/Android)
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.
We need to decide which sections to include. The posting includes:
- Intro description about company and role: could be "About the role" (or maybe "About the role" is appropriate). It's prose.
- "What Success Looks Like" includes bullet points (list of duties). That could be "Responsibilities". It's a list.
- "In Your First 3–6 Months, You Might ..." also list of duties (maybe also responsibilities). Could combine with responsibilities.
- "What You Will Bring" includes list of qualifications/experience. That could be "Requirements" or "Qualifications". It's a list.
- "Bonus Points If You've Worked with ..." could be "Preferred Qualifications" or "Skills". Could be "Skills".
- Salary range: "The salary range for this role is $170,000 – $190,000." That's pay info. So we need a Pay section.
- Benefits: mention "The base salary is one component of the total compensation package, which includes equity, PTO and other benefits." That's benefits info. So we need Benefits section.
- Schedule: Not mentioned explicitly. There's mention of remote work, async, office hubs Boston/New York, candidates anywhere in US Eastern time zone. That's about work location/arrangement, not schedule. No explicit schedule like full-time, part-time. So we should not create Schedule section unless posting actually states it. It does not. So omit.
- Also mention "Beacon's robust asynchronous work practices ensure a first-class remote work experience, but we also have in-person office hubs located in Boston and New York. For this position we will consider candidates based anywhere in the US Eastern time zone." That could be part of About the role or maybe a separate "Location" but not required. We can incorporate into About the role paragraph.
We need to avoid duplication. Also need to remove boilerplate like EEO etc. There's none.
We need to preserve all substantive information. So we need to include all details: company mission, role description, responsibilities (What Success Looks Like, In first 3-6 months), qualifications (What You Will Bring), bonus points (maybe Skills), Pay, Benefits.
We need to decide headings: Use
for each section.
Potential sections:
- About the role (company description + role overview)
- Responsibilities (What Success Looks Like + In Your First 3–6 Months)
- Qualifications (What You Will Bring)
- Skills (Bonus Points If You've Worked with ...) maybe combine with Qualifications? But we can separate: Qualifications (required) and Skills (preferred). The instruction says prefer a few substantive sections over many thin ones. Could combine Qualifications and Skills into one "Requirements" section with sublists? But we need to use - for any list. Could have two lists under same heading? Might be okay but better to separate if they are distinct. However "prefer a few substantive sections over many thin ones" suggests we shouldn't create many sections if they are thin. The Bonus Points list is not huge but still substantive. Could combine into "Qualifications and Skills" heading.
But we have also Pay and Benefits sections.
Thus sections: About the role, Responsibilities, Qualifications, Pay, Benefits.
We need to ensure we don't create empty sections.
Now craft HTML.
We need to wrap content in appropriate tags.
For About the role: a
containing the company description and role overview. Should we split into multiple paragraphs? Could be one paragraph but might be long. It's okay.
We need to include the sentence: "Beacon Biosignals is transforming precision medicine for the brain, from clinical development to clinical care. For Life Sciences partners, we offer the leading at-home EEG platform for clinical development of novel therapeutics for neurological, psychiatric, and sleep disorders. Our Diagnostics business is building the most comprehensive at-home platform for precision diagnostics, combining EEG and cardiopulmonary signals to deliver reimbursable assessments for sleep and central nervous system disorders. Together, we're changing the way patients are diagnosed and treated for any disorder that affects brain physiology. As a Senior Mobile App Engineer, you’ll help power Beacon's mission by building cross-platform apps that interface with our EEG headbands and other wearables to capture high-fidelity data and enable seamless experiences for patients and clinicians. This isn’t just another app — you’ll be crafting tools that help unlock insights into neurological, psychiatric, and sleep disorders, with the potential to improve lives at scale. Beacon's robust asynchronous work practices ensure a first-class remote work experience, but we also have in-person office hubs located in Boston and New York. For this position we will consider candidates based anywhere in the US Eastern time zone."
That's the About the role.
Responsibilities: combine "What Success Looks Like" bullet points and "In Your First 3–6 Months, You Might". We'll create a
- list.
List items:
- Develop our React Native mobile applications and our native iOS and Android BLE device SDKs.
- Design and implement UX workflows for clinical trial participants and at-home diagnostic patients.
- Own the user experience, app performance, reliability, and observability of the apps and features you develop, leveraging feedback from real users in a diverse set of use cases and environments.
- Partner with our Devices team, other Platform teams, and product designers to develop user-centric mobile app capabilities that are deeply integrated with the rest of Beacon’s product ecosystem.
- Help shape the roadmap and technical direction of our mobile platform.
- Build a new in-app feature to validate EEG signal quality before data capture.
- Improve BLE pairing and reconnection reliability across both iOS and Android.
- Streamline onboarding for new patients and trial participants to help make our devices easier to use than ever.
- Deploy new features to help our Clinical Operations team track compliance.
We need to ensure we didn't miss any. The "What Success Looks Like" had 5 bullet points. The "In Your First 3–6 Months" had 4 bullet points. So total 9.
Now Qualifications: "What You Will Bring" list:
- 8+ years of experience in mobile development (native iOS/Android and/or React Native).
- Experience working with BLE, sensor integration, or health data streams.
- A product mindset — you care deeply about UX, edge cases, and performance.
- Familiarity with our tech stack (TypeScript, React Native, Swift, Kotlin, Expo, GitHub)
- Strong communication skills and comfort working in a collaborative, async environment
We could also include the "Bonus Points If You've Worked with ..." as part of Qualifications or separate Skills. Let's combine into Qualifications (required) and maybe add a note for bonus points as a separate list under same heading? But we need to avoid thin sections. Could add a second list under same heading labeled "Bonus points" but that would be a subheading? Not allowed because only h3 headings. Could incorporate bonus points as part of the same list but differentiate with phrasing? Might be okay to include them as separate items but they'd be mixed with required. However the instruction says preserve all substantive information; we can include them as separate list items under same heading, but we need to indicate they are bonus points. Could add a preceding sentence: "Bonus points if you have:" then list. That would be a
then
. That's acceptable.
Thus Qualifications section: a for required qualifications intro? Actually we can have a
describing required qualifications then a
for required list, then a for bonus points intro then another
for bonus list.
But we need to avoid too many thin sections; still okay.
Now Pay section: include the salary range sentence and maybe the note about base salary being one component of total compensation package, which includes equity, PTO and other benefits. Actually that sentence mentions benefits; but we have a separate Benefits section. Could put the base salary note in Pay, and benefits in Benefits.
Pay: The salary range for this role is $170,000 – $190,000. Salary ranges are determined using current market compensation data for this role and adjusted based on experience, skills, and location. The base salary is one component of the total compensation package.
Benefits: Includes equity, PTO and other benefits.
Also maybe mention cultural and scientific impact etc? That's more about values, not benefits. Could include in About the role? Might be okay to keep in About the role? The posting includes: "At Beacon, we've found that cultural and scientific impact is driven most by those that lead by example. As such, we're always seeking new contributors whose work demonstrates an avid curiosity, a bias towards simplicity, an eye for composability, a self-service mindset, and - most of all - a deep empathy towards colleagues, stakeholders, users, and patients. We believe a diverse team builds more robust systems and achieves higher impact." This is more about company values/culture. Could be part of About the role or maybe a separate "Culture" but not required headings. We could incorporate into About the role paragraph after location. That would preserve all info.
Thus About the role paragraph will be longer, including mission, role, remote work, office hubs, location, and cultural values.
Now we need to ensure we don't include any boilerplate like EEO etc. There's none.
Now produce HTML fragment:
About the role
...
Responsibilities
- ...
...
Qualifications
Required qualifications:
- ...
...
Bonus points if you have:
- ...
...
Pay
...
Benefits
...
Make sure no extra whitespace? It's fine.
Now craft the About the role paragraph precisely.
Let's copy the text:
"Beacon Biosignals is transforming precision medicine for the brain, from clinical development to clinical care. For Life Sciences partners, we offer the leading at-home EEG platform for clinical development of novel therapeutics for neurological, psychiatric, and sleep disorders. Our Diagnostics business is building the most comprehensive at-home platform for precision diagnostics, combining EEG and cardiopulmonary signals to deliver reimbursable assessments for sleep and central nervous system disorders. Together, we're changing the way patients are diagnosed and treated for any disorder that affects brain physiology. As a Senior Mobile App Engineer, you’ll help power Beacon's mission by building cross-platform apps that interface with our EEG headbands and other wearables to capture high-fidelity data and enable seamless experiences for patients and clinicians. This isn’t just another app — you’ll
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. We need to decide which sections to include. The posting includes: - Intro description about company and role: could be "About the role" (or maybe "About the role" is appropriate). It's prose. - "What Success Looks Like" includes bullet points (list of duties). That could be "Responsibilities". It's a list. - "In Your First 3–6 Months, You Might ..." also list of duties (maybe also responsibilities). Could combine with responsibilities. - "What You Will Bring" includes list of qualifications/experience. That could be "Requirements" or "Qualifications". It's a list. - "Bonus Points If You've Worked with ..." could be "Preferred Qualifications" or "Skills". Could be "Skills". - Salary range: "The salary range for this role is $170,000 – $190,000." That's pay info. So we need a Pay section. - Benefits: mention "The base salary is one component of the total compensation package, which includes equity, PTO and other benefits." That's benefits info. So we need Benefits section. - Schedule: Not mentioned explicitly. There's mention of remote work, async, office hubs Boston/New York, candidates anywhere in US Eastern time zone. That's about work location/arrangement, not schedule. No explicit schedule like full-time, part-time. So we should not create Schedule section unless posting actually states it. It does not. So omit. - Also mention "Beacon's robust asynchronous work practices ensure a first-class remote work experience, but we also have in-person office hubs located in Boston and New York. For this position we will consider candidates based anywhere in the US Eastern time zone." That could be part of About the role or maybe a separate "Location" but not required. We can incorporate into About the role paragraph. We need to avoid duplication. Also need to remove boilerplate like EEO etc. There's none. We need to preserve all substantive information. So we need to include all details: company mission, role description, responsibilities (What Success Looks Like, In first 3-6 months), qualifications (What You Will Bring), bonus points (maybe Skills), Pay, Benefits. We need to decide headings: Use
for each section.
Potential sections:
- About the role (company description + role overview)
- Responsibilities (What Success Looks Like + In Your First 3–6 Months)
- Qualifications (What You Will Bring)
- Skills (Bonus Points If You've Worked with ...) maybe combine with Qualifications? But we can separate: Qualifications (required) and Skills (preferred). The instruction says prefer a few substantive sections over many thin ones. Could combine Qualifications and Skills into one "Requirements" section with sublists? But we need to use - for any list. Could have two lists under same heading? Might be okay but better to separate if they are distinct. However "prefer a few substantive sections over many thin ones" suggests we shouldn't create many sections if they are thin. The Bonus Points list is not huge but still substantive. Could combine into "Qualifications and Skills" heading.
But we have also Pay and Benefits sections.
Thus sections: About the role, Responsibilities, Qualifications, Pay, Benefits.
We need to ensure we don't create empty sections.
Now craft HTML.
We need to wrap content in appropriate tags.
For About the role: a
containing the company description and role overview. Should we split into multiple paragraphs? Could be one paragraph but might be long. It's okay.
We need to include the sentence: "Beacon Biosignals is transforming precision medicine for the brain, from clinical development to clinical care. For Life Sciences partners, we offer the leading at-home EEG platform for clinical development of novel therapeutics for neurological, psychiatric, and sleep disorders. Our Diagnostics business is building the most comprehensive at-home platform for precision diagnostics, combining EEG and cardiopulmonary signals to deliver reimbursable assessments for sleep and central nervous system disorders. Together, we're changing the way patients are diagnosed and treated for any disorder that affects brain physiology. As a Senior Mobile App Engineer, you’ll help power Beacon's mission by building cross-platform apps that interface with our EEG headbands and other wearables to capture high-fidelity data and enable seamless experiences for patients and clinicians. This isn’t just another app — you’ll be crafting tools that help unlock insights into neurological, psychiatric, and sleep disorders, with the potential to improve lives at scale. Beacon's robust asynchronous work practices ensure a first-class remote work experience, but we also have in-person office hubs located in Boston and New York. For this position we will consider candidates based anywhere in the US Eastern time zone."
That's the About the role.
Responsibilities: combine "What Success Looks Like" bullet points and "In Your First 3–6 Months, You Might". We'll create a
- list.
List items:
- Develop our React Native mobile applications and our native iOS and Android BLE device SDKs.
- Design and implement UX workflows for clinical trial participants and at-home diagnostic patients.
- Own the user experience, app performance, reliability, and observability of the apps and features you develop, leveraging feedback from real users in a diverse set of use cases and environments.
- Partner with our Devices team, other Platform teams, and product designers to develop user-centric mobile app capabilities that are deeply integrated with the rest of Beacon’s product ecosystem.
- Help shape the roadmap and technical direction of our mobile platform.
- Build a new in-app feature to validate EEG signal quality before data capture.
- Improve BLE pairing and reconnection reliability across both iOS and Android.
- Streamline onboarding for new patients and trial participants to help make our devices easier to use than ever.
- Deploy new features to help our Clinical Operations team track compliance.
We need to ensure we didn't miss any. The "What Success Looks Like" had 5 bullet points. The "In Your First 3–6 Months" had 4 bullet points. So total 9.
Now Qualifications: "What You Will Bring" list:
- 8+ years of experience in mobile development (native iOS/Android and/or React Native).
- Experience working with BLE, sensor integration, or health data streams.
- A product mindset — you care deeply about UX, edge cases, and performance.
- Familiarity with our tech stack (TypeScript, React Native, Swift, Kotlin, Expo, GitHub)
- Strong communication skills and comfort working in a collaborative, async environment
We could also include the "Bonus Points If You've Worked with ..." as part of Qualifications or separate Skills. Let's combine into Qualifications (required) and maybe add a note for bonus points as a separate list under same heading? But we need to avoid thin sections. Could add a second list under same heading labeled "Bonus points" but that would be a subheading? Not allowed because only h3 headings. Could incorporate bonus points as part of the same list but differentiate with phrasing? Might be okay to include them as separate items but they'd be mixed with required. However the instruction says preserve all substantive information; we can include them as separate list items under same heading, but we need to indicate they are bonus points. Could add a preceding sentence: "Bonus points if you have:" then list. That would be a
then
. That's acceptable.
Thus Qualifications section: a for required qualifications intro? Actually we can have a
describing required qualifications then a
for required list, then a for bonus points intro then another
for bonus list.
But we need to avoid too many thin sections; still okay.
Now Pay section: include the salary range sentence and maybe the note about base salary being one component of total compensation package, which includes equity, PTO and other benefits. Actually that sentence mentions benefits; but we have a separate Benefits section. Could put the base salary note in Pay, and benefits in Benefits.
Pay: The salary range for this role is $170,000 – $190,000. Salary ranges are determined using current market compensation data for this role and adjusted based on experience, skills, and location. The base salary is one component of the total compensation package.
Benefits: Includes equity, PTO and other benefits.
Also maybe mention cultural and scientific impact etc? That's more about values, not benefits. Could include in About the role? Might be okay to keep in About the role? The posting includes: "At Beacon, we've found that cultural and scientific impact is driven most by those that lead by example. As such, we're always seeking new contributors whose work demonstrates an avid curiosity, a bias towards simplicity, an eye for composability, a self-service mindset, and - most of all - a deep empathy towards colleagues, stakeholders, users, and patients. We believe a diverse team builds more robust systems and achieves higher impact." This is more about company values/culture. Could be part of About the role or maybe a separate "Culture" but not required headings. We could incorporate into About the role paragraph after location. That would preserve all info.
Thus About the role paragraph will be longer, including mission, role, remote work, office hubs, location, and cultural values.
Now we need to ensure we don't include any boilerplate like EEO etc. There's none.
Now produce HTML fragment:
About the role
...
Responsibilities
- ...
...
Qualifications
Required qualifications:
- ...
...
Bonus points if you have:
- ...
...
Pay
...
Benefits
...
Make sure no extra whitespace? It's fine.
Now craft the About the role paragraph precisely.
Let's copy the text:
"Beacon Biosignals is transforming precision medicine for the brain, from clinical development to clinical care. For Life Sciences partners, we offer the leading at-home EEG platform for clinical development of novel therapeutics for neurological, psychiatric, and sleep disorders. Our Diagnostics business is building the most comprehensive at-home platform for precision diagnostics, combining EEG and cardiopulmonary signals to deliver reimbursable assessments for sleep and central nervous system disorders. Together, we're changing the way patients are diagnosed and treated for any disorder that affects brain physiology. As a Senior Mobile App Engineer, you’ll help power Beacon's mission by building cross-platform apps that interface with our EEG headbands and other wearables to capture high-fidelity data and enable seamless experiences for patients and clinicians. This isn’t just another app — you’ll
containing the company description and role overview. Should we split into multiple paragraphs? Could be one paragraph but might be long. It's okay. We need to include the sentence: "Beacon Biosignals is transforming precision medicine for the brain, from clinical development to clinical care. For Life Sciences partners, we offer the leading at-home EEG platform for clinical development of novel therapeutics for neurological, psychiatric, and sleep disorders. Our Diagnostics business is building the most comprehensive at-home platform for precision diagnostics, combining EEG and cardiopulmonary signals to deliver reimbursable assessments for sleep and central nervous system disorders. Together, we're changing the way patients are diagnosed and treated for any disorder that affects brain physiology. As a Senior Mobile App Engineer, you’ll help power Beacon's mission by building cross-platform apps that interface with our EEG headbands and other wearables to capture high-fidelity data and enable seamless experiences for patients and clinicians. This isn’t just another app — you’ll be crafting tools that help unlock insights into neurological, psychiatric, and sleep disorders, with the potential to improve lives at scale. Beacon's robust asynchronous work practices ensure a first-class remote work experience, but we also have in-person office hubs located in Boston and New York. For this position we will consider candidates based anywhere in the US Eastern time zone." That's the About the role. Responsibilities: combine "What Success Looks Like" bullet points and "In Your First 3–6 Months, You Might". We'll create a
- list.
List items:
- Develop our React Native mobile applications and our native iOS and Android BLE device SDKs.
- Design and implement UX workflows for clinical trial participants and at-home diagnostic patients.
- Own the user experience, app performance, reliability, and observability of the apps and features you develop, leveraging feedback from real users in a diverse set of use cases and environments.
- Partner with our Devices team, other Platform teams, and product designers to develop user-centric mobile app capabilities that are deeply integrated with the rest of Beacon’s product ecosystem.
- Help shape the roadmap and technical direction of our mobile platform.
- Build a new in-app feature to validate EEG signal quality before data capture.
- Improve BLE pairing and reconnection reliability across both iOS and Android.
- Streamline onboarding for new patients and trial participants to help make our devices easier to use than ever.
- Deploy new features to help our Clinical Operations team track compliance.
We need to ensure we didn't miss any. The "What Success Looks Like" had 5 bullet points. The "In Your First 3–6 Months" had 4 bullet points. So total 9.
Now Qualifications: "What You Will Bring" list:
- 8+ years of experience in mobile development (native iOS/Android and/or React Native).
- Experience working with BLE, sensor integration, or health data streams.
- A product mindset — you care deeply about UX, edge cases, and performance.
- Familiarity with our tech stack (TypeScript, React Native, Swift, Kotlin, Expo, GitHub)
- Strong communication skills and comfort working in a collaborative, async environment
We could also include the "Bonus Points If You've Worked with ..." as part of Qualifications or separate Skills. Let's combine into Qualifications (required) and maybe add a note for bonus points as a separate list under same heading? But we need to avoid thin sections. Could add a second list under same heading labeled "Bonus points" but that would be a subheading? Not allowed because only h3 headings. Could incorporate bonus points as part of the same list but differentiate with phrasing? Might be okay to include them as separate items but they'd be mixed with required. However the instruction says preserve all substantive information; we can include them as separate list items under same heading, but we need to indicate they are bonus points. Could add a preceding sentence: "Bonus points if you have:" then list. That would be a
then
- . That's acceptable.
Thus Qualifications section: a
- ... ...
- ... ...
- ... ...
for required qualifications intro? Actually we can have a
describing required qualifications then a
- for required list, then a
for bonus points intro then another
- for bonus list.
But we need to avoid too many thin sections; still okay.
Now Pay section: include the salary range sentence and maybe the note about base salary being one component of total compensation package, which includes equity, PTO and other benefits. Actually that sentence mentions benefits; but we have a separate Benefits section. Could put the base salary note in Pay, and benefits in Benefits.
Pay:
The salary range for this role is $170,000 – $190,000. Salary ranges are determined using current market compensation data for this role and adjusted based on experience, skills, and location. The base salary is one component of the total compensation package.
Benefits:Includes equity, PTO and other benefits.
Also maybe mention cultural and scientific impact etc? That's more about values, not benefits. Could include in About the role? Might be okay to keep in About the role? The posting includes: "At Beacon, we've found that cultural and scientific impact is driven most by those that lead by example. As such, we're always seeking new contributors whose work demonstrates an avid curiosity, a bias towards simplicity, an eye for composability, a self-service mindset, and - most of all - a deep empathy towards colleagues, stakeholders, users, and patients. We believe a diverse team builds more robust systems and achieves higher impact." This is more about company values/culture. Could be part of About the role or maybe a separate "Culture" but not required headings. We could incorporate into About the role paragraph after location. That would preserve all info. Thus About the role paragraph will be longer, including mission, role, remote work, office hubs, location, and cultural values. Now we need to ensure we don't include any boilerplate like EEO etc. There's none. Now produce HTML fragment:About the role
...
Responsibilities
Qualifications
Required qualifications:
Bonus points if you have:
Pay
...
Benefits
...
Make sure no extra whitespace? It's fine. Now craft the About the role paragraph precisely. Let's copy the text: "Beacon Biosignals is transforming precision medicine for the brain, from clinical development to clinical care. For Life Sciences partners, we offer the leading at-home EEG platform for clinical development of novel therapeutics for neurological, psychiatric, and sleep disorders. Our Diagnostics business is building the most comprehensive at-home platform for precision diagnostics, combining EEG and cardiopulmonary signals to deliver reimbursable assessments for sleep and central nervous system disorders. Together, we're changing the way patients are diagnosed and treated for any disorder that affects brain physiology. As a Senior Mobile App Engineer, you’ll help power Beacon's mission by building cross-platform apps that interface with our EEG headbands and other wearables to capture high-fidelity data and enable seamless experiences for patients and clinicians. This isn’t just another app — you’ll