Principal Software Engineer, Electronic Dental Record - athenaCollector

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, no invention. Remove boilerplate like EEO, navigation, etc. Must not include placeholder sections. We need to parse the posting. Key sections: - About the role: The intro paragraph: "Join us as we work to create a thriving ecosystem that delivers accessible, high-quality, and sustainable healthcare for all. Principal Software Engineer, Electronic Dental Record (EDR) Location: Boston, MA (Hybrid) Reports to: Senior Manager, Engineering Join athenahealth as a Principal Software Engineer on our Electronic Dental Records (EDR) platform, where you'll serve as the top technologist driving the design and evolution of enhanced dental workflows. This is an execution cum leadership role. Along with the Architect, you'll set the architectural direction, define the engineering approach, and be accountable to drive the development teams on how the EDR platform is built, modernized, and scaled. We're looking for an engineer with the depth to navigate complex legacy systems, the vision to define what comes next, and the leadership to bring teams along with them." We can treat that as About the role. - Team Summary: Could be part of About the role or separate? The instruction says use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can include About the role covering the intro and team summary. - Responsibilities: There's "Essential Job Responsibilities" list and "Additional Job Responsibilities". Combine into responsibilities. - Expected Education & Experience: That's qualifications/requirements. Could be Requirements and Qualifications. We need to decide: The posting includes "Expected Education & Experience". That's qualifications. Also there is "Expected Compensation". That's Pay. - Skills: The posting mentions specific technologies: Java, Spring Boot, PostgreSQL, AWS services, Kubernetes, Terraform, React strongly preferred, AI coding assistants, etc. Could be Skills. - Benefits: The posting mentions "Along with health and financial benefits, athenistas enjoy perks specific to each location, including commuter support, employee assistance programs, tuition assistance, employee resource groups, and collaborative workspaces — some offices even welcome dogs. We also encourage a better work-life balance...". Also "Total Rewards package - depending on role eligibility, we offer both short and long-term incentives by way of an annual discretionary bonus plan, variable compensation plan, and equity plans." So we have benefits content. - Pay: Expected Compensation $164,000 - $280,000 plus description. - Schedule: Not explicitly mentioned. There's location hybrid but no schedule details. So we should not include Schedule section. We must not include sections with placeholder or vague like "commensurate with experience". Not present. We must not include boilerplate like EEO, navigation, legal, etc. Remove the final lines about equal-opportunity and the link. We must preserve all substantive info; do not invent or summarize away detail. So we need to keep details like bullet points. We need to format using

for section headings,

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

  for prose. We must output only HTML fragment, no /, no markdown fences. Let's craft. First, About the role: combine intro and team summary into prose paragraphs. We'll have:

  About the role

  Join us as we work to create a thriving ecosystem that delivers accessible, high-quality, and sustainable healthcare for all. Join athenahealth as a Principal Software Engineer on our Electronic Dental Records (EDR) platform, where you'll serve as the top technologist driving the design and evolution of enhanced dental workflows. This is an execution cum leadership role. Along with the Architect, you'll set the architectural direction, define the engineering approach, and be accountable to drive the development teams on how the EDR platform is built, modernized, and scaled. We're looking for an engineer with the depth to navigate complex legacy systems, the vision to define what comes next, and the leadership to bring teams along with them.

  The EDR platform powers end-to-end dental practice workflows from clinical documentation and treatment planning to billing and claims. We are actively modernizing the platform, including a significant migration from .NET Azure to Java AWS, while simultaneously building enhanced workflows that raise the bar for dental providers on athenahealth. As Principal Engineer, you will be the technical anchor for this transformation, directing design decisions, establishing engineering standards, and ensuring the platform is built for long-term scalability, reliability, and maintainability.

  That preserves details. Next Responsibilities: combine essential and additional. We'll have

  Responsibilities

  then
  with each responsibility as
  • . Need to keep each bullet as separate
  • . Let's list them. Essential Job Responsibilities list: - Own system-level architecture: Lead end-to-end architectural design across multiple product domains — claims processing, billing workflows, RCM — balancing long-term scalability, operational reliability, and delivery velocity. Your decisions set the standard other engineers build against. - Define the AI-augmented engineering model: Go beyond personal use of AI tooling — establish team-wide patterns, guardrails, and best practices for integrating AI coding assistants, agentic tools, and LLM-assisted workflows into the full SDLC. Define what "responsible AI use" looks like in a healthcare-regulated environment. - Drive spec-first culture at scale: Champion upstream investment in requirements clarity, acceptance criteria, and design reviews. Push product, design, and engineering to operate with enough precision that AI tooling and human review both run faster and with less ambiguity. - Set the bar for AI output quality: Establish team standards for evaluating, debugging, and refining AI-generated code, tests, and designs. Ensure AI output is treated as a prototype — not a deliverable — and that correctness, security, and maintainability are never delegated to the model. - Lead cross-team technical alignment: Serve as the primary technical voice across engineering teams across orgs. Drive resolution on architectural trade-offs, cross-team dependencies, and system-wide design decisions that no individual team can resolve alone. - Prototype and productionize AI-powered capabilities: Lead exploratory work on LLM-assisted features for internal developer productivity and client-facing product capabilities — defining safe, scalable, and regulation-aware patterns for AI application in healthcare. - Evolve engineering practices: Own the evolution of code review norms, testing strategy, design review processes, and delivery practices across the organization. Identify systemic gaps and drive durable improvements. - Grow the engineering organization: Mentor Senior and Staff engineers on architectural thinking, responsible AI use, and domain depth. Elevate the technical ceiling of the teams around you — not just through direct work but through the standards you set and the culture you model. Additional Job Responsibilities: - Provide technical leadership on infrastructure decisions across AWS, Kubernetes, RDS including establishing AI-assisted infrastructure-as-code practices. - Guide the adoption of emerging technologies where they materially improve platform capabilities. - Contribute to the development of best practices and standards for software development. - Define and oversee testing strategy at the system level — including AI-assisted test generation, integration coverage, and performance validation. - Lead root-cause analysis and post-incident reviews for critical production issues; establish patterns that reduce repeat failures. - Evaluate and recommend emerging AI-assisted development tools and practices — with a clear lens on what's production-ready vs. experimental. - Represent engineering perspective in cross-functional planning, capacity discussions, and roadmap prioritization. We'll combine them into one list. Next Requirements/Qualifications: The posting has "Expected Education & Experience". We'll treat that as Requirements (or Qualifications). Since we have both sections possible, we could split: Requirements (education/experience) and Qualifications (specific skills). But the instruction says use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include both Requirements and Qualifications if there is distinct content. We have education/experience bullet list: Bachelor's degree..., 12+ years..., Deep backend expertise..., Proven experience making..., Hands-on..., Proven experience leading..., Experience defining..., Strong track record..., Experience with..., React is strongly preferred..., Familiarity with healthcare domain..., Experience working in and improving Agile delivery environments... We could treat that as Requirements (or Qualifications). Then Skills could be the specific technologies list: Java, Spring Boot, PostgreSQL, AWS services, Kubernetes, Terraform, React, AI coding assistants, etc. But the education/experience already includes many of those. To avoid duplication, we could make Requirements cover education/experience, and Skills cover specific technologies and domain knowledge. Let's extract skills: Java, Spring Boot, PostgreSQL, AWS services, Kubernetes, Terraform, React (strongly preferred), AI coding assistants (Claude Code, Codex, GitHub Copilot, Cursor), experience with LLM-assisted workflows, AI-assisted infrastructure-as-code, AI-assisted test generation, etc. Also healthcare domain concepts (RCM, claims processing, billing). Agile delivery. We'll create Skills section with a list. Now Benefits: we have paragraph about health and financial benefits, perks, total rewards, flexibility, etc. We'll put in

    Benefits

    with
    items. Pay: Expected Compensation $164,000 - $280,000 plus description about base pay depends on factors, total rewards, short/long term incentives, bonus plan, variable compensation, equity plans. We'll put in

    Pay

    with prose. Schedule: Not present, so omit. Now ensure we don't include any boilerplate: remove EEO, navigation, legal, etc. The final lines: "Learn more about our culture and benefits here: athenahealth.com/careers https://www.athenahealth.com/careers/equal-opportunity" should be removed. Also remove "Our vision: ..."? That's part of About Athenahealth section which is boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About Athenahealth" section describing vision, culture, DEI, etc. might be considered boilerplate? It's not strictly legal but could be considered generic company description. However the instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The "About Athenahealth" is substantive about company mission, culture, DEI, benefits. It might be considered relevant. But the sections we have (About the role, Responsibilities, etc.) already cover role specifics. The "About Athenahealth" could be considered part of Benefits or culture. However we already have Benefits section covering perks. The "About Athenahealth" includes vision, culture, DEI commitment, etc. Might be considered part of Benefits or maybe we could include a section "About the company" but not in allowed headings. Since only allowed headings are those listed, we should not add extra headings. We could incorporate relevant parts into Benefits or About the role? The instruction says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. It does not forbid including company description under Benefits or About the role if relevant. But the About the role already focuses on role. The company description could be considered part of Benefits (culture, perks). However the Benefits section we have includes health and financial benefits, perks, flexibility, etc. The company vision and DEI might be less directly a benefit but still part of culture. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The "About Athenahealth" is not exactly those; it's more about company mission and culture. It might be considered substantive. But we have no heading for it; we could incorporate into Benefits as a paragraph about company culture and mission. That seems okay. Thus we will not output a separate "