Data Solutions Developer

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the description. First, remove boilerplate: cookie/navigation/legal/EEO etc. The description includes "Location Details:", "Work alongside...", etc. We need to produce sections. We need to decide headings: Use

for each section. We must not repeat job title as heading. We need to include sections only if content present. Let's extract content: - About the role: The description starts: "Evans is hiring Data Solutions Developer resource to join one of their growing contracts supporting the Federal Aviation Administration. This role will support the deployment of an air traffic support system building solutions end-to-end. The ideal candidate can take high-level operational requirements, design the technical architecture, and write production code to deliver working software. This ideal candidate has experience executing end-to-end ownership—from data modeling and server-side development through user interface delivery, testing, and sustainment." That's about the role. - Location Details: "Location Details: This role is mostly remote with occasional on-site requirements at the Department of Transportation Headquarters in Washington D.C. and the FAA Headquarters in Egg Harbor Township, NJ." This could be part of About the role or separate? Not a required heading; we could include under About the role or maybe a separate "Location" but not in list of allowed headings. Since only allowed headings are given, we should fold location into About the role or maybe into a short

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

or drop it." So location is minor metadata; we can include a short

after About the role. - Responsibilities: The bullet list after location: "Work alongside the current data solutions developer and the Project Coordination team to translate operational requirements into scalable technical solutions. Design, develop, enhance, and maintain databases, dashboards, applications, reports, and decision-support tools used to manage Implementation. Develop new and centralized capabilities that improve consistency, automation, data integration, and efficiency across recurring Implementation processes. Identify opportunities to reduce manual data handling and improve the reliability and usability of Implementation information. Test, troubleshoot, document, and sustain developed solutions as requirements and operational needs evolve. Provide sufficient technical depth and continuity to reduce reliance on a single developer for critical Implementation data and application capabilities." These are responsibilities. - Requirements: The section titled "Requirements" includes: "A minimum of 16 years of relevant experience is required. Relevant degrees may be credited toward the experience requirement as follows: Bachelor's degree (5 years), Master's degree (3 years), and PhD (7 years)." Then a list of specific requirements: Advanced SQL & Data Engineering..., Operational Data Architecture..., Data Integrity & Sustainment..., Developing and managing complex Power BI reports..., Translating analytical data..., Power Pages & Front-End Development..., Web Development & User Experience..., Forms, Data & Business Logic..., Security, Testing & Troubleshooting... These are detailed requirements; could be considered under Requirements or Skills. The instruction: Use headings for sections like Requirements, Qualifications, Skills. We need to decide where to put each piece. We have a "Requirements" heading in the posting; we can use that. Then we have "The Evans Experience" which is about company culture; maybe not needed. Then "We Take Care Of Our Own (Benefits)" which is benefits. Then "Work Environment and Physical Demands" etc. Not needed. Then "Work Authorization" etc. Not needed. Then "Identity Statement" etc. Not needed. Then "Compensation" with salary range. Thus we have sections: About the role, Responsibilities, Requirements, Benefits, Pay. We might also have Skills: The detailed list could be considered Skills. But we already have Requirements covering experience and skill areas. Could split: Requirements for experience/education, Skills for technical competencies. However the posting lumps them together under "Requirements". To avoid thin sections, we could keep a single Requirements section that includes both experience and skill details. That's acceptable. Benefits: The bullet list under "We Take Care Of Our Own (Benefits)" includes many items. Pay: The compensation section includes salary range. Schedule: Not mentioned; we should not create Schedule section. Thus output HTML with sections: About the role, Responsibilities, Requirements, Benefits, Pay. We need to use

for each section heading. Use

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

  for prose. We must preserve all substantive information; do not invent or summarize away detail. Must not omit any substantive info. We need to include location as a short

  maybe after About the role. We need to include the bullet points for responsibilities as

  • . We need to include the requirements list: includes the experience requirement and degree conversion, then the bullet list of skill areas. We'll need to format as
    • for each bullet. The experience requirement could be a

      or part of list? It's a requirement; we can put as

      then list. We need to include the benefits list as

      • . We need to include pay as

        with salary range. We must not include boilerplate like "We Take Care Of Our Own (Benefits)" heading; we just use Benefits heading. We must not include "Work Environment and Physical Demands", "Work Authorization", "Identity Statement", etc. We must not include "The Evans Experience" etc. We must not include "Location Details:" as heading; we can incorporate as a short

        . Now craft HTML. Start with

        About the role

        then

        ... include location sentence maybe as separate

        . Let's write the About the role prose: "Evans is hiring a Data Solutions Developer to join one of their growing contracts supporting the Federal Aviation Administration. This role will support the deployment of an air traffic support system building solutions end-to-end. The ideal candidate can take high-level operational requirements, design the technical architecture, and write production code to deliver working software. This ideal candidate has experience executing end-to-end ownership—from data modeling and server-side development through user interface delivery, testing, and sustainment." Then location:

        Location: This role is mostly remote with occasional on-site requirements at the Department of Transportation Headquarters in Washington D.C. and the FAA Headquarters in Egg Harbor Township, NJ.

        Now Responsibilities heading:

        Responsibilities

        then
        • each bullet. List bullets: - Work alongside the current data solutions developer and the Project Coordination team to translate operational requirements into scalable technical solutions. - Design, develop, enhance, and maintain databases, dashboards, applications, reports, and decision-support tools used to manage Implementation. - Develop new and centralized capabilities that improve consistency, automation, data integration, and efficiency across recurring Implementation processes. - Identify opportunities to reduce manual data handling and improve the reliability and usability of Implementation information. - Test, troubleshoot, document, and sustain developed solutions as requirements and operational needs evolve. - Provide sufficient technical depth and continuity to reduce reliance on a single developer for critical Implementation data and application capabilities. Now Requirements heading:

          Requirements

          We need to include experience requirement and degree conversion as prose or list. Could be

          A minimum of 16 years of relevant experience is required. Relevant degrees may be credited toward the experience requirement as follows: Bachelor's degree (5 years), Master's degree (3 years), and PhD (7 years).

          Then list of skill areas as
          • . Each bullet is a heading-like phrase with description. We need to preserve the detail exactly as posted. Let's extract each bullet: - Advanced SQL & Data Engineering: Advanced SQL proficiency, including complex queries, joins, subqueries, data transformation, troubleshooting, and performance optimization in support of operational applications, reporting, and analytics - Operational Data Architecture: Hands-on experience designing relational schemas, data models, and application data layers around complex operational workflows, reporting requirements, and evolving business needs - Data Integrity & Sustainment: Experience designing and maintaining validation logic, data integrity controls, schema changes, indexing and performance considerations, and maintainable data structures that can evolve as operational requirements change - Developing and managing complex Power BI reports and dashboards using advanced DAX and data modeling - Translating analytical data into decision support models for senior leadership - Power Pages & Front-End Development: Significant hands-on experience developing and maintaining custom Power Pages applications and production-quality user interfaces, including customization beyond out-of-the-box components. - Web Development & User Experience: Strong proficiency in HTML, CSS, and JavaScript, with the ability to build responsive, intuitive interfaces that support complex operational workflows. - Forms, Data & Business Logic: Experience developing sophisticated forms and data-driven applications with conditional logic, validation, dynamic content, multiple data sources, and integration with Dataverse and related Power Platform components. - Security, Testing & Troubleshooting: Experience implementing role-based access and independently testing, debugging, and resolving front-end, application logic, data interaction, and integration issues. We need to keep the colon and description. Now Benefits heading:

            Benefits

            then
            • each benefit. List from "We Take Care Of Our Own (Benefits)": - Supporting Work-Life Integration - Professional Development & Educational Assistance w/ Extensive Growth Resources - Annual Discretionary Bonus, Spot Bonus, and Peer Recognition Programs - Paid Maternity & Paternity Leave - Medical/Dental/Vision Benefits - Company-Paid Life Insurance - Short-Term & Long-Term Disability Benefits - Flexible Spending Accounts (FSA) & Health Savings Accounts (HSA) - Generous PTO & Paid Holidays - 401(k) Retirement Plan, Evans' Contribution and 100% Vesting We need to preserve exactly as posted. Now Pay heading:

              Pay

              then

              Salary is determined by various factors, including but not limited to location, the individual's particular combination of education, knowledge, skills, competencies, and experience, as well as contract-specific affordability and organizational requirements. The projected compensation range for this position is $125,000 to $140,000 (annualized USD). The estimate displayed represents the typical salary range for this position and is just one component of Evans's total compensation package for employees.

              We should not include extra fluff like "Compensation" heading; we use Pay. Now ensure we didn't miss any substantive info: The "Work Environment and Physical Demands" includes ability to work in fast-paced, dynamic environment, reasonable accommodations per ADA, contact email. This is minor metadata? Could be considered as part of About the role or maybe we should include as a short

              under About the role? The instruction says fold minor metadata into a short

              or drop it. This is about work environment; could be considered minor. We could include a short

              after About the role: "Ability to work in a fast-paced, dynamic environment. Reasonable accommodations are provided in accordance with ADA." But we already have location paragraph; we could add another paragraph. However we must preserve all substantive information; this is substantive but maybe minor. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

              or drop it." This is not Job ID; it's work environment. It's not explicitly listed as minor metadata but could be considered. Safer to include as a short

              after location. Also "Work Authorization" etc is minor metadata; we could drop. "Identity Statement" also minor; drop. Thus we will include two short paragraphs after About the role: location and work environment. Now check for any other substantive info: "The Evans Experience" is culture description; could be considered minor but maybe we should include as part of About the role? It's about company culture; could be considered substantive but not required heading