Manager, Software Engineering

We need to output HTML fragment with sections only if content present. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to parse the posting. First, remove boilerplate: "About The Role" heading is present; we will use

About the role

and then prose. We need to separate sections: About the role (intro paragraph). Then responsibilities: list of duties. Then qualifications/requirements: maybe combine? The posting includes "What You'll Get To Do" (responsibilities), "You'll Bring These Qualifications" (qualifications), "What We Can Offer You" (benefits). Also there is mention of WorkFlex hybrid work program (benefits). Also mention of benefits package (but no specifics). We should not create Benefits section unless specific content. The posting says: "We offer a highly competitive, comprehensive benefits package so you can worry less and focus on what truly matters. Please click here to review our benefits on our company website." That's vague; not specific. So we should not create Benefits section because no specific benefit details. However we have WorkFlex description: hybrid work program details. That could be considered a benefit (schedule/flexibility). Could be placed under Benefits or Schedule? The instruction: include a section ONLY when posting has real, specific content for it. WorkFlex is specific: hybrid work program offering flexibility to work from home while also requiring in-office workdays. That's a specific benefit. So we could create a Benefits section with that description. Or maybe a Schedule section? WorkFlex is about work arrangement, could be considered Schedule. But we have both Benefits and Schedule possible. The instruction: prefer a few substantive sections over many thin ones. So we could combine WorkFlex into Benefits section (since it's a benefit). Or we could create a Benefits section with that description. We'll not create Schedule unless explicit schedule details (like hours). Not present. Pay: not mentioned. So omit Pay. Thus sections: About the role, Responsibilities, Qualifications (or Requirements), Benefits (WorkFlex). Possibly also Skills? The qualifications list includes many technical skills; could be under Requirements or Qualifications. We'll use Requirements for qualifications and maybe Skills separate? But we can combine qualifications and skills into one Requirements section. The instruction: use headings for e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose which to include. We have About the role, Responsibilities, Requirements (or Qualifications), Benefits. We'll not duplicate. We need to preserve all substantive information. So we need to include all points from "What You'll Get To Do" as list items under Responsibilities. Also include all points from "You'll Bring These Qualifications" as list items under Requirements (or Qualifications). Also include the introductory paragraphs under About the role. We must not repeat job title as heading. Already not. We must not include Job ID etc. We must remove boilerplate like EOE etc. At end there is "EOE M/F/D/V Females and Minorities Encouraged to Apply" - remove. Also remove "Please click here to review our benefits on our company website." That's a link instruction; but it's part of benefits description. Since we are not including Benefits section with specifics, maybe we still include WorkFlex but not that line. The line about clicking is application instruction? It's a reference to benefits page; could be considered boilerplate. We'll remove it. Now craft HTML. Structure:

About the role

... (intro paragraphs)

Responsibilities

• ... each duty

Requirements

• ... each qualification

Benefits

... WorkFlex description

We need to ensure we preserve all substantive info from About the role: The first paragraph(s) after "About The Role". Let's extract: "About The Role It's a great time to join us at Airlines Reporting Corporation (ARC)! ARC accelerates the growth of global air travel by delivering forward-looking travel data, flexible distribution services and other innovative industry solutions. We are a leading travel intelligence company with the world’s largest, most comprehensive global airline ticket dataset, including more than 15 billion passenger flights. By working here, you can contribute to solutions and expertise that strengthen economies and enrich lives. We think big, embrace challenges and explore new ideas to lead the way for the travel industry. ARC is looking for a talented Manager, Software Engineer to join our team! You will oversee multiple concurrent large-scale projects, direct the allocation of resources, and set priorities for a team of employees and contractors who perform software engineering for the full product stack in support of ARC products and services. You will drive the development of new products within a complex multi-platform environment. You will meet challenging development and support commitments and improve upon development processes. You will help grow, develop and mentor a team of software engineers and align with operations, site reliability and the product teams. You will quickly assess team/project needs, capacity management and competency and make prioritization changes where necessary. You will provide deep technical input to products that align with ARC’s strategy and work with peers to implement a comprehensive project based planning process across all software groups and projects." That seems like a mix of About the role and responsibilities. Actually the "You will..." sentences are responsibilities. The instruction says we should have a Responsibilities section for duties. So we should split: About the role includes the introductory description up to "ARC is looking for a talented Manager, Software Engineer to join our team!" Then responsibilities start with "You will oversee..." etc. However the posting also has a separate "What You'll Get To Do" section with more responsibilities. So we need to combine all responsibility sentences from both places. Thus About the role paragraph: up to the exclamation before "You will oversee..." Let's capture: "About The Role It's a great time to join us at Airlines Reporting Corporation (ARC)! ARC accelerates the growth of global air travel by delivering forward-looking travel data, flexible distribution services and other innovative industry solutions. We are a leading travel intelligence company with the world’s largest, most comprehensive global airline ticket dataset, including more than 15 billion passenger flights. By working here, you can contribute to solutions and expertise that strengthen economies and enrich lives. We think big, embrace challenges and explore new ideas to lead the way for the travel industry. ARC is looking for a talented Manager, Software Engineer to join our team!" We need to ensure we keep the exclamation and punctuation. Now responsibilities: combine the "You will..." sentences from the first paragraph after that, plus the bullet list under "What You'll Get To Do". Let's extract them. First set (after "You will oversee..."): - oversee multiple concurrent large-scale projects - direct the allocation of resources - set priorities for a team of employees and contractors who perform software engineering for the full product stack in support of ARC products and services - drive the development of new products within a complex multi-platform environment - meet challenging development and support commitments and improve upon development processes - help grow, develop and mentor a team of software engineers and align with operations, site reliability and the product teams - quickly assess team/project needs, capacity management and competency and make prioritization changes where necessary - provide deep technical input to products that align with ARC’s strategy and work with peers to implement a comprehensive project based planning process across all software groups and projects Now "What You'll Get To Do" list: - Support software engineering by providing patterns to deliver the optimal product; including communicating and constantly improving design patterns. - Mentor other engineers. - Provide overall technical leadership to software and site reliability engineers. - Partner with product owners, business SMEs and site reliability engineering to analyze the business needs and provide a supportable and sustainable, engineered solution. - Ensure that the overall technical solution aligned with the business needs. - Drive the creation and modifications of the product portfolio components, identify and engage all technical resources necessary to contribute to the solution. - Ensure the solution is consistent with ARC architecture, design and development standards. - Develop applications using industry best practices. - Make adjustments to adopt new methodologies that provide the business with increased flexibility and agility. - Stay current with latest development tools, technology ideas, patterns and methodologies; share knowledge by clearly articulating results and ideas to key stakeholders. - Continue to grow in people development and enterprise influence. We need to preserve all; combine into one list (maybe deduplicate overlapping items like mentor other engineers vs help grow... but we should keep both as they are distinct). We'll just list all. Now Requirements/Qualifications: extract from "You'll Bring These Qualifications". It's a long list with many items separated by line breaks. We need to turn each line into

. Ensure we keep all details. Let's list them: - Bachelor’s Degree in Computer Science or related field; or equivalent experience - 7+ years of application programming in both front end User Interfaces, server-side application and database queries - 3+ years of engineering leadership, managing multiple workstreams and leading blended internal / external delivery models - 5+ years of experience with full cycle application development (Full SDLC experience: design, development, delivery, etc.) - 3+ years with Agile, Scrum, DevOps, XP, and Continuous Integration and Continuous Delivery - 5+ years of experience implementing modern applications using: - Cloud Based Solutions/Technologies (AWS, Google, Azure). AWS developer environment including, but not limited to, Lambda, API Gateway, DynamoDB, S3, Cloudwatch - Implementation of modern application and infrastructure design patterns, including micro-services and containers, disposable, reactive, stateless and distributed patterns - Open source technologies including, but not limited to, NodeJS, OpenJDK, React, Python and NoSql DynamoDB database(s) - DevOps tools including, but not limited to, Terraform/Cloud formation, Jenkins pipeline, GIT, Jira, Confluence, Jenkins, Sonar, Nexus, automated test and deployment tools - Data warehouse platforms (such as Teradata, Snowflake, Redshift). Expertise with SQL, database design/structures, ETL/ELT design patterns, datamart structures (star, snowflake schemas, etc.) - Experience w/Data Lake concepts and design patters (AWS S3, parquet, python, lambda, java, hadoop, Spark, noSQL mongoDB, Dynamodb, Athena, etc.) - Working knowledge of integrating AI and LLM APIs into production applications, with good knowledge of RAG, vector databases, LLMs, and prompt engineering. - Experience with AI coding tools such as GitLab Duo, GitHub Copilot, Cursor IDE, and similar tools to accelerate and improve software development workflows. - Proven ability to lead and mentor technical teams and collaborate with stakeholders at all levels to reliably move efforts from multiple workstreams from backlog through to production. - Proven ability to influence technology strategy and best practices across peer and leadership groups to support an agile development culture - Outstanding communication skills (verbal and written) and ability to communicate with internal and external customers and all levels of management, including communicating technical information to nontechnical audiences - A strong intellectual curiosity to continually challenge what exists and explore what should be changed to best meet evolving business and market - A strong passion to support peers to help meet timelines on larger projects Note there is some formatting: after "5+ years of experience implementing modern applications using:" there is a colon and then a list of sub-items. We need to preserve as list items; we could either keep as a single item with subdetails or break into sub-items. The instruction: use

• for any list of duties/requirements/benefits. So we can treat each top-level bullet as
• . The sub-items could be part of the same
• text. That's fine. Now Benefits: WorkFlex description: "Joining ARC means joining a team that is motivated, diverse, creative, collaborative and solutions-oriented. We think big, embrace challenges, and explore new ideas to lead the way for