Software Engineer - Full Stack
K Health · New York, NY · 1 mo ago
HybridEngineering$140k/yrFull-time
We need to output HTML fragment with sections: About the role (already present), Responsibilities (what you will do), Requirements (what we are looking for), Benefits (Benefits & Perks), Pay (Compensation). Also maybe Schedule? The posting mentions onsite presence 4 days a week, but that's schedule info. Should we include Schedule section? The rule: include a section ONLY when posting has real, specific content for it. The schedule info: "This role requires onsite presence in our New York City office 4 days a week and does not provide immigration support." That's schedule info. So we can include a Schedule section with that content. Also note we must not repeat job title as heading. Use for each section heading.
We need to remove boilerplate: EEO, scam warning, etc. Also remove "Who We Are:" maybe not needed? It's descriptive but could be part of About the role? The About the role already includes description; "Who We Are:" is separate but could be considered part of About the role? However we already have About the role heading; we could include that paragraph under About the role. But we must preserve all substantive information. The "Who Are:" paragraph is substantive about company. Could be placed under About the role as additional prose. However the instruction: "Use
for each section heading.
We need to remove boilerplate: EEO, scam warning, etc. Also remove "Who We Are:" maybe not needed? It's descriptive but could be part of About the role? The About the role already includes description; "Who We Are:" is separate but could be considered part of About the role? However we already have About the role heading; we could include that paragraph under About the role. But we must preserve all substantive information. The "Who Are:" paragraph is substantive about company. Could be placed under About the role as additional prose. However the instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can have About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. Possibly also Qualifications? The posting includes "What we are looking for" which includes qualifications. We'll treat that as Requirements. Could also have Skills but not needed.
We need to use - for any list of duties/requirements/benefits. So for Responsibilities list items, Requirements list items, Benefits list items.
We need to preserve all substantive info, not invent or summarize away detail. So we need to capture each bullet.
Let's extract sections.
About the role: The first paragraph(s) before "What you will do". The text:
"About the RoleAs a Software Engineer at K Health, you are the champion of technical excellence for a high-stakes portfolio of clinical AI and a suite of products that serve the patients and the physicians. We don't just build apps; we build, and operate modern, AI-powered, 24/7 virtual clinics for the nation’s largest health systems.In this role, your mission is to help build a product ecosystem where reliability, privacy, and performance are non-negotiable. You will develop reusable components and resilient architectures that exude trust, ensuring that every patient interaction is seamless and every clinical data point is secure. You will be a "multiplier," creating the foundational frameworks that allow us to deploy 5-star experiences across a portfolio of partners without sacrificing the quality our users depend on.This role requires onsite presence in our New York City office 4 days a week and does not provide immigration support."
We need to separate schedule line maybe for Schedule section. But the schedule line is part of About the role paragraph. We could keep it in About the role, but also we have a Schedule section. The rule: include a section ONLY when posting has real, specific content for it. The schedule content exists; we could put it in Schedule section. However we must not duplicate content. If we move schedule line to Schedule section, we should remove it from About the role to avoid duplication. But we need to preserve all substantive information; we can move it. The About the role section can still have the rest.
Thus About the role content: everything except the schedule line.
Let's extract About the role without schedule:
"As a Software Engineer at K Health, you are the champion of technical excellence for a high-stakes portfolio of clinical AI and a suite of products that serve the patients and the physicians. We don't just build apps; we build, and operate modern, AI-powered, 24/7 virtual clinics for the nation’s largest health systems.In this role, your mission is to help build a product ecosystem where reliability, privacy, and performance are non-negotiable. You will develop reusable components and resilient architectures that exude trust, ensuring that every patient interaction is seamless and every clinical data point is secure. You will be a "multiplier," creating the foundational frameworks that allow us to deploy 5-star experiences across a portfolio of partners without sacrificing the quality our users depend on."
Now Responsibilities: "What you will do" bullet list:
- Full-Stack: Support the end-to-end lifecycle of products and features, from multi-platform clients, to the Kotlin/JVM-based backend services that power them.
- Quality as a Feature: Enforce standards for high-stakes engineering—ensuring that performance, accessibility, and data privacy are baked into every feature
- Platform Innovation: Proactively modernize our systems to leverage agentic AI tools that improve developer productivity and team efficiency.
- Technical Stewardship: Act as a stabilizing force in complex technical situations, bringing clarity to ambiguous requirements and making informed decisions that mitigate risk.
- Mentor & Multiply: Level up the engineering organization by fostering an ownership mindset and modeling how to move fast while maintaining clinical-grade quality.
We need to preserve the colon headings maybe as part of list item text.
Now Requirements: "What we are looking for" includes many bullet-like sentences. Let's parse:
"Established Expertise: 3-5+ years of professional software engineering experience, with a deep focus on building robust, customer-facing products from front-to-back.
Full Stack Fluency: Strong professional experience in front-to-back-end development using Node/Typescript with a JVM language (Kotlin or Java) as a major plus.
Middle Layer Proficiency: You understand how to build resilient APIs that support critical workflows on any user-facing platform. We leverage GraphQL and Typescript heavily in the middle layers.
Tasteful User Experience: You develop with the customer in mind, and prioritize their experience across the functional and non-functional considerations that shape the overall experience across Web and for Mobile platforms.
AI-First Mindset: Proficiency with modern agentic development tools (i.e., Claude Code), using them effectively across platforms to deliver high-quality code quickly and reliably.
Repeatable Patterns Mentality: Experience building reusable frameworks, white-label solutions, or multi-tenant architectures where code quality directly impacts multiple products.
Mission-Driven Reliability: A background in high-stakes industries (e.g., HealthTech, ConsumerTech, or Conversational AI) where performance and privacy are paramount.
Autonomy & Judgment: Proven ability to work with high levels of autonomy, using your expertise to "do the right thing" for the patient and the partner.
Education: A Bachelor’s or Master’s degree in Computer Science or a related technical field."
Also Bonus section: "BonusKMP: Experience with Kotlin Multiplatform to drive logic sharing across the portfolio.Security Expertise: Deep knowledge of security best practices and data encryption.Clinical Integration: Experience with healthcare standards (FHIR, HL7) or integrating with EHR systems."
We could treat Bonus as part of Requirements or separate Skills. But we only need sections when there is real content. Could include Requirements covering all these, and maybe Skills for Bonus? But we can just include all under Requirements (including Bonus). The rule: Use
- for any list of duties/requirements/benefits. So we can make a list for Requirements.
Now Benefits: "Benefits & Perks: Hybrid work schedule with weekly lunches and stocked fridges Monthly social committees for company events18 vacation days, 9 company holidays, 5 sick days, and 2 personal days Stock options for every full-time employee Paid parental leave401k benefitCommuter Benefits Competitive health, dental, and vision insurance options"
We need to split into list items. The text seems concatenated without spaces. Let's parse:
- Hybrid work schedule with weekly lunches and stocked fridges
- Monthly social committees for company events
- 18 vacation days, 9 company holidays, 5 sick days, and 2 personal days
- Stock options for every full-time employee
- Paid parental leave
- 401k benefit
- Commuter Benefits
- Competitive health, dental, and vision insurance options
We need to ensure spacing.
Now Pay: "Compensation:: $140,000 USD - $165,000 USD". Note double colon. We'll output as "$140,000 USD - $165,000 USD".
Now Schedule: "This role requires onsite presence in our New York City office 4 days a week and does not provide immigration support."
We'll put that as a
under Schedule heading.
Now we need to output only HTML fragment, no /. Use
headings,
for prose,
- for lists.
We must not include boilerplate like EEO, scam warning, etc. Also remove "Who We Are:" section. Also remove "We offer competitive compensation packages based on industry benchmarks..." etc. That's boilerplate? It's somewhat generic but maybe considered boilerplate. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "We offer competitive compensation packages..." is generic but not necessarily boilerplate; but it's repetitive of compensation info already given. Might be considered duplicated lines? It's not duplicate but could be considered filler. Safer to remove it. Also remove "We are proud to be an Equal Opportunity Employer..." etc. Also remove "We depend on our differences..." etc. Also remove "We are committed to maintaining the integrity of our hiring process..." etc. Also remove "All communication for job offers..." etc. Also remove "Be cautious of job offers from sources..." etc.
Thus final HTML:
About the role
As a Software Engineer at K Health, you are the champion of technical excellence for a high-stakes portfolio of clinical AI and a suite of products that serve the patients and the physicians. We don't just build apps; we build, and operate modern, AI-powered, 24/7 virtual clinics for the nation’s largest health systems.In this role, your mission is to help build a product ecosystem where reliability, privacy, and performance are non-negotiable. You will develop reusable components and resilient architectures that exude trust, ensuring that every patient interaction is seamless and every clinical data point is secure. You will be a "multiplier," creating the foundational frameworks that allow us to deploy 5-star experiences across a portfolio of partners without sacrificing the quality our users depend on.
Responsibilities
- Full-Stack: Support the end-to-end lifecycle of products and features, from multi-platform clients, to the Kotlin/JVM-based backend services that power them.
- Quality as a Feature: Enforce standards for high-stakes engineering—ensuring that performance, accessibility, and data privacy are baked into every feature
- Platform Innovation: Proactively modernize our systems to leverage agentic AI tools that improve developer productivity and team efficiency.
- Technical Stewardship: Act as a stabilizing force in complex technical situations, bringing clarity to ambiguous requirements and making informed decisions that mitigate risk.
- Mentor & Multiply: Level up the engineering organization by fostering an ownership mindset and modeling how to move fast while maintaining clinical-grade quality.
Requirements
- Established Expertise: 3-5+ years of professional software engineering experience, with a deep focus on building robust, customer-facing products from front-to-back.
- Full Stack Fluency: Strong professional experience in front-to-back-end development using Node/Typescript with a JVM language (Kotlin or Java) as a major plus.
- Middle Layer Proficiency: You understand how to build resilient APIs that support critical workflows on any user-facing platform. We leverage GraphQL and Typescript heavily in the middle layers.
- Tasteful User Experience: You develop with the customer in mind, and prioritize their experience across
- for any list of duties/requirements/benefits. So for Responsibilities list items, Requirements list items, Benefits list items.
We need to preserve all substantive info, not invent or summarize away detail. So we need to capture each bullet.
Let's extract sections.
About the role: The first paragraph(s) before "What you will do". The text:
"About the RoleAs a Software Engineer at K Health, you are the champion of technical excellence for a high-stakes portfolio of clinical AI and a suite of products that serve the patients and the physicians. We don't just build apps; we build, and operate modern, AI-powered, 24/7 virtual clinics for the nation’s largest health systems.In this role, your mission is to help build a product ecosystem where reliability, privacy, and performance are non-negotiable. You will develop reusable components and resilient architectures that exude trust, ensuring that every patient interaction is seamless and every clinical data point is secure. You will be a "multiplier," creating the foundational frameworks that allow us to deploy 5-star experiences across a portfolio of partners without sacrificing the quality our users depend on.This role requires onsite presence in our New York City office 4 days a week and does not provide immigration support."
We need to separate schedule line maybe for Schedule section. But the schedule line is part of About the role paragraph. We could keep it in About the role, but also we have a Schedule section. The rule: include a section ONLY when posting has real, specific content for it. The schedule content exists; we could put it in Schedule section. However we must not duplicate content. If we move schedule line to Schedule section, we should remove it from About the role to avoid duplication. But we need to preserve all substantive information; we can move it. The About the role section can still have the rest.
Thus About the role content: everything except the schedule line.
Let's extract About the role without schedule:
"As a Software Engineer at K Health, you are the champion of technical excellence for a high-stakes portfolio of clinical AI and a suite of products that serve the patients and the physicians. We don't just build apps; we build, and operate modern, AI-powered, 24/7 virtual clinics for the nation’s largest health systems.In this role, your mission is to help build a product ecosystem where reliability, privacy, and performance are non-negotiable. You will develop reusable components and resilient architectures that exude trust, ensuring that every patient interaction is seamless and every clinical data point is secure. You will be a "multiplier," creating the foundational frameworks that allow us to deploy 5-star experiences across a portfolio of partners without sacrificing the quality our users depend on."
Now Responsibilities: "What you will do" bullet list:
- Full-Stack: Support the end-to-end lifecycle of products and features, from multi-platform clients, to the Kotlin/JVM-based backend services that power them.
- Quality as a Feature: Enforce standards for high-stakes engineering—ensuring that performance, accessibility, and data privacy are baked into every feature
- Platform Innovation: Proactively modernize our systems to leverage agentic AI tools that improve developer productivity and team efficiency.
- Technical Stewardship: Act as a stabilizing force in complex technical situations, bringing clarity to ambiguous requirements and making informed decisions that mitigate risk.
- Mentor & Multiply: Level up the engineering organization by fostering an ownership mindset and modeling how to move fast while maintaining clinical-grade quality.
We need to preserve the colon headings maybe as part of list item text.
Now Requirements: "What we are looking for" includes many bullet-like sentences. Let's parse:
"Established Expertise: 3-5+ years of professional software engineering experience, with a deep focus on building robust, customer-facing products from front-to-back.
Full Stack Fluency: Strong professional experience in front-to-back-end development using Node/Typescript with a JVM language (Kotlin or Java) as a major plus.
Middle Layer Proficiency: You understand how to build resilient APIs that support critical workflows on any user-facing platform. We leverage GraphQL and Typescript heavily in the middle layers.
Tasteful User Experience: You develop with the customer in mind, and prioritize their experience across the functional and non-functional considerations that shape the overall experience across Web and for Mobile platforms.
AI-First Mindset: Proficiency with modern agentic development tools (i.e., Claude Code), using them effectively across platforms to deliver high-quality code quickly and reliably.
Repeatable Patterns Mentality: Experience building reusable frameworks, white-label solutions, or multi-tenant architectures where code quality directly impacts multiple products.
Mission-Driven Reliability: A background in high-stakes industries (e.g., HealthTech, ConsumerTech, or Conversational AI) where performance and privacy are paramount.
Autonomy & Judgment: Proven ability to work with high levels of autonomy, using your expertise to "do the right thing" for the patient and the partner.
Education: A Bachelor’s or Master’s degree in Computer Science or a related technical field."
Also Bonus section: "BonusKMP: Experience with Kotlin Multiplatform to drive logic sharing across the portfolio.Security Expertise: Deep knowledge of security best practices and data encryption.Clinical Integration: Experience with healthcare standards (FHIR, HL7) or integrating with EHR systems."
We could treat Bonus as part of Requirements or separate Skills. But we only need sections when there is real content. Could include Requirements covering all these, and maybe Skills for Bonus? But we can just include all under Requirements (including Bonus). The rule: Use
- for any list of duties/requirements/benefits. So we can make a list for Requirements.
Now Benefits: "Benefits & Perks: Hybrid work schedule with weekly lunches and stocked fridges Monthly social committees for company events18 vacation days, 9 company holidays, 5 sick days, and 2 personal days Stock options for every full-time employee Paid parental leave401k benefitCommuter Benefits Competitive health, dental, and vision insurance options"
We need to split into list items. The text seems concatenated without spaces. Let's parse:
- Hybrid work schedule with weekly lunches and stocked fridges
- Monthly social committees for company events
- 18 vacation days, 9 company holidays, 5 sick days, and 2 personal days
- Stock options for every full-time employee
- Paid parental leave
- 401k benefit
- Commuter Benefits
- Competitive health, dental, and vision insurance options
We need to ensure spacing.
Now Pay: "Compensation:: $140,000 USD - $165,000 USD". Note double colon. We'll output as "$140,000 USD - $165,000 USD".
Now Schedule: "This role requires onsite presence in our New York City office 4 days a week and does not provide immigration support."
We'll put that as a
under Schedule heading. Now we need to output only HTML fragment, no /. Use
headings,
for prose,
- for lists.
We must not include boilerplate like EEO, scam warning, etc. Also remove "Who We Are:" section. Also remove "We offer competitive compensation packages based on industry benchmarks..." etc. That's boilerplate? It's somewhat generic but maybe considered boilerplate. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "We offer competitive compensation packages..." is generic but not necessarily boilerplate; but it's repetitive of compensation info already given. Might be considered duplicated lines? It's not duplicate but could be considered filler. Safer to remove it. Also remove "We are proud to be an Equal Opportunity Employer..." etc. Also remove "We depend on our differences..." etc. Also remove "We are committed to maintaining the integrity of our hiring process..." etc. Also remove "All communication for job offers..." etc. Also remove "Be cautious of job offers from sources..." etc.
Thus final HTML:
About the role
As a Software Engineer at K Health, you are the champion of technical excellence for a high-stakes portfolio of clinical AI and a suite of products that serve the patients and the physicians. We don't just build apps; we build, and operate modern, AI-powered, 24/7 virtual clinics for the nation’s largest health systems.In this role, your mission is to help build a product ecosystem where reliability, privacy, and performance are non-negotiable. You will develop reusable components and resilient architectures that exude trust, ensuring that every patient interaction is seamless and every clinical data point is secure. You will be a "multiplier," creating the foundational frameworks that allow us to deploy 5-star experiences across a portfolio of partners without sacrificing the quality our users depend on.
Responsibilities
- Full-Stack: Support the end-to-end lifecycle of products and features, from multi-platform clients, to the Kotlin/JVM-based backend services that power them.
- Quality as a Feature: Enforce standards for high-stakes engineering—ensuring that performance, accessibility, and data privacy are baked into every feature
- Platform Innovation: Proactively modernize our systems to leverage agentic AI tools that improve developer productivity and team efficiency.
- Technical Stewardship: Act as a stabilizing force in complex technical situations, bringing clarity to ambiguous requirements and making informed decisions that mitigate risk.
- Mentor & Multiply: Level up the engineering organization by fostering an ownership mindset and modeling how to move fast while maintaining clinical-grade quality.
Requirements
- Established Expertise: 3-5+ years of professional software engineering experience, with a deep focus on building robust, customer-facing products from front-to-back.
- Full Stack Fluency: Strong professional experience in front-to-back-end development using Node/Typescript with a JVM language (Kotlin or Java) as a major plus.
- Middle Layer Proficiency: You understand how to build resilient APIs that support critical workflows on any user-facing platform. We leverage GraphQL and Typescript heavily in the middle layers.
- Tasteful User Experience: You develop with the customer in mind, and prioritize their experience across
- for lists.
We must not include boilerplate like EEO, scam warning, etc. Also remove "Who We Are:" section. Also remove "We offer competitive compensation packages based on industry benchmarks..." etc. That's boilerplate? It's somewhat generic but maybe considered boilerplate. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "We offer competitive compensation packages..." is generic but not necessarily boilerplate; but it's repetitive of compensation info already given. Might be considered duplicated lines? It's not duplicate but could be considered filler. Safer to remove it. Also remove "We are proud to be an Equal Opportunity Employer..." etc. Also remove "We depend on our differences..." etc. Also remove "We are committed to maintaining the integrity of our hiring process..." etc. Also remove "All communication for job offers..." etc. Also remove "Be cautious of job offers from sources..." etc.
Thus final HTML:
- for any list of duties/requirements/benefits. So we can make a list for Requirements.
Now Benefits: "Benefits & Perks: Hybrid work schedule with weekly lunches and stocked fridges Monthly social committees for company events18 vacation days, 9 company holidays, 5 sick days, and 2 personal days Stock options for every full-time employee Paid parental leave401k benefitCommuter Benefits Competitive health, dental, and vision insurance options"
We need to split into list items. The text seems concatenated without spaces. Let's parse:
- Hybrid work schedule with weekly lunches and stocked fridges
- Monthly social committees for company events
- 18 vacation days, 9 company holidays, 5 sick days, and 2 personal days
- Stock options for every full-time employee
- Paid parental leave
- 401k benefit
- Commuter Benefits
- Competitive health, dental, and vision insurance options
We need to ensure spacing.
Now Pay: "Compensation:: $140,000 USD - $165,000 USD". Note double colon. We'll output as "$140,000 USD - $165,000 USD".
Now Schedule: "This role requires onsite presence in our New York City office 4 days a week and does not provide immigration support."
We'll put that as a