Engineer, Software

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, disclaimer, etc. Must preserve all substantive info. We need to parse the posting and extract content for each section. Let's identify sections: - About the role: The introductory paragraph(s) describing IPC, mission, environment, etc. Could be considered "About the role". The posting starts: "At Independent Purchasing Cooperative (IPC), we are more than just a supply chain services provider—we're the strategic sourcing partner behind one of the world’s most recognized brands: Subway®. As a member-owned organization, we are driven by our commitment to serve the franchisees who own and operate Subway® restaurants across North America, Canada, Puerto Rico, and the U.S. Virgin Islands. Headquartered in Miami, FL, we were founded in 1996 with a mission to help franchisees be more profitable and competitive by delivering exceptional value through supply chain solutions, contract negotiation, technology initiatives, and industry expertise. At IPC, you'll find a supportive and inclusive environment that fosters personal growth, professional development, and a healthy work-life balance. Whether you're a seasoned supply chain professional or just beginning your career journey, IPC offers opportunities to make a meaningful impact! IPC is seeking a highly motivated Software Engineer with expertise in the .NET and integration platforms as well with the Microsoft Development stack. The main goal of Software Engineer is to design, implement and maintain solutions to support the always changing environment our organization is immersed into, ensuring that the best practices from the Software Development Cycle principles are met." That's about the role and company. So we can put that in

About the role

with

containing that text (maybe split into paragraphs). We'll keep it as one paragraph or multiple. - Responsibilities: The "Essential Duties and Responsibilities" section lists many bullet-like paragraphs. We need to convert each duty into

• . The list includes: Designing and Developing Software Solutions - Architect and develop software solutions using .NET, C#, and integration with Dynamics 365. - Ensure that solutions are scalable, secure, and aligned with business requirements and best coding practices. Maintaining and Enhancing Application Platforms - Maintain cloud-based platforms and environments of supported applications. - Perform updates and data transformation into Dynamics 365 to support ongoing business needs. Collaborating with the Business Applications Team - Work closely with team members to understand requirements and deliver high-quality software solutions. - Participate in code and architectural reviews to ensure best practices and standards are upheld. Implementing DevOps and CI/CD Practices - Apply DevOps principles to automate and streamline deployment processes using Azure DevOps. - Create and maintain automated tests to ensure code quality and reliability. Supporting Integration and API Development - Develop and maintain integration solutions and APIs that connect Dynamics 365 with other systems. - Drive the API/Platform strategy in a fast-paced, innovative-focused environment. Ensuring Security and Compliance - Implement cloud security controls and ensure that applications adhere to industry standards and regulations. - Collaborate with security teams to address vulnerabilities and ensure the security of application platforms. Continuous Learning and Improvement - Embrace new technologies and stay updated on industry trends to continuously improve software solutions. - Participate in ongoing feedback sessions, knowledge sharing, and retrospectives to improve processes. Providing Technical Documentation - Create and maintain documentation for developers and business users to ensure clarity and ease of use. - Provide post-incident reviews and analysis to improve system resilience and prevent future issues. - Be willing to learn innovative technologies and proactively adapt to technological evolution. We need to decide how to structure: Could have a
  with each duty as
  • containing the description. Could also group under subheadings but not required. Simpler: each bullet as
  • . We'll include all. - Requirements: The posting includes "Knowledge, Skills, and Abilities" and "Qualifications and Experience". Might split: Requirements could be the "Knowledge, Skills, and Abilities" list. Qualifications could be the "Qualifications and Experience" list. Skills could be maybe overlapping. But we need to follow instruction: Use headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only those with real specific content. We have content for Requirements (Knowledge, Skills, and Abilities). We have Qualifications (Qualifications and Experience). We have Skills maybe overlapping but we could treat "Skills" as the technical skills list (like .NET, C#, Azure, etc.) but that is also in Qualifications. However we can still create a Skills section if there is distinct content. The posting includes "Competencies" list (Action Oriented, Customer Focus, etc.) which could be considered Skills (behavioral). Also there is "Knowledge, Skills, and Abilities" which includes both knowledge and abilities. The "Competencies" list could be considered Skills. We'll decide to put the "Competencies" under Skills section. The "Knowledge, Skills, and Abilities" could be Requirements. The "Qualifications and Experience" could be Qualifications. We must avoid filler like "commensurate with experience". Not present. Benefits: The posting mentions supportive environment, work-life balance, but not explicit benefits like health insurance, 401k, etc. There's no explicit benefits section. So we should NOT create Benefits section. Pay: No salary info. So omit. Schedule: The posting includes "This is a full-time position. Standard office hours are from Monday through Friday, 8:30 AM to 5:00 PM EST. This position may require additional work hours outside these working hours, including weekends to complete job requirements." That's schedule info. So we can create Schedule section with that. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Schedule. Now we need to extract content for each. Let's extract About the role text: We'll combine the first few paragraphs up to "The main goal of Software Engineer is to design, implement and maintain solutions to support the always changing environment our organization is immersed into, ensuring that the best practices from the Software Development Cycle principles are met." We'll keep as one

    . Responsibilities: We'll list each duty as

  • . Might need to keep the heading titles (Designing and Developing Software Solutions, etc.) as part of the li text. Could embed them as bold? But we just need plain text. We'll include them as part of li. We'll produce
    • Designing and Developing Software Solutions: Architect and develop software solutions using .NET, C#, and integration with Dynamics 365. Ensure that solutions are scalable, secure, and aligned with business requirements and best coding practices.
    etc. But we need to preserve all substantive information; we should not lose any detail. So each duty's sub-bullets should be included. Let's list them precisely: 1. Designing and Developing Software Solutions - Architect and develop software solutions using .NET, C#, and integration with Dynamics 365. - Ensure that solutions are scalable, secure, and aligned with business requirements and best coding practices. 2. Maintaining and Enhancing Application Platforms - Maintain cloud-based platforms and environments of supported applications. - Perform updates and data transformation into Dynamics 365 to support ongoing business needs. 3. Collaborating with the Business Applications Team - Work closely with team members to understand requirements and deliver high-quality software solutions. - Participate in code and architectural reviews to ensure best practices and standards are upheld. 4. Implementing DevOps and CI/CD Practices - Apply DevOps principles to automate and streamline deployment processes using Azure DevOps. - Create and maintain automated tests to ensure code quality and reliability. 5. Supporting Integration and API Development - Develop and maintain integration solutions and APIs that connect Dynamics 365 with other systems. - Drive the API/Platform strategy in a fast-paced, innovative-focused environment. 6. Ensuring Security and Compliance - Implement cloud security controls and ensure that applications adhere to industry standards and regulations. - Collaborate with security teams to address vulnerabilities and ensure the security of application platforms. 7. Continuous Learning and Improvement - Embrace new technologies and stay updated on industry trends to continuously improve software solutions. - Participate in ongoing feedback sessions, knowledge sharing, and retrospectives to improve processes. 8. Providing Technical Documentation - Create and maintain documentation for developers and business users to ensure clarity and ease of use. - Provide post-incident reviews and analysis to improve system resilience and prevent future issues. - Be willing to learn innovative technologies and proactively adapt to technological evolution. We'll combine each main duty and its subpoints into a single li maybe with semicolons. Or we could nest ul inside li but spec says use
    • for any list of duties/requirements/benefits. It didn't forbid nested lists, but safer to keep flat list with each duty as a li containing all subpoints. We'll produce something like:
    • Designing and Developing Software Solutions: Architect and develop software solutions using .NET, C#, and integration with Dynamics 365. Ensure that solutions are scalable, secure, and aligned with business requirements and best coding practices.
    Similarly for others. Now Requirements: Knowledge, Skills, and Abilities list: - Ability to prioritize tasks, aligned with IPC’s strategic priorities, when handed project activities. - Problem solving and a logical approach to work. - Good organizational, communication and people skills. - Understanding of the different project management methodologies and actively participate during all phases. - Meticulous attention to detail. - Ability to perform root cause analysis on code, external and internal processes and data to identify opportunities for improvement. - Excellent analytic skills to work on structured and/or unstructured datasets. - Ability to code processes that support data and workload optimization, tasks automation and improved dependency mapping. - Ability to perform code development by following the Software Development Lifecycle principles. We'll put each as li. Now Qualifications: Qualifications and Experience list: - Bachelor’s degree or equivalent in Computer Science, Engineering, or a related field. Equivalent experience may be considered in satisfaction of the education requirements. - 8+ years of industry experience in software engineering, with a focus on integration solutions, cloud technologies, and data modeling. - Expert knowledge of Microsoft Azure cloud, Dynamics 365, and C#. - Experience with Agile methodology, DevOps principles, and CI/CD concepts, particularly using Azure DevOps. - Experience with Low Code development platforms, such as Microsoft Power Automate. - Strong knowledge of cloud security controls, including tenant isolation, encryption, and key management. - Proficiency in engineering practices such as code refactoring, design patterns, TDD, and continuous integration. - Hands-on experience with SaaS environments, Microsoft API Integration, SQL Server, .NET frameworks, and JavaScript frameworks. - Ability to perform deep-dive analysis and solve technical problems in operational environments. Also there is "Leadership Responsibility: No Travel: This job does not require international travel. Occasionally, local travel within driving distance, and overnight domestic travel may be required." That's not qualification but maybe schedule/travel. We'll treat travel as part of Schedule? Actually schedule section already includes hours; travel could be separate but we have no Travel heading. Could include in Schedule or maybe in Qualifications? Better to add a note in Schedule? But schedule heading is for hours; travel is separate. There's no specific heading for Travel; we could incorporate into Schedule as additional note, but that might be mixing. However instruction: include a section ONLY when the posting has real, specific content for it. There's no explicit Travel heading in the list of allowed headings, but we could put travel info under Schedule? Might be okay but not ideal. However we could also put under Qualifications? Not appropriate. Perhaps we can omit travel info because it's not covered by allowed headings? But we must preserve ALL substantive information; we cannot drop it. So we