Software Developer

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. Must not include Job ID etc. Must remove boilerplate like EEO, legal, etc. Must preserve all substantive info. We need to parse the job description. Key sections: - About the role: The first paragraph(s) describing role: "Are you a Software Developer..." up to "If you are looking for a role where you can grow quickly..." That's about the role. - Responsibilities: The list under "IN THIS ROLE, YOUR RESPONSIBILITIES WILL:" with bullet points (Collaborate, Learn from Domain Experts, Contribute to Specifications, Innovate, Automate, Iterate, Tech Savvy, Always Curious, Team Obsessed). Each bullet has description. - Requirements: Under "WHO YOU ARE:" and "FOR THIS ROLE, YOU WILL NEED:" Actually "WHO YOU ARE:" seems like personal attributes, but could be considered Requirements? The instruction: Use headings for Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where. We have "FOR THIS ROLE, YOU WILL NEED:" which lists required qualifications: Bachelor's degree..., 2+ years..., internship + master's, foundational knowledge of languages, strong problem solving, legal auth. That's requirements. Then "PREFERRED QUALIFICATIONS THAT SET YOU APART:" list: exposure to web/desktop app dev using React with TypeScript/JS, familiarity with Git, basic understanding of APIs, curiosity about AI-assisted tools, any experience with Agile, genuine interest in industrial automation. Those could be Qualifications (preferred) or Skills. We could treat them as Qualifications (preferred) and maybe Skills separate? But we have both Qualifications and Skills headings. Could put required qualifications under Requirements, preferred under Qualifications. Skills could be extracted from responsibilities? But we might not need Skills section if no explicit skill list besides those. However we have "Foundational knowledge of software development in one or more languages such as JavaScript, Python, C#, or C++" that's a skill. Could go under Skills. Better: Use Requirements for mandatory (degree, experience, auth). Use Qualifications for preferred qualifications. Use Skills for technical skills like languages, React, Git, APIs, AI-assisted tools, Agile, industrial automation interest. But we need to avoid duplication. Let's extract: Mandatory requirements: - Bachelor's degree in Engineering, Computer Science, or related STEM discipline - OR 2+ years demonstrated proficiency in software development principles - OR Internship experience in software development principles and a master’s degree in engineering, computer science or related STEM discipline - Foundational knowledge of software development in one or more languages such as JavaScript, Python, C#, or C++ - Strong problem-solving skills and a genuine desire to understand complex systems - Legal authorization to work in the United States without sponsorship now and in the future - Individuals with temporary visas ... are not eligible for hire. (That's part of auth.) Preferred qualifications: - Exposure to web or desktop application development using React with TypeScript and/or JavaScript - Familiarity with version control systems such as Git - Basic understanding of APIs or client-server application architecture - Curiosity about or exposure to AI-assisted development tools, spec-driven workflows, or structured specification formats such as OpenAPI or JSON Schema - Any experience with Agile or structured development processes - Genuine interest in industrial automation, process control, or real-time systems Skills could be overlapping; maybe we put technical skills under Skills: languages (JavaScript, Python, C#, C++), React/TypeScript, Git, APIs, AI-assisted tools, spec-driven (OpenAPI/JSON Schema), Agile, industrial automation. But we already have those in preferred qualifications. To avoid duplication, maybe we put only the mandatory under Requirements, and put preferred under Qualifications, and skip Skills (or combine). However instruction: Prefer a few substantive sections over many thin ones. So we could have About the role, Responsibilities, Requirements, Qualifications. That's four sections. Benefits, Pay, Schedule only if present. Benefits: there is a section "Our Culture & Commitment to You" describing benefits: market-leading 401(k) profit-sharing, medical insurance, dental/vision, family formation benefits, paid parental leave, EAP, tuition reimbursement, employee resource groups, recognition, flexible time off, etc. That's substantive benefits. So we should include Benefits section. Pay: Not mentioned. Schedule: Not mentioned (no mention of work hours). So we omit Pay and Schedule. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits. Now we need to format. Use

for each section heading. Inside each, use

for prose,

• for lists. We must not repeat job title. Not include Job ID etc. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep the exact details but can rephrase? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Means we should not omit details, but we can rephrase? Probably we should keep the substance but can rewrite for HTML. Safer to keep the sentences essentially same. We'll extract the prose for About the role: from start up to "If you are looking for a role where you can grow quickly, contribute meaningfully, and be part of something that has lasting real-world impact, we want to hear from you." Let's copy that paragraph exactly (maybe two paragraphs). The text: "Are you a Software Developer who is eager to launch your career building technology that makes a real-world impact? Emerson has an exciting opportunity for you. We are looking for curious, motivated engineers who are passionate about learning and ready to grow their skills in a collaborative, supportive environment. Based in Austin, Texas, you will join a diverse community and work as a contributing member of a cross-functional Agile team focused on the development of Emerson's PACSystems technologies. PACSystems is trusted by leading companies across discrete and hybrid manufacturing industries to safely and reliably control critical processes. In this role, you will be focused on client-side software that engineers and operators rely on every day, building applications used to configure, program, visualize, and manage PACSystems controllers and automation solutions. Your work will directly contribute to the experience of the engineers and operators who depend on these tools in demanding industrial environments. You will contribute to the design and development of next-generation PACSystems software capabilities. Our team embraces modern development practices, including AI-assisted and spec-driven development methodologies, where structured specifications and intelligent tooling are used to accelerate delivery, improve quality, and reduce ambiguity. We are actively investing in these approaches and want to bring in developers who are excited to learn and grow alongside them. You will be part of an organization led by leaders who are deeply committed to technical excellence, Agile principles, mentorship, and building an environment where engineers do their best work. If you are looking for a role where you can grow quickly, contribute meaningfully, and be part of something that has lasting real-world impact, we want to hear from you." That's the About the role. Now Responsibilities: list each bullet with its description. We need to capture each bullet's heading and description. The bullet headings are capitalized words like Collaborate, Learn from Domain Experts, Contribute to Specifications, Innovate, Automate, Iterate, Tech Savvy, Always Curious, Team Obsessed. Each has a description after dash. We'll produce
  • where each
  • contains maybe heading? Not required but we can keep the heading as plain text. The instruction: Use
    • for any list of duties/requirements/benefits. So we can put the whole bullet as
    • Collaborate - Contribute to a creative team atmosphere, participate in code reviews, and actively engage in Agile activities such as sprint planning and retrospectives. Take part in Hackathons, Tech Talks, and Communities of Practice with like-minded engineers.
    etc. Now Requirements: list the mandatory requirements. We need to capture the list from "FOR THIS ROLE, YOU WILL NEED:" plus maybe the "WHO YOU ARE:"? The "WHO YOU ARE:" seems like personal attributes but could be considered requirements as well. However we have separate Qualifications for preferred. To avoid missing info, we could include both WHO YOU ARE and FOR THIS ROLE under Requirements? But WHO YOU ARE is more about traits: "You stay on top of new technologies and look for ways to apply it. You take time to ask questions and define the problem. You make learning a priority and a goal. You engage in collaborative planning and constantly look to improve your team and deliver results." That's also requirements (behaviors). Could be placed under Requirements as well. But we have Qualifications for preferred qualifications; we could put WHO YOU ARE under Requirements as they are required traits. However the instruction: Use headings for Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid putting personal traits under Requirements. So we can include WHO YOU ARE as part of Requirements list. Thus Requirements list items: - You stay on top of new technologies and look for ways to apply it. - You take time to ask questions and define the problem. - You make learning a priority and a goal. - You engage in collaborative planning and constantly look to improve your team and deliver results. - Bachelor's degree in Engineering, Computer Science, or a related STEM discipline - 2+ years demonstrated proficiency in software development principles - Internship experience in software development principles and a master’s degree in engineering, computer science or related STEM discipline - Foundational knowledge of software development in one or more languages such as JavaScript, Python, C#, or C++ - Strong problem-solving skills and a genuine desire to understand complex systems - Legal authorization to work in the United States without sponsorship now and in the future - Individuals with temporary visas such as E, F-1 (including those with OPT or CPT), H-1, H-2, L-1, B, J or TN, or who need sponsorship for work authorization now or in the future, are not eligible for hire. We need to preserve the "OR" logic? The original says: Bachelor's degree ... OR 2+ years demonstrated proficiency ... OR Internship experience ... and a master’s degree. It's a bit ambiguous. We'll keep as separate bullet points but maybe note "OR". However we should not invent or summarize away detail. The original includes "OR". We could keep as a single bullet: "Bachelor's degree in Engineering, Computer Science, or a related STEM discipline OR 2+ years demonstrated proficiency in software development principles OR Internship experience in software development principles and a master’s degree in engineering, computer science or related STEM discipline". That preserves the OR. Then separate bullets for other items. Thus Requirements bullets: - Bachelor's degree in Engineering, Computer Science, or a related STEM discipline OR 2+ years demonstrated proficiency in software development principles OR Internship experience in software development principles and a master’s degree in engineering, computer science or related STEM discipline - Foundational knowledge of software development in one or more languages such as JavaScript, Python, C#, or C++ - Strong problem-solving skills and a genuine desire to understand complex systems - Legal authorization to work in the United States without sponsorship now and in the future - Individuals with temporary visas such as E, F-1 (including those with OPT or CPT), H-1, H-2, L-1, B, J or TN, or who need sponsorship for work authorization now or in the future, are not eligible for hire. - You stay on top of new technologies and look for ways to apply it. - You take time to ask questions and define the problem. - You make learning a priority and a goal. - You engage in collaborative planning and constantly look to improve your team and deliver results. We could reorder but preserve all. Now Qualifications (preferred): list those. - Exposure to web or desktop application development using React with TypeScript and/or JavaScript