Principal Software Engineer – Android
for each heading. Use - for any list of duties/requirements/benefits. Use
for prose. Do NOT repeat job title as heading. Do NOT put Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions.
We need to preserve all substantive information. Let's parse the posting.
First paragraph: "This is where your work makes a difference..." This is about company mission, culture. Could be "About the role"? Actually "About the role" maybe includes description of role and company. The posting includes a paragraph about Baxter mission, then "As a Principal Android Software Engineer, you will lead architecture..." That's role description. So we can put that under About the role (or maybe Responsibilities). The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content.
We have:
- About the role: Could include company mission and role overview. The first paragraph about Baxter mission and "This is where your work saves lives". Then "As a Principal Android Software Engineer, you will lead architecture and delivery..." That's role overview. So we can put that in About the role.
- Responsibilities: The bullet list under "What you'll be doing:" includes many responsibilities. Those are duties. So we can put that under Responsibilities as a list.
- Requirements: The bullet list under "What you'll bring:" includes education, experience, etc. That's qualifications/requirements. Could be Requirements.
- Qualifications: Might overlap with Requirements. But we can separate: maybe Requirements = experience/education, Qualifications = specific technical expertise? However the instruction says prefer few substantive sections over many thin ones. We could combine Requirements and Qualifications into one section? But headings are predefined; we should only emit heading if we have real specific content for it. We could put all under Requirements and skip Qualifications if content overlaps. But we need to see if there is distinct content for Qualifications separate from Requirements. The "What you'll bring:" includes Bachelor's degree, 10+ years experience, proven experience leading technical architecture, expertise in Kotlin, experience building reusable SDKs, hands-on experience integrating cameras, strong problem-solving, communication, experience in healthcare/medical devices. That's basically qualifications. Could treat as Requirements. Could also treat as Qualifications. But we need to avoid duplicate sections. Perhaps we can put Requirements for education/experience, and Qualifications for technical skills. But the instruction says prefer few substantive sections over many thin ones. So maybe we just have one section for Requirements/Qualifications combined, but we need to pick a heading. Which heading is more appropriate? The posting includes "What you'll bring:" which is typical qualifications. So we could use "Qualifications". But also there is no separate "Requirements" heading content besides that. Could we put everything under "Qualifications"? Then we would not have a Requirements section. That's okay if we don't have content for Requirements. But we need to ensure we don't miss any content. The "What you'll bring:" includes education, experience, expertise, etc. That's qualifications. So we can put that under Qualifications.
But we also have "What you'll be doing:" responsibilities. So we have Responsibilities.
We also have Benefits section: there is a paragraph about US Benefits. That's substantive. So we need Benefits heading.
Pay: there is salary range: "The estimated base salary for this position is $120,000-$165,000 annually." Also mention discretionary bonuses. So we have Pay content.
Schedule: there is mention of flexible workplace policy: "Baxter is committed to supporting the needs for flexibility in the workplace. We do so through our flexible workplace policy which includes a required minimum number of days a week onsite." That's schedule info. So we have Schedule content.
Thus we have sections: About the role, Responsibilities, Qualifications, Benefits, Pay, Schedule. Possibly also Skills? The posting includes skills embedded in qualifications; but we could treat Skills as part of Qualifications. Since we already have Qualifications, we might not need Skills separate. The instruction says prefer few substantive sections over many thin ones. So we can omit Skills if its content is covered elsewhere.
Now we need to format.
We must not include boilerplate: EEO, equal opportunity, reasonable accommodations, recruitment fraud notice, etc. Also remove duplicated lines, navigation, cookie, legal, application instructions (like "please speak to the recruiter", "visit our Benefits site", etc). Also remove "Applicants must be authorized to work for any employer in the U.S. We are unable to sponsor or take over sponsorship of an employment visa at this time." That's maybe considered boilerplate? It's a requirement about work authorization. Could be considered a requirement. But it's also a legal statement. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is a legal requirement about work authorization; might be considered boilerplate? It's not EEO but it's a legal requirement. Might be considered part of Requirements? However it's a standard statement; but it's substantive? It says applicants must be authorized to work in US, no sponsorship. That is a requirement. Could keep under Requirements/Qualifications. But the instruction says remove legal boilerplate. This is a legal statement about work authorization; might be considered boilerplate. Safer to remove it.
Also remove "For questions about this, our pay philosophy, and available benefits, please speak to the recruiter if you decide to apply and are selected for an interview." That's application instruction; remove.
Also remove "For additional information regarding Baxter US Benefits, please speak with your recruiter or visit our Benefits site: Benefits | Baxter" - remove.
Also remove "Know Your Rights: Workplace Discrimination is Illegal Reasonable Accommodations ..." - remove.
Also remove "Recruitment Fraud Notice ..." - remove.
Also remove "We understand compensation is an important factor..." maybe part of Pay? It's about compensation philosophy; could keep as part of Pay? But it's somewhat generic. However we already have salary range; we could keep the sentence about estimated base salary and discretionary bonuses. The rest about pay philosophy maybe boilerplate? It's not strictly boilerplate but could be considered fluff. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The pay philosophy sentences are substantive? They talk about equitable pay, transparency, etc. Might be considered substantive but could be considered boilerplate. I'd keep the salary range and mention of discretionary bonuses; maybe also the sentence about individual pay based on location, skills, etc. That's substantive. The earlier sentence "We understand compensation is an important factor..." is more fluff; could drop. But to be safe, keep the substantive parts: estimated base salary, discretionary bonuses, individual pay based on location, skills, expertise, experience, and other relevant factors. That's enough.
Now Benefits: we have a paragraph describing benefits. Need to keep substantive: medical and dental coverage start day one, insurance for basic life, accident, short-term and long-term disability, business travel accident insurance. Financial and retirement benefits: ESPP, 401(k) RSP with employee contributions and company matching. Flexible Spending Accounts, educational assistance programs, time-off benefits: paid holidays, paid time off ranging from 20 to 35 days based on length of service, family and medical leaves of absence, paid parental leave. Additional benefits: commuting benefits, Employee Discount Program, Employee Assistance Program (EAP), childcare benefits. We should keep that.
Now Schedule: flexible workplace policy includes required minimum number of days a week onsite. Also mention policy subject to local laws, may adjust, suspend, discontinue. That's schedule info.
Now About the role: we need to capture the mission paragraph and role overview. Let's extract:
"This is where your work makes a difference. At Baxter, we believe every person—regardless of who they are or where they are from—deserves a chance to live a healthy life. It was our founding belief in 1931 and continues to be our guiding principle. We are redefining healthcare delivery to make a greater impact today, tomorrow, and beyond. Our Baxter colleagues are united by our Mission to Save and Sustain Lives. Together, our community is driven by a culture of courage, trust, and collaboration. Every individual is empowered to take ownership and make a meaningful impact. We strive for efficient and effective operations, and we hold each other accountable for delivering exceptional results. Here, you will find more than just a job—you will find purpose and pride. This is where your work saves lives As a Principal Android Software Engineer, you will lead architecture and delivery of shared Android capabilities that power multiple clinical product applications worldwide. You will own significant portions of the Android system design—reusable services and libraries, hybrid WebView/React UI foundations, device connectivity patterns, and common clinical workflows—while mentoring engineers and raising the bar for quality in a regulated medical-device environment. An ideal candidate brings deep hands-on Android expertise, a clear technical vision for multi-product platform software, and the ability to drive complex cross-team decisions independently. Strong communication and collaboration with product teams, systems, hardware, and other platform partners are essential."
We need to ensure we don't repeat the job title as heading; we are not using it as heading. It's okay to appear in paragraph.
Now Responsibilities: list from "What you'll be doing:" with bullet points. Let's extract each bullet:
- Lead Platform Android Architecture and Delivery: Define and evolve shared Android platform architecture (Kotlin services, DI, WebView/JS bridge patterns, messaging/broker integration, networking foundations) used by multiple product apps, and drive implementation of high-reliability reusable capabilities.
- Own Cross-Product Platform Capabilities: Lead design and development of common on-device building blocks such as authentication, clinical data and patient workflows, foreground services, camera and ML integration patterns, local networking, and secure peripheral/device connectivity APIs that product teams can adopt consistently.
- Enable Product Teams: Partner with product engineering teams consuming the platform, gather requirements and feedback, publish clear contracts and guidance, and keep product apps aligned with platform conventions, versioning, and release trains.
- Raise Engineering Quality: Set coding standards, lead design and code reviews, strengthen unit/instrumentation/automated test strategy, and guide CI/CD, static analysis, and release practices appropriate for medical software shared across products.
- Mentor and Multiply the Team: Coach senior and mid-level engineers, unblock technical issues, and establish patterns that improve velocity and long-term maintainability across platform and consuming product software teams.
- Collaborate Cross-Functionally: Work with systems, hardware, clinical, and product partners to translate multi-product needs into robust Android platform designs; represent Android technical trade-offs in planning and design reviews.
- Document and Sustain: Create and maintain architecture, design, and test documentation that supports regulated development, knowledge sharing, and sustaining engineering for shared platform components.
Now Qualifications: from "What you'll bring:" bullet points (though they are not bullet but separated by periods). Let's extract:
- Bachelor’s degree in Computer Science, Computer Engineering, Electrical Engineering, or a related field.
- 10+ years of software development experience, including extensive Android application development.
- Proven experience leading technical architecture and development across complex mobile platforms, shared services, or multi-product ecosystems.
- Expertise in Kotlin and modern Android development, including networking, dependency injection, multithreading/coroutines, APIs, and CI/CD practices.
- Experience building reusable mobile SDKs, libraries, platform services, and scalable application architectures.
- Hands-on experience integrating cameras, connected devices, embedded services, or hybrid mobile/web applications.
- Strong problem-solving, communication, and cross-functional leadership skills with the ability to influence technical direction and drive execution.
- Experience in healthcare, medical devices, or other regulated environments, with knowledge of compliance-focused software development and a focus on delivering reliable, high-quality applications.
Now
for prose. Do NOT repeat job title as heading. Do NOT put Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. We need to preserve all substantive information. Let's parse the posting. First paragraph: "This is where your work makes a difference..." This is about company mission, culture. Could be "About the role"? Actually "About the role" maybe includes description of role and company. The posting includes a paragraph about Baxter mission, then "As a Principal Android Software Engineer, you will lead architecture..." That's role description. So we can put that under About the role (or maybe Responsibilities). The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content. We have: - About the role: Could include company mission and role overview. The first paragraph about Baxter mission and "This is where your work saves lives". Then "As a Principal Android Software Engineer, you will lead architecture and delivery..." That's role overview. So we can put that in About the role. - Responsibilities: The bullet list under "What you'll be doing:" includes many responsibilities. Those are duties. So we can put that under Responsibilities as a list. - Requirements: The bullet list under "What you'll bring:" includes education, experience, etc. That's qualifications/requirements. Could be Requirements. - Qualifications: Might overlap with Requirements. But we can separate: maybe Requirements = experience/education, Qualifications = specific technical expertise? However the instruction says prefer few substantive sections over many thin ones. We could combine Requirements and Qualifications into one section? But headings are predefined; we should only emit heading if we have real specific content for it. We could put all under Requirements and skip Qualifications if content overlaps. But we need to see if there is distinct content for Qualifications separate from Requirements. The "What you'll bring:" includes Bachelor's degree, 10+ years experience, proven experience leading technical architecture, expertise in Kotlin, experience building reusable SDKs, hands-on experience integrating cameras, strong problem-solving, communication, experience in healthcare/medical devices. That's basically qualifications. Could treat as Requirements. Could also treat as Qualifications. But we need to avoid duplicate sections. Perhaps we can put Requirements for education/experience, and Qualifications for technical skills. But the instruction says prefer few substantive sections over many thin ones. So maybe we just have one section for Requirements/Qualifications combined, but we need to pick a heading. Which heading is more appropriate? The posting includes "What you'll bring:" which is typical qualifications. So we could use "Qualifications". But also there is no separate "Requirements" heading content besides that. Could we put everything under "Qualifications"? Then we would not have a Requirements section. That's okay if we don't have content for Requirements. But we need to ensure we don't miss any content. The "What you'll bring:" includes education, experience, expertise, etc. That's qualifications. So we can put that under Qualifications. But we also have "What you'll be doing:" responsibilities. So we have Responsibilities. We also have Benefits section: there is a paragraph about US Benefits. That's substantive. So we need Benefits heading. Pay: there is salary range: "The estimated base salary for this position is $120,000-$165,000 annually." Also mention discretionary bonuses. So we have Pay content. Schedule: there is mention of flexible workplace policy: "Baxter is committed to supporting the needs for flexibility in the workplace. We do so through our flexible workplace policy which includes a required minimum number of days a week onsite." That's schedule info. So we have Schedule content. Thus we have sections: About the role, Responsibilities, Qualifications, Benefits, Pay, Schedule. Possibly also Skills? The posting includes skills embedded in qualifications; but we could treat Skills as part of Qualifications. Since we already have Qualifications, we might not need Skills separate. The instruction says prefer few substantive sections over many thin ones. So we can omit Skills if its content is covered elsewhere. Now we need to format. We must not include boilerplate: EEO, equal opportunity, reasonable accommodations, recruitment fraud notice, etc. Also remove duplicated lines, navigation, cookie, legal, application instructions (like "please speak to the recruiter", "visit our Benefits site", etc). Also remove "Applicants must be authorized to work for any employer in the U.S. We are unable to sponsor or take over sponsorship of an employment visa at this time." That's maybe considered boilerplate? It's a requirement about work authorization. Could be considered a requirement. But it's also a legal statement. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is a legal requirement about work authorization; might be considered boilerplate? It's not EEO but it's a legal requirement. Might be considered part of Requirements? However it's a standard statement; but it's substantive? It says applicants must be authorized to work in US, no sponsorship. That is a requirement. Could keep under Requirements/Qualifications. But the instruction says remove legal boilerplate. This is a legal statement about work authorization; might be considered boilerplate. Safer to remove it. Also remove "For questions about this, our pay philosophy, and available benefits, please speak to the recruiter if you decide to apply and are selected for an interview." That's application instruction; remove. Also remove "For additional information regarding Baxter US Benefits, please speak with your recruiter or visit our Benefits site: Benefits | Baxter" - remove. Also remove "Know Your Rights: Workplace Discrimination is Illegal Reasonable Accommodations ..." - remove. Also remove "Recruitment Fraud Notice ..." - remove. Also remove "We understand compensation is an important factor..." maybe part of Pay? It's about compensation philosophy; could keep as part of Pay? But it's somewhat generic. However we already have salary range; we could keep the sentence about estimated base salary and discretionary bonuses. The rest about pay philosophy maybe boilerplate? It's not strictly boilerplate but could be considered fluff. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The pay philosophy sentences are substantive? They talk about equitable pay, transparency, etc. Might be considered substantive but could be considered boilerplate. I'd keep the salary range and mention of discretionary bonuses; maybe also the sentence about individual pay based on location, skills, etc. That's substantive. The earlier sentence "We understand compensation is an important factor..." is more fluff; could drop. But to be safe, keep the substantive parts: estimated base salary, discretionary bonuses, individual pay based on location, skills, expertise, experience, and other relevant factors. That's enough. Now Benefits: we have a paragraph describing benefits. Need to keep substantive: medical and dental coverage start day one, insurance for basic life, accident, short-term and long-term disability, business travel accident insurance. Financial and retirement benefits: ESPP, 401(k) RSP with employee contributions and company matching. Flexible Spending Accounts, educational assistance programs, time-off benefits: paid holidays, paid time off ranging from 20 to 35 days based on length of service, family and medical leaves of absence, paid parental leave. Additional benefits: commuting benefits, Employee Discount Program, Employee Assistance Program (EAP), childcare benefits. We should keep that. Now Schedule: flexible workplace policy includes required minimum number of days a week onsite. Also mention policy subject to local laws, may adjust, suspend, discontinue. That's schedule info. Now About the role: we need to capture the mission paragraph and role overview. Let's extract: "This is where your work makes a difference. At Baxter, we believe every person—regardless of who they are or where they are from—deserves a chance to live a healthy life. It was our founding belief in 1931 and continues to be our guiding principle. We are redefining healthcare delivery to make a greater impact today, tomorrow, and beyond. Our Baxter colleagues are united by our Mission to Save and Sustain Lives. Together, our community is driven by a culture of courage, trust, and collaboration. Every individual is empowered to take ownership and make a meaningful impact. We strive for efficient and effective operations, and we hold each other accountable for delivering exceptional results. Here, you will find more than just a job—you will find purpose and pride. This is where your work saves lives As a Principal Android Software Engineer, you will lead architecture and delivery of shared Android capabilities that power multiple clinical product applications worldwide. You will own significant portions of the Android system design—reusable services and libraries, hybrid WebView/React UI foundations, device connectivity patterns, and common clinical workflows—while mentoring engineers and raising the bar for quality in a regulated medical-device environment. An ideal candidate brings deep hands-on Android expertise, a clear technical vision for multi-product platform software, and the ability to drive complex cross-team decisions independently. Strong communication and collaboration with product teams, systems, hardware, and other platform partners are essential." We need to ensure we don't repeat the job title as heading; we are not using it as heading. It's okay to appear in paragraph. Now Responsibilities: list from "What you'll be doing:" with bullet points. Let's extract each bullet: - Lead Platform Android Architecture and Delivery: Define and evolve shared Android platform architecture (Kotlin services, DI, WebView/JS bridge patterns, messaging/broker integration, networking foundations) used by multiple product apps, and drive implementation of high-reliability reusable capabilities. - Own Cross-Product Platform Capabilities: Lead design and development of common on-device building blocks such as authentication, clinical data and patient workflows, foreground services, camera and ML integration patterns, local networking, and secure peripheral/device connectivity APIs that product teams can adopt consistently. - Enable Product Teams: Partner with product engineering teams consuming the platform, gather requirements and feedback, publish clear contracts and guidance, and keep product apps aligned with platform conventions, versioning, and release trains. - Raise Engineering Quality: Set coding standards, lead design and code reviews, strengthen unit/instrumentation/automated test strategy, and guide CI/CD, static analysis, and release practices appropriate for medical software shared across products. - Mentor and Multiply the Team: Coach senior and mid-level engineers, unblock technical issues, and establish patterns that improve velocity and long-term maintainability across platform and consuming product software teams. - Collaborate Cross-Functionally: Work with systems, hardware, clinical, and product partners to translate multi-product needs into robust Android platform designs; represent Android technical trade-offs in planning and design reviews. - Document and Sustain: Create and maintain architecture, design, and test documentation that supports regulated development, knowledge sharing, and sustaining engineering for shared platform components. Now Qualifications: from "What you'll bring:" bullet points (though they are not bullet but separated by periods). Let's extract: - Bachelor’s degree in Computer Science, Computer Engineering, Electrical Engineering, or a related field. - 10+ years of software development experience, including extensive Android application development. - Proven experience leading technical architecture and development across complex mobile platforms, shared services, or multi-product ecosystems. - Expertise in Kotlin and modern Android development, including networking, dependency injection, multithreading/coroutines, APIs, and CI/CD practices. - Experience building reusable mobile SDKs, libraries, platform services, and scalable application architectures. - Hands-on experience integrating cameras, connected devices, embedded services, or hybrid mobile/web applications. - Strong problem-solving, communication, and cross-functional leadership skills with the ability to influence technical direction and drive execution. - Experience in healthcare, medical devices, or other regulated environments, with knowledge of compliance-focused software development and a focus on delivering reliable, high-quality applications. Now