Technical Project Manager (Contractor Position)

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. We need to preserve all substantive information. We need to parse the posting. Let's extract sections: - About the role: The first paragraph about MBTA vision, mission, values, and then "Job Summary The Technical Project Manager for Transit Technology will deploy and implement technology solutions..." That's about role. So we can put that in

About the role

with

containing that content. - Responsibilities: Duties & Responsibilities section includes many bullet-like sentences. We need to convert to

• . The text includes headings like "Implement Technology Solutions", "Project Management", "General". Those could be subheadings but we only have

  for sections; we can keep them as

  maybe? But we can treat each bullet as

  . The instruction: Use

  • for any list of duties/requirements/benefits. So we need to list each duty as
  • . We can group under subheadings maybe as

    but not required. We'll just produce a list. - Requirements: Minimum Requirements & Qualifications section. That includes bullet-like list of qualifications. We'll put under

    Requirements

    (or Qualifications?). The instruction includes both Requirements and Qualifications as possible headings. We have both Minimum Requirements & Qualifications and Preferred Experience & Skills. We could split: Requirements for minimum, Qualifications for preferred? But they said use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Requirements for minimum qualifications, Qualifications for preferred experience & skills, Skills maybe for specific skills? However we have Preferred Experience & Skills which includes both experience and skills. Could treat as Qualifications. Or we could have Requirements (minimum) and Qualifications (preferred). Skills maybe not needed if covered. We also have Substitutions section (alternative qualifications). That's part of minimum requirements. We'll include within Requirements. We have Job Conditions etc. Those are not specifically requested headings; they could be omitted if not matching headings. But we need to preserve ALL substantive information; we cannot drop them unless they fit under a heading. The instruction: "Prefer a few substantive sections over many thin ones." But also "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to include all info somewhere. If we don't have a heading for Job Conditions, we could put them under Requirements or Qualifications? Might be better to create a section "Job Conditions" but not in allowed list? The allowed list includes only those specific headings; but we could still include other headings? The instruction: "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, not exclusive? It says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. But we also need to preserve all info; we could embed job conditions within Requirements or Qualifications as a paragraph. Similarly, "Disclaimers And Definitions" etc are boilerplate; we should remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The disclaimer section includes legal stuff; we should remove it as boilerplate. The "Application Completion:" etc also boilerplate; remove. Thus we keep: About the role (vision/mission + job summary), Responsibilities (duties), Requirements (minimum qualifications + substitutions), Qualifications (preferred experience & skills), Skills maybe we can extract specific skills from preferred? But we could also put skills under Qualifications. The instruction includes Skills as possible heading; we could create a Skills section listing specific skills: e.g., "Experience with statistical modeling or data science", "Experience with support for or integration between transportation data, scheduling, dispatch, or timekeeping systems such as TransitMaster, HASTUS, TimeClock Plus, Automated Passenger Counters, or similar." Also "Experience working for a public agency", "Experience in transit or transportation". Those could be skills. We also have "Job Conditions" which includes ability to read/comprehend English, age, commute, etc. Those could be considered Requirements or Qualifications. We'll put them under Requirements as they are eligibility criteria. We have no explicit Pay, Benefits, Schedule info in posting. So we should NOT create those sections because they are not stated. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." So we omit those. Thus final HTML will have sections: About the role, Responsibilities, Requirements, Qualifications, Skills (maybe). We need to ensure we don't create empty sections. Let's extract content precisely. About the role: Paragraph: "At the MBTA, we envision a thriving region enabled by a best-in-class transit system. Our mission is to serve the public by providing safe, reliable, and accessible transportation. MBTA’s core values are built around safety, service, equity, sustainability, culture, and accessibility, and each employee that works for the MBTA performs their roles based on our vision, mission, and values. This includes attendance, participation, and contribution in local safety committee meetings as needed. Job Summary The Technical Project Manager for Transit Technology will deploy and implement technology solutions administered by the MBTA’s Transit Technology division or other teams across the Transformation & Technology Department. The Transit Technology team is responsible for designing, building, and maintaining dispatching systems and other technology tools that enable MBTA Operations division to deliver safer, more efficient, and more reliable transit services. This role will span across the MBTA’s modern civic technology teams (e.g., Software Engineers, Product Managers, UX Research & Design staff, Application Analysts) and the front-line operations departments critical for delivering transit service every day. The Technical Project Manager will use their deep technical IT knowledge, expertise at managing vendors, and technical understanding of transit operations processes to drive clarity and organizational change. They will manage and oversee smooth deployments of technical systems and ensure that feedback from operations stakeholders and users are part of technical teams’ iteration and maintenance processes. This role will be able to work successfully across different transit technology teams/topics, and maintain their own roadmap based on priorities set by MBTA leadership." We need to ensure we don't repeat the job title as heading; we already have heading About the role. Now Responsibilities: The Duties & Responsibilities section includes many items. Let's extract each bullet-like sentence. The text: "Duties & Responsibilities Implement Technology SolutionsProvide rapid-response project and information technology support during emergencies.Identify, lead, and support technical initiatives to improve Operations processes and technologies, including but not limited to automation, consolidation, standardization, resiliency planning, and communication with stakeholders.Define user requirements for system modification, enhancements, and integration.Develop or work from detailed system and program specifications.Develop related tracking metrics and reports for Operations.Develop technical specifications, contract documents, schedules, and budgets.Manage the preparation of user documentation and train users on application systems.Prepare and maintain program documentation, including data flow diagrams and program turnover documentation.Make recommendations for and scope system enhancements.Work with technology teams to scope or manage technology feature development.Work with MBTA Procurement to scope, initiate, and administer complex procurements of vendor systems/support while adhering to technology best practices.Project ManagementDevelop and manage comprehensive project plans—including scope, goals, budget, timeline, and deliverables—while prioritizing critical path tasks and resource allocation.Communicate effectively through written and verbal channels, lead productive meetings, and deliver presentations with confidence and minimal oversight.Provide regular updates on project status, timelines, and key metrics; document process milestones and lead retrospective evaluations to drive continuous improvement.Identify and mitigate risks and blockers throughout all project phases, escalating issues as needed to maintain momentum.Guide cross-functional teams to act with urgency and stay aligned with timelines, roadmaps, and deliverables.Critically review project documentation to ensure feasibility, mitigate risk, and optimize planning.Assist with the planning and coordination of overall project management workload and staff deliverables across MBTA Transit Technology teams.GeneralBe a committed, vocal, collaborative member of the Transit Technology division and push for excellence in any/all dimensions of its work.Prepare project-related correspondence, reports, charts, and presentations.Work independently in addressing complex tasks in a time-sensitive environment.Respond to each inquiry, whether from a customer, vendor, or co-worker, in a courteous and professional manner consistent with the Authority's Customer Service quality standard.Visit work sites and/or attend off-site meetings throughout the MBTA service area.Perform all other duties and projects that may be assigned.Additional responsibilities may include a focus on one or more departments or locations. See the applicable addendum for department or location-specific functions." We need to split into list items. Each sentence seems separated by a period but there is no spacing. We'll parse manually. Let's list: - Provide rapid-response project and information technology support during emergencies. - Identify, lead, and support technical initiatives to improve Operations processes and technologies, including but not limited to automation, consolidation, standardization, resiliency planning, and communication with stakeholders. - Define user requirements for system modification, enhancements, and integration. - Develop or work from detailed system and program specifications. - Develop related tracking metrics and reports for Operations. - Develop technical specifications, contract documents, schedules, and budgets. - Manage the preparation of user documentation and train users on application systems. - Prepare and maintain program documentation, including data flow diagrams and program turnover documentation. - Make recommendations for and scope system enhancements. - Work with technology teams to scope or manage technology feature development. - Work with MBTA Procurement to scope, initiate, and administer complex procurements of vendor systems/support while adhering to technology best practices. - Develop and manage comprehensive project plans—including scope, goals, budget, timeline, and deliverables—while prioritizing critical path tasks and resource allocation. - Communicate effectively through written and verbal channels, lead productive meetings, and deliver presentations with confidence and minimal oversight. - Provide regular updates on project status, timelines, and key metrics; document process milestones and lead retrospective evaluations to drive continuous improvement. - Identify and mitigate risks and blockers throughout all project phases, escalating issues as needed to maintain momentum. - Guide cross-functional teams to act with urgency and stay aligned with timelines, roadmaps, and deliverables. - Critically review project documentation to ensure feasibility, mitigate risk, and optimize planning. - Assist with the planning and coordination of overall project management workload and staff deliverables across MBTA Transit Technology teams. - Be a committed, vocal, collaborative member of the Transit Technology division and push for excellence in any/all dimensions of its work. - Prepare project-related correspondence, reports, charts, and presentations. - Work independently in addressing complex tasks in a time-sensitive environment. - Respond to each inquiry, whether from a customer, vendor, or co-worker, in a courteous and professional manner consistent with the Authority's Customer Service quality standard. - Visit work sites and/or attend off-site meetings throughout the MBTA service area. - Perform all other duties and projects that may be assigned. - Additional responsibilities may include a focus on one or more departments or locations. See the applicable addendum for department or location-specific functions. We'll put each as

    . Now Requirements (minimum). Extract Minimum Requirements & Qualifications section: "Bachelor’s degree field from an accredited institution in computer science, information science, project management, software engineering, civil engineering, planning, or a related field.Five (5) years of experience managing, implementing, or supporting the managagement and implementation of technical operations processes, including managing vendors and developing technical scopes of work to translate operational needs into technical