4572 Software Development Engineer III

We need to output HTML fragment with sections: About the role (already given as heading? The user says do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings. Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need sections for About the role, Responsibilities, Requirements, maybe Preferred Qualifications? The instructions: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. We have content for About the role (the paragraph). We have "A Day in the Life" which could be Responsibilities. We have "Requirements" section. We have "Preferred Qualifications". We have "Benefits". No Pay or Schedule given, so omit those sections. Also we have "About Innovaccer" maybe not needed? It's company description; could be omitted as not a standard heading. The instructions: remove boilerplate, navigation, legal, EEO, scam-warning, duplicated lines, application instructions. Also remove "Innovaccer Inc. is an equal opportunity employer..." etc. Also remove "Disclaimer:" etc. Also remove "About Innovaccer" maybe not needed but could be considered company overview; but not a standard heading; we could omit. The user wants only sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They said use those as examples; we can include others if appropriate? Probably stick to those headings. We have content for About the role, Responsibilities (A Day in the Life), Requirements, Preferred Qualifications (could be Qualifications), Benefits. Skills maybe not separate; we could embed skills within Requirements. But we could also create a Skills section if we have explicit skills list; but we have many skills in Requirements; better to keep Requirements. Qualifications could be Preferred Qualifications. So sections: About the role, Responsibilities, Requirements, Qualifications, Benefits. We need to use

for each section heading. Use

• for any list of duties/requirements/benefits, and

  for prose. We need to preserve all substantive information; do not invent or summarize away detail. So we need to convert the paragraphs into appropriate HTML. We need to avoid filler like "commensurate with experience". Not present. We need to remove boilerplate: EEO, disclaimer, etc. Also remove "Innovaccer Inc. is an equal opportunity employer..." and the E-Verify stuff, disclaimer, etc. Also remove "About Innovaccer" paragraph? It's not boilerplate but maybe not needed; but it's substantive about company. However the instruction says to use sections only for those headings; we could include it as a

  under About the role? But About the role already has description; we could add a separate paragraph about company but not under a heading. The instruction: "Output ONLY the HTML fragment — no /, no markdown code fences." It didn't forbid extra paragraphs outside sections. But better to keep within sections. Could add a

  about company under About the role after the role description? Might be okay. But we need to preserve ALL substantive information; if we omit About Innovaccer, we lose info. However the instruction says "remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." About Innovaccer is not boilerplate; it's company description. Should we keep it? Possibly yes, as it's substantive. But we don't have a heading for it; we could put it as a

  after the About the role section, maybe under same heading? Or we could create a section "About the Company" but not in allowed list. The instruction says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not exclusive; we could add other headings if needed, but they said "include a section ONLY when the posting has real, specific content for it". So we could add a section "About the Company" if we want. However they gave examples; maybe they expect only those headings. Safer to stick to those headings and embed company description within About the role as a paragraph. Thus About the role section will have multiple paragraphs: first paragraph describing role, then maybe a paragraph about company. Now we need to convert lists. Let's extract content. About The Role paragraph: "As an SDE 3 at Innovaccer, you will be a senior full-stack engineer who stays deep in the code, with a focus on Python, RPA, and healthcare workflow automation. You'll design and build high-impact product features end to end — Python backend services, browser-extension automation clients, APIs, workflows, and the UI that makes them usable — while helping raise the engineering bar on your team. This is a builder's role first: you'll write production code daily across backend and extension layers, own complex components from design through delivery, and lead by doing, while mentoring peers and contributing to sound technical decisions. You'll work closely with product, clinical, RCM, and engineering partners to turn healthcare operations problems into reliable software that ships. If you want senior IC scope without leaving the keyboard, this role is for you." A Day in the Life (Responsibilities): list of bullet-like sentences each starting with a verb. We need to turn into

  • . Let's list them: - Design, build, and ship complex full-stack features — Python backend services, APIs, RPA/automation workflows, and browser-extension UI/automation — writing high-quality production code yourself - Build and extend the Chrome extension that drives in-page automation: content scripts, background/service-worker logic, side-panel UI, and DOM tools (click, type, extract, iframe handling) - Own automation and product components end to end: clarify requirements, implement across agent + extension, and ensure bots/workflows perform reliably in production - Analyze business and clinical/RCM processes, translate them into robust automation workflows, and contribute reusable components and frameworks - Integrate extension clients with backend orchestration over HTTP and WebSockets (session/chat, tool execution, worker connectivity) - Contribute to technical design for the systems you build, making practical decisions for scalability, performance, security, and maintainability, then implementing them - Follow and reinforce engineering best practices across the SDLC — code quality, testing, security, observability, and operational excellence — through the code you write and review - Build resilient, well-tested services and interfaces that integrate cleanly across products and with external healthcare systems (e.g., EHRs, claims platforms) - Ensure the software you build complies with healthcare and data-protection requirements, including HIPAA and GDPR, embedding compliance and security into the implementation - Debug, profile, and harden production systems and deployed automations (including flaky selectors, frame issues, and extension/browser edge cases), taking ownership of reliability for the features and workflows you ship - Provide hands-on technical mentorship to engineers through design discussions, pairing, and code review - Partner with product, clinical, and RCM stakeholders to turn real-world needs into well-scoped, technically sound designs you can deliver Now Requirements: list of bullet points. Let's extract each line: - Bachelor's or Master's in Computer Science, Software Engineering, or a related field, or equivalent practical experience - 5-8+ years of software engineering experience with a strong track record of personally building and shipping production systems - Deep, current, hands-on Python expertise for backend services and automation — this role writes Python daily (e.g., FastAPI/Flask/Django or equivalent async Python) - Strong JavaScript/TypeScript and React experience for full-stack delivery, including modern state management (e.g., Redux Toolkit) and component-driven UI - Experience building browser extensions (Chrome MV3 preferred): content scripts, background/service workers, messaging, permissions, and in-page UI injection - Hands-on DOM / browser automation skills: CSS selectors, iframes, event simulation, and debugging automation against real web apps - Strong software design skills across backend services, APIs, WebSockets, and user-facing application layers - Experience building or integrating RPA / workflow automation solutions (custom browser automation, workflow engines, or commercial RPA platforms) - Experience integrating with third-party systems, databases, and distributed services in production environments - Hands-on experience operating production systems: CI/CD, monitoring, performance tuning, and troubleshooting incidents - Familiarity with healthcare data and regulatory compliance (HIPAA, GDPR), or the ability to ramp quickly on a regulated domain - Excellent problem-solving skills and strong communication, with the ability to align engineers and stakeholders around a technical approach - Solid experience with cloud platforms (AWS, GCP, or Azure) and containerization (Docker; Kubernetes familiarity is a plus) Preferred Qualifications: - Experience in healthcare RCM (claims, denials, eligibility, holds, payer workflows) or EHR-adjacent automation - Familiarity with healthcare data standards (e.g., FHIR, HL7) and systems such as athenahealth or similar EHRs - Experience with extension frameworks such as WXT / Vite-based extension builds, Tailwind CSS, and React Router - Experience with AI/ML-assisted automation (document understanding, LLM-powered interpretation within structured workflows) - Experience building event-driven or async Python systems (queues, websockets, background jobs) - Exposure to production bot monitoring/reliability practices and selector resilience - Familiarity with MongoDB, Redis, and pytest (or equivalent) in production Python services Benefits: list: - Generous Paid Time Off: Recharge and relax with 20 days of fixed time off per year, in addition to company holidays—because we believe work-life balance fuels performance - Best-in-Class Parental Leave: Spend quality time with your growing family. We offer one of the industry's most generous parental leave policies to support you during life's most important moments - Recognition & Rewards: We celebrate wins—big and small. Get rewarded with monetary incentives and company-wide recognition for your impact and dedication. Your hard work won't go unnoticed - Comprehensive Insurance Coverage: Stay covered with medical, dental, and vision insurance, plus 100% company-paid short- and long-term disability and basic life insurance. Optional perks include discounted legal aid and pet insurance Now we need to output HTML fragment. Structure:

    About the role

    ... role description ...

    ... maybe company description ...

    Responsibilities

    • ... each responsibility ...

    Requirements

    • ... each requirement ...

    Qualifications

    • ... each preferred qualification ...

    Benefits

    • ... each benefit ...
    We must not include Pay or Schedule sections. We need to ensure we preserve all substantive information; we have included everything from the sections we kept. Did we miss any? The "About Innovaccer" paragraph we omitted; we could embed it as a paragraph under About the role after role description. Let's include that. About Innovaccer paragraph: "Innovaccer activates the flow of healthcare data, empowering providers, payers, and government organizations to deliver intelligent and connected experiences that advance health outcomes. The Healthcare Intelligence Cloud equips every stakeholder in the patient journey to turn fragmented data into proactive, coordinated actions that elevate the quality of care and drive operational performance. Leading healthcare organizations like CommonSpirit Health, Atlantic Health, and Banner Health trust Innovaccer to integrate a system of intelligence into their existing infrastructure, extending the human touch in healthcare. For more information, visit www.innovaccer.com. Check us out on YouTube, Glassdoor, LinkedIn, Instagram, and the Web."