Sr Project Manager, Technical

We need to output HTML fragment with sections: headings

for sections present: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections that have real specific content. We need to parse the posting. First, the job title is Sr. Project Manager, Technical Leads process and readiness initiatives... Actually the title is "Sr. Project Manager, Technical Leads process and readiness initiatives grounded in field execution acting as a consultant and influencer to deployment." That seems weird but it's the title. We must not repeat job title as heading. We need to extract sections: - About the role: The first paragraph(s) describing the role: "At T-Mobile, we invest in YOU! Our Total Rewards Package ensures that employees get the same big love we give our customers. All team members receive a competitive base salary and compensation package - this is Total Rewards. Employees enjoy multiple wealth-building opportunities through our annual stock grant, employee stock purchase plan, 401(k), and access to free, year-round money coaches. That’s how we’re UNSTOPPABLE for our employees! The Sr. Project Manager, Technical Leads process and readiness initiatives grounded in field execution acting as a consultant and influencer to deployment. This role draws upon deep field and deployment experience to define standards, processes, and readiness frameworks that enable front-line teams and vendors to operate efficiently, safely, and consistently." That's about the role. So we can put that in

About the role

with

content. - Responsibilities: There's a "Job Responsibilities:" list. It includes bullet points (each line starts with a verb). We need to put them in

• . So

  Responsibilities

  with each bullet. - Education and Work Experience: That's qualifications/requirements. We can put under

  Requirements

  maybe. The posting includes "Education and Work Experience:" with bullet points. Also "Knowledge, Skills and Abilities:" which is skills. So we can separate: Requirements (education/experience) and Skills (knowledge, skills and abilities). Also there is "Additional:" with age, work authorization, travel etc. That could be part of Requirements or maybe separate but we can fold into Requirements as minor metadata. - Benefits: There's a paragraph about benefits: "At T-Mobile, our benefits exemplify the spirit of One Team, Together! ..." plus list of benefits. So we need Benefits section. - Pay: There's pay range info: "Total Target Cash Earnings Opportunity: $108,215 - $195,155 National Base Pay Range: $94,100 - $169,700" plus explanation. So we need Pay section. - Schedule: Not mentioned besides travel required yes/no. No schedule details like full-time/part-time, hours. So we should not create Schedule section because no specific content. - Qualifications: Might be same as Requirements. But we already have Requirements. Could also have Qualifications separate but we can combine. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include only those with real content. So we can have About the role, Responsibilities, Requirements, Skills, Benefits, Pay. Possibly also Qualifications if we separate education/experience vs qualifications. But we have Education and Work Experience (requirements). Knowledge, Skills and Abilities (skills). So we can map: - Requirements: Education and Work Experience (including additional must be at least 18, legally authorized, travel required yes/no, DOT regulated etc). We'll include that. - Skills: Knowledge, Skills and Abilities list. We should not repeat job title as heading. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The posting includes some like "Never stop growing!" etc. That's not boilerplate but maybe cultural. We can keep as part of About the role? It's after benefits. It's more about career growth. Could be part of About the role or maybe separate but we can include in About the role as extra paragraph. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all details from the posting, but we can format them. We need to output only HTML fragment, no /, no markdown fences. Let's extract content precisely. First, About the role paragraph(s): "At T-Mobile, we invest in YOU! Our Total Rewards Package ensures that employees get the same big love we give our customers. All team members receive a competitive base salary and compensation package - this is Total Rewards. Employees enjoy multiple wealth-building opportunities through our annual stock grant, employee stock purchase plan, 401(k), and access to free, year-round money coaches. That’s how we’re UNSTOPPABLE for our employees! The Sr. Project Manager, Technical Leads process and readiness initiatives grounded in field execution acting as a consultant and influencer to deployment. This role draws upon deep field and deployment experience to define standards, processes, and readiness frameworks that enable front-line teams and vendors to operate efficiently, safely, and consistently." We should keep that as is. Second, Responsibilities list: "Lead project teams to deliver technical solutions that meet schedule and quality requirements across multiple functions Develop and maintain project schedules, monitor progress, and report status to partners and sponsors Identify and assess project risks and process, tool, and standard gaps; implement mitigation strategies and facilitate risk reviews to minimize impact Coordinate project and process documentation, approvals, and distribution to ensure compliance with company standards Facilitate project meetings and communication to keep teams informed and aligned on project objectives Coordinate with national hubs, technology development, and procurement on deployment readiness alignment Develop and implement standards and workflows for projects and programs Close projects by archiving documentation, transferring deliverables, and translating takeaways into updated processes, business requirements, and recommended improvements Support FOA validation Drive training and adoption Also responsible for other duties/projects assigned by business management as needed" We need to ensure each bullet is a
  • . We'll keep the text exactly. Third, Education and Work Experience: "Bachelor's Degree plus 5 years of related work experience OR advanced degree with 3 years of related experience (Required) Acceptable areas of study include Computer Science, Business Administration, Project Management or combination of equivalent experience and education (Required) 4-7 years of industry experience as a program or product manager within a technology environment, with a progressive record of successful delivery of complex solutions, systems, or services. (Required) Experience working on projects in a wireless industry. (Preferred)" Then Additional: "Must be at least 18 years of age Must be legally authorized to work in the United States Travel: Travel Required (Yes/No): Yes DOT Regulated: DOT Regulated Position (Yes/No): No Safety Sensitive Position (Yes/No): No" We should include these under Requirements. Fourth, Knowledge, Skills and Abilities list: many items each with (Required) or (Preferred). We need to keep them as list items. We should preserve the exact wording including the parenthetical (Required) or (Preferred). The list includes many items. We'll output each as
  • . Let's copy them exactly: "Budget Management (Required) – Manages project budgets and financial commitments throughout the cell site development lifecycle, ensuring expenditures align with approved project scopes and organizational financial guidelines. Business Process Management (BPM) (Required) – Applies BPM principles to document, analyze, and improve end-to-end workflows for network cell site builds and leasing processes, using tools such as Lucid to map current and future state processes. Life Cycle Planning (Required) – Oversees project planning across the full cell site development lifecycle — from lease origination through construction closeout — ensuring checkpoint alignment and on-time delivery at each stage. Management Review (Required) – Prepares and presents project status, process findings, and performance metrics to leadership, facilitating informed decision-making and elevation of risks or blockers. Process Simplification (Required) – Identifies opportunities to streamline and automate routine tasks within leasing and deployment workflows, translating process improvements into actionable business requirements for system enhancements. Progress Monitoring (Required) – Tracks project targets and deliverables across multiple concurrent cell site projects, surfacing deviations early and maintaining alignment with program timelines and efficiency targets. Project Development (Required) – Leads the initiation and structuring of new projects, establishing scope, objectives, partner alignment, and resource plans to support network deployment readiness. Project Documentation (Required) – Creates and maintains accurate project documentation — including process flows, requirements documents, meeting notes, and closeout records — ensuring compliance with company standards. Project Facilitation (Required) – Facilitates large cross-functional working sessions with collaborators across Area, National RF, Procurement, Finance, and FE&O Hubs to drive consensus on process standards and ways of working. Project Management (Required) – Prior proficiency to manage multiple concurrent projects in a complex, fast-paced environment from kick-off through closeout, with consistent focus on scope, schedule, quality, and budget. Project Tracking (Required) – Monitors and reports project progress using T-Mobile's internal tools, including MagentaBuilt, to ensure active portfolios remain on track and partners have real-time insight into status. Resource Management (Required) – Coordinates and optimizes team and vendor resources across projects to ensure the right people and tools are engaged at the right time throughout the deployment lifecycle. Risk Management (Required) – Identifies, assesses, and mitigates risks across projects and processes, elevating issues to leadership as needed and implementing contingency plans to protect project outcomes. Solutions Development (Required) – Translates identified process gaps and business needs into clear, actionable requirements for tool and system enhancements that support lease lifecycle management and deployment readiness. Stakeholder Management (Required) – Builds and maintains effective relationships with a broad set of internal partners — including field personnel, procurement, finance, and engineering teams — to align priorities and drive cross-functional collaboration. Technical Project Management (Required) – Applies technical PM methods to manage complex, multi-workstream projects tied to network infrastructure, tool development, and process automation initiatives. Vendor Management (Required) – Manages relationships with external vendors and internal procurement teams to ensure timely delivery of goods and services in alignment with project scope and budget. Ability to Translate Process into Business Requirements for System Enhancements (Required) – Captures workflow documentation and collaborator input to author structured business requirements that enable technology teams to build or enhance tools supporting deployment processes. Agile Methodology (Preferred) – Familiarity with Agile frameworks is a plus for managing iterative process improvement and tool development workstreams. Contract Review (Preferred) – Experience reviewing lease agreements, vendor contracts, or procurement documents to ensure terms align with project and organizational requirements. Cost Efficiency (Preferred) – Track record of identifying cost-saving opportunities within project execution or vendor management activities. Leadership Development Programs (Preferred) – Participation in or facilitation of leadership or professional development initiatives to grow team capabilities. Project Implementations (Preferred) – Hands-on experience managing the implementation phase of projects, including user acceptance testing, training rollout, and launch support. Project Team Management (Preferred) – Experience leading and developing project team members, including workload distribution, performance feedback, and skills coaching. Schedule Adherence (Preferred) – Proven track record to maintain project schedules under competing priorities and dynamic scope changes. Schedule Development (Preferred) – Experience building detailed project schedules using tools such as MagentaBuilt or Microsoft Project, including phase gate sequencing and critical path analysis. Working Knowledge of Lucid, MagentaBuilt, Talon & ScopeWorker (Preferred) – Proficiency in T-Mobile's core project and process management tools — Lucid for process documentation, MagentaBuilt for project tracking, Talon for closeout packages and site surveys, and ScopeWorker for requisition management — is strongly preferred. Knowledge of RF, Development and Ops Processes (Preferred) – Understanding of T-Mobile's RF engineering, network development, and operations workflows to effectively facilitate cross-functional process discussions and requirements gathering. Ability to Document