Associate Technical Project Manager

We need to output HTML fragment with sections: About Us? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the posting. Content: - About Us: description of Intrado mission. - Responsibilities/Qualifications: Actually they have a heading "Responsibilities/Qualifications" then description: "The Associate Technical Project Manager will support the planning, execution, and completion of technical projects. This role involves collaborating with cross-functional teams, managing project schedules, and ensuring that projects are delivered on time and within scope. The ideal candidate will be a quick learner with some exposure to technology/software development, excellent communication skills, and a passion for project management." Then they list "Key Responsibilities" with sub-bullets: Project Planning and Coordination, Project Execution, Communication And Reporting, Risk Management, Quality Assurance, Technical Support. Each with description. Then "Qualifications": list bullet points: 1-year of experience..., Experience working with project management tools..., Strong organizational..., Excellent communication..., Problem-solving..., Some experience..., Bachelor’s degree..., Equivalent work experience... Then "Total Rewards": description of benefits package, includes list of benefits. Then "The starting hourly wage is anticipated between $22 and $26.40 and will be commensurate with experience." This is pay info. Then EEO boilerplate etc to remove. We need to produce sections: maybe About Us, Responsibilities, Qualifications, Benefits, Pay. We must not include sections with filler placeholder like "commensurate with experience" is not filler? Actually they said never create Pay/Schedule/Benefits sections unless posting actually states them. Pay is stated: starting hourly wage between $22 and $26.40. So we can include Pay section. Benefits: they have Total Rewards describing benefits. So Benefits section. Schedule: not mentioned, so omit. We need to use

  for section headings. We need to use

  • for any list of duties/requirements/benefits. We need to use

    for prose. We need to preserve all substantive info, not invent or summarize away detail. We need to remove boilerplate: EEO, Drug Free Workplace, etc. Also remove duplicated lines. We need to not repeat job title as heading. We need to not put Job ID/requisition numbers as headings (none present). We need to fold minor metadata into short

    or drop it. Not needed. Now we need to decide structure. Potential sections: - About Us (maybe heading "About Us" but they said use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They didn't list About Us but we can still use

    for any heading? The instruction: use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests those are examples, but we can still use other headings? Probably we should stick to those examples; but "About Us" is not in list. However we could use "About the role" as heading for the description about the role? But they have "About Us" describing company. Could we treat that as "About the role"? Not exactly. Maybe we should not include a heading for About Us; we could just put it in a

    without heading? But they said use

    for section headings (e.g. About the role...). It doesn't forbid other headings, but they gave examples. Safer to follow examples: we could use "About the role" for the company description? Might be odd. Better to include a heading "About Us" as

    even if not in examples; likely acceptable. But they said "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This implies those are the allowed headings. However they didn't say you cannot use other headings; they just gave examples. Usually in such tasks, they expect you to use those headings where applicable. Since we have About Us content, we could map to "About the role"? Not ideal. Maybe we can omit About Us heading and just put the paragraph as a

    at top without heading. That would preserve info. The instruction: "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say you must have a heading for every block; you can have prose without heading. So we can put About Us as a

    without heading. That seems fine. Then we need Responsibilities section: we have list of responsibilities. Use

    Responsibilities

    then
    • each responsibility. But we also have a paragraph before the list describing role. That could be a

      inside Responsibilities section before the list. Qualifications: similar. Benefits: we have Total Rewards description with list of benefits. Use

      Benefits

      then maybe a

      summarizing then

      • each benefit. Pay: we have starting hourly wage anticipated between $22 and $26.40 and will be commensurate with experience. The phrase "commensurate with experience" is filler? They said never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. For Pay section, we have actual numbers $22-$26.40, plus the phrase "commensurate with experience". That phrase is filler but we can include it as part of the prose; it's not a heading followed by filler only. So we can include Pay section with

        containing that sentence. We must not include Schedule. Now we need to remove boilerplate: EEO, Veterans/Disabled, Drug Free Workplace, etc. Also remove "Apply today to join us in work worth doing!" maybe considered application instruction? They said remove application instructions. So remove that line. Also remove "Want to love where you work? At Intrado, we offer a comprehensive benefits package that includes..." That's part of Benefits, keep. Now we need to ensure we preserve all substantive information. Let's extract substantive content: About Us paragraph: "Intrado is dedicated to saving lives and protecting communities, helping them prepare for, respond to, and recover from critical events. Our cutting-edge company strives to become the most trusted, data-centric emergency services partner by uniting fragmented communications into actionable intelligence for first responders. At Intrado, all of our work truly matters." That's it. Responsibilities section: Paragraph before list: "The Associate Technical Project Manager will support the planning, execution, and completion of technical projects. This role involves collaborating with cross-functional teams, managing project schedules, and ensuring that projects are delivered on time and within scope. The ideal candidate will be a quick learner with some exposure to technology/software development, excellent communication skills, and a passion for project management." Then list: Key Responsibilities: - Project Planning and Coordination: Assist in defining project scope, objectives, and deliverables in collaboration with senior management and stakeholders; Develop detailed project plans, timelines, and resource allocation schedules; Coordinate internal resources and third parties/vendors for the flawless execution of projects - Project Execution: Monitor project progress and handle any issues that arise; Use appropriate verification techniques to manage changes in project scope, schedule, and costs; Measure project performance using appropriate systems, tools, and techniques - Communication And Reporting: Maintain comprehensive project documentation; Provide regular updates to senior management and stakeholders on project status, risks, and issues; Facilitate communication and collaboration among project team members and stakeholders - Risk Management: Identify potential project risks and develop mitigation strategies; Track project risks and implement contingency plans as needed - Quality Assurance: Ensure that all projects are delivered on time, within scope, and within budget; Conduct post-project evaluations and identify successful and unsuccessful project elements - Technical Support: Provide technical assistance and support to project teams; Understand and analyze technical requirements and translate them into project tasks and milestones We need to preserve all detail. Could break each bullet into multiple

      • items? The instruction: use
        • for any list of duties/requirements/benefits. So each duty could be a
        • . The sub-bullets could be separate
        • or we could keep as one
        • with semicolons. Probably better to split each duty into separate
        • for clarity. But we must not invent or summarize away detail; splitting is fine as long as we keep all detail. Thus we could have
          with each responsibility as a
          • containing the description. Similarly Qualifications: Paragraph? Actually they have a list: Qualifications - 1-year of experience in technical project management, project coordinator, or related role - Experience working with project management tools (e.g., MS Project, JIRA, Asana) - Strong organizational and multitasking abilities - Excellent communication and interpersonal skills - Problem-solving mindset and attention to detail - Some experience in the technology, software, or public safety industries preferred - Bachelor’s degree in Computer Science, Business or a related field - Equivalent work experience in a similar position may be substituted for educational requirements We can put each as
          • . Benefits: From Total Rewards: "Want to love where you work? At Intrado, we offer a comprehensive benefits package that includes what you’d expect (medical, dental, vision, life and disability coverage, paid time off, a 401(k) retirement plan, and several that go above and beyond – paid parental leave, access to a robust library of personal and professional training resources, employee discounts, critical illness, hospital indemnity, access to legal support, pet insurance, identity theft protection, an EAP (Employee Assistance Program) that includes free mental health resources/support, and more!" We can turn that into a

            maybe then a

            • list of benefits. List items: medical, dental, vision, life and disability coverage, paid time off, a 401(k) retirement plan, paid parental leave, access to a robust library of personal and professional training resources, employee discounts, critical illness, hospital indemnity, access to legal support, pet insurance, identity theft protection, an EAP (Employee Assistance Program) that includes free mental health resources/support. We need to preserve all. Pay: "The starting hourly wage is anticipated between $22 and $26.40 and will be commensurate with experience." We can put as

              . Now we need to ensure we don't include any filler heading like Pay with only filler. We have actual numbers. Now we need to output only HTML fragment. Let's craft:

              About Us paragraph.

              Responsibilities

              Role description paragraph.