Software Engineer L4 (Remote)

We need to produce HTML fragment with sections: About the role? The posting includes Overview, Responsibilities Summary, Responsibilities, Qualifications (Required Skills, Preferred Skills), Physical Role Requirements, Minimum Education..., Minimum Experience, Pay info, Benefits. Also maybe Overview as About the role. We must not repeat job title as heading. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we need to decide which sections actually have content. We have Overview (could be About the role). Responsibilities Summary and Responsibilities (maybe combine). Qualifications includes Required Skills and Preferred Skills. Also Physical Role Requirements maybe part of Requirements? Could be separate Requirements section. Minimum Education, Licensure, Professional Certification, Minimum Experience could be under Qualifications or Requirements. Pay info: we have salary range. Benefits: described. Schedule: not mentioned (no schedule specifics). So we should not create Schedule section. We must not create sections with filler like "not specified". So include only sections with real content. We need to use

• for any list of duties/requirements/benefits. Use

  for prose. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO etc. Also remove duplicated lines, application instructions. Also remove "Need help finding the right job? We can recommend jobs specifically for you!Software Powered by ICIMS..." etc. We need to output only HTML fragment. Let's extract content: Overview paragraph: "Frontdoor is reimagining how homeowners maintain and repair their most valuable asset – their home. As the parent company of two leading brands, we bring over 50 years of experience in providing our members with comprehensive options to protect their homes from costly and unexpected breakdowns through our extensive network of pre-qualified professional contractors. American Home Shield, the category leader in home service plans with approximately two million members, gives homeowners budget protection and convenience, covering up to 23 essential home systems and appliances. Frontdoor is a cutting edge, one-stop app for home repair and maintenance. Enabled by our Streem technology, the app empowers homeowners by connecting them in real time through video chat with pre-qualified experts to diagnose and solve their problems. The Frontdoor app also offers homeowners a range of other benefits including DIY tips, discounts and more. For more information about American Home Shield and Frontdoor, please visit frontdoorhome.com ." We can keep that as About the role. Responsibilities Summary: "Our Software Engineers are product focused, giving them the opportunity to work on a product and understand the layers of the software stack. Work includes documentation, automated testing, debugging, working with algorithms and data structures, coding, design, system performance scaling, and problem solving for routine and moderately complex software programs. Responsibilities also include participation in projects." Then Responsibilities list bullet points: many items. We need to combine maybe into a single Responsibilities section with

  • each duty. Let's list each bullet: - Write documentation and automated tests for code to be written. - Implement functionality for automated tests that will successfully pass and meet coding standards. - Debug production issues and create subsequent mitigation plans. - Optimize performance of existing implementations. - Debug issues, recognize the causes of issues, and tackle reproducible issues using query language and scripting. - Select optimal data structures using fundamental software algorithms and concepts of space and time complexity. - Fix easily reproducible bugs, build new and straightforward features, write unit tests for code coverage, and spot bottlenecks through the ability to read and understand others’ code. - Implement code based on common design patterns. - Determine correct algorithms based on input size and frequency using basic concepts of algorithms and Big-O Notation. - Prioritize tasks with Scrummaster that leads the team to be successful. - Bring forward ideas to experiment and work in teams to transform ideas to reality. - May include other duties as assigned. We should keep them as list items. Qualifications: Required Skills list: - Basic understanding of computer science fundamentals, such as data structures, (trees, graphs, hash tables); - Basic understanding of functioning and implementation of basic algorithms, such as sorts, searching, and the capability to explain performance characteristics using Big-O Notations - Capability to debug basic problems and analyze logs in production systems and to read basic existing code - Understanding of various data storage options, such as relational, no-SQL, etc. - Basic scripting skill in Shell, Python, or Ruby - Basic skills in languages, such as C, C++, Java, Golang, .net Core - Knowledge of Requirement Management, Agile Development, Test Process, Code Management, and Deployment - Ability to be on call on a rotating basis for the services owned by the team Preferred Skills list: - Experience in developing products in an Agile development environment - Experience working in a CI/CD environment - Understanding of Git and development activities such as merge and conflict resolution of code - Understanding and experience in Docker, Kubernets, and AWS cloud services Physical Role Requirements: list: - Be seated at a computer intermittently for up to eight hours a day. - Move up to 10 pounds occasionally, by lifting, carrying, pushing, pulling, or otherwise repositioning objects. - Sitting for long periods of time while using office equipment such as computers and phones. - Repetitive motions using hands and digits, such as movement of wrists, hands and fingers while picking, pinching, and typing during your normal working environment. Minimum Education, Licensure and Professional Certification requirements: "Bachelor’s degree in Computer Science, Electrical Engineering, or related field required, Master’s degree preferred" Minimum Experience required: "5+ years of product development experience required" Pay: "This role pays between $103k to $120k, and your actual base pay will depend on your skills, qualifications, responsibilities, experience, and location. At Frontdoor certain roles are eligible for additional rewards and incentives. Speak directly to your recruiter to learn more." Benefits: "Our approach to benefits is holistic, and includes health, wellbeing and financial components including: insurance for medical/pharmacy, dental, vision, life, and disability, weight loss and smoking cessation programs, matching 401(k) and ability to participate in our employee stock purchase plan." We also have location info: "Job Locations US ID 2026-4181" maybe not needed. Also Category Engineering Type Full Time Company AHS American Home Shield Corp. Might be considered metadata; we could fold into a short

    or drop. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it. So we could include a short paragraph with location, job type, company. But maybe better to drop as not substantive? It's somewhat metadata but could be included as a short p. However we need to preserve ALL substantive information; location, job type, company might be considered substantive. We'll include a short paragraph after overview maybe. We must not create sections with filler. So we will have sections: About the role (overview), Responsibilities, Qualifications (maybe split into Required Skills and Preferred Skills? But we can have Qualifications section with sub-sections? The instruction: use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests we could have Qualifications and Skills separate. But we have both Required Skills and Preferred Skills; maybe we can put them under Qualifications. Or we could have Skills section for Required Skills and Preferred Skills. However we also have Minimum Education etc. Could be under Qualifications. Physical Role Requirements could be under Requirements. But we don't have a separate Requirements heading in the list; we have Requirements as possible heading. We could use Requirements for Physical Role Requirements and maybe Minimum Education/Experience. But we also have Qualifications. Let's decide: We'll create sections: - About the role (h3) - Responsibilities (h3) - Qualifications (h3) containing Required Skills, Preferred Skills, Minimum Education, Minimum Experience (maybe as sublists or paragraphs) - Physical Role Requirements (h3) maybe under Requirements? But we have a heading "Requirements" in the list; we could use Requirements for Physical Role Requirements and maybe Minimum Education/Experience. However Qualifications already covers education/experience. To avoid duplication, we could use Requirements for Physical Role Requirements only. But we also have "Requirements" as a possible heading; we can use it for Physical Role Requirements. Then we keep Qualifications for skills/education/experience. - Benefits (h3) - Pay (h3) We must not create Schedule section. Now we need to format lists. For Qualifications, we could have subheadings? Not allowed; only h3 for section headings. Inside we can use

    and

    • . So we can list Required Skills as a
      • , then Preferred Skills as another
        • , then Minimum Education as

          , Minimum Experience as

          . Similarly for Responsibilities we have a

          • list. Physical Role Requirements:
            • . Benefits: maybe a
              • list of benefits items. Pay:

                with salary range and note. Now ensure we preserve all substantive information. Let's extract each piece exactly. Overview paragraph: we need to keep it as is, maybe trim trailing spaces. Responsibilities Summary paragraph: we could include as a

                before the list? The instruction: Use

                for prose. So we can have a

                for the summary, then

                • for the list. Responsibilities list: we need to keep each bullet exactly as given, preserving punctuation. Let's copy them: - Write documentation and automated tests for code to be written. - Implement functionality for automated tests that will successfully pass and meet coding standards. - Debug production issues and create subsequent mitigation plans. - Optimize performance of existing implementations. - Debug issues, recognize the causes of issues, and tackle reproducible issues using query language and scripting. - Select optimal data structures using fundamental software algorithms and concepts of space and time complexity. - Fix easily reproducible bugs, build new and straightforward features, write unit tests for code coverage, and spot bottlenecks through the ability to read and understand others’ code. - Implement code based on common design patterns. - Determine correct algorithms based on input size and frequency using basic concepts of algorithms and Big-O Notation. - Prioritize tasks with Scrummaster that leadsthe team to be successful. (Note there's a missing space: "leadsthe". We must preserve as is.) - Bring forward ideas to experiment and work in teams to transform ideas to reality. - May include other duties as assigned. Check for any typos: "leadsthe" exactly as in source. We'll keep. Now Required Skills list: need to preserve punctuation and line breaks. Let's copy each: - Basic understanding of computer science fundamentals, such as data structures, (trees, graphs, hash tables); - Basic understanding of functioning and implementation of basic algorithms, such as sorts, searching, and the capability to explain performance characteristics using Big-O Notations - Capability to debug basic problems and analyze logs in production systems and to read basic existing code - Understanding of various data storage options, such as relational, no-SQL, etc. - Basic scripting skill in Shell, Python, or Ruby - Basic skills in languages, such as C, C++, Java, Golang, .net Core - Knowledge of Requirement Management, Agile Development, Test Process, Code Management, and Deployment - Ability to be on call on a rotating basis for the services owned by the team Note some have trailing semicolons, etc. Keep as is. Preferred Skills list: - Experience in developing products in an Agile development environment - Experience working in a CI/CD environment - Understanding of Git and development activities such as merge and conflict resolution of code - Understanding and experience in Docker, Kubernets, and AWS cloud services Physical Role Requirements list: - Be seated at a computer intermittently for up to eight hours a day. - Move up to 10 pounds occasionally, by lifting, carrying, pushing, pulling