Jobs · Consulting · New York

Manager - Infrastructure Project Advisory (Strategy & Technology)

KPMG US · New York, NY · 1 mo ago
HybridConsultingFull-time
We need to output HTML fragment with sections: About the role? The posting includes intro paragraphs about KPMG Advisory practice, then a specific job description. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content. We need to preserve all substantive info, remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines, application instructions. Also remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. We need to decide what sections to include. Content: - Intro: "The KPMG Advisory practice is at the forefront of transformation..." This is about the role? Could be "About the role" or "About the practice". Probably "About the role" is appropriate. - Then "KPMG is currently seeking a Manager - Infrastructure Project Advisory (Strategy & Technology) in Infrastructure and Projects Advisory for our Deal Advisory practice." That's job title but we should not repeat job title as heading. So we can embed that in About the role paragraph. - Responsibilities: list bullet points. - Qualifications: list bullet points. - Benefits: mention comprehensive benefits package, medical/dental, vision, disability, life insurance, 401(k), personal well-being benefits, PTO, holidays, breaks. Also mention Total Rewards package. - Pay: The posting mentions salary ranges: "KPMG LLP and its subsidiaries (“KPMG”) complies with all local/state regulations regarding displaying salary ranges. If required, the ranges displayed below or via the URL below are specifically for those potential hires who will work in the location(s) listed. Any offered salary is determined based on relevant factors..." Also link to salary ranges. So there is some pay info, though not explicit numbers. It says they comply and provide link. This is substantive? It mentions salary ranges and link. Should we include Pay section? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state that they comply and provide link to salary ranges. So we can include Pay section with that info (maybe summarizing that salary ranges are available via link). But we must not invent or summarize away detail. We can include the statement about salary ranges and the link. - Schedule: Not mentioned explicitly. There's mention of standard work hours, PTO, holidays, breaks. That's more about benefits/schedule? It mentions "Depending on job classification, standard work hours, and years of service, KPMG provides Personal Time Off per fiscal year." Also "each year KPMG publishes a calendar of holidays... provides eligible employees two breaks each year where employees will not be required to use Personal Time Off". That's schedule-related info (work hours, holidays, breaks). Could be considered Schedule section. However the instruction says only create Schedule section if posting actually states them. It does mention standard work hours, holidays, breaks. So we could include Schedule section with that info. But we need to avoid thin sections. Perhaps combine Benefits and Schedule? But they are separate headings allowed. We could have Benefits section covering medical, dental, etc., and Schedule section covering work hours, PTO, holidays, breaks. We must not include boilerplate like EEO, equal opportunity, visa sponsorship details? The visa sponsorship info is part of Qualifications? Actually it's a requirement: "Applicants must be authorized to work in the U.S. without the need for employment-based visa sponsorship now or in the future; KPMG LLP will not sponsor applicants for U.S. work visa status for this opportunity (no sponsorship is available for H-1B, L-1, TN, O-1, E-3, H-1B1, F-1, J-1, OPT, CPT or any other employment-based visa)". That's a qualification/requirement. Should we keep it? It's substantive info about eligibility. It's not boilerplate; it's a specific requirement. So we should include it under Qualifications or Requirements. The posting has a "Qualifications:" section already; we can include that bullet there. Also there is a line about "KPMG LLP and its subsidiaries (“KPMG”) complies with all local/state regulations regarding displaying salary ranges." That's not boilerplate; it's about pay transparency. Keep in Pay section. We must remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, application instructions. The posting includes many EEO statements at the end: "KPMG is an equal opportunity employer..." etc. Also "No phone calls or agencies please." Also "KPMG recruits on a rolling basis..." etc. Also Los Angeles County applicants stuff. Those are boilerplate/legal; we should remove them. Also remove the link to Benefits & How We Work? That's part of benefits info; we can keep mention of benefits but maybe not the link? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. The link is substantive? It's a reference to where to find more details. Might be considered boilerplate? It's a link to benefits details. Could keep but maybe it's okay. However the instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The benefits link is not those. So we can keep. But we need to avoid too many thin sections. Let's decide sections: - About the role (intro paragraph + job title sentence) - Responsibilities (list) - Qualifications (list) (including education, experience, visa requirement) - Benefits (list) - Pay (paragraph about salary ranges and link) - Schedule (paragraph about standard work hours, PTO, holidays, breaks) We must not include Skills separate if not present; we have skills within qualifications but not separate. We must not repeat job title as heading. Now craft HTML. We need to use

for each section heading. Use
  • for any list of duties/requirements/benefits. Use

    for prose. We need to preserve all substantive info. Let's extract. Intro paragraph(s): "The KPMG Advisory practice is at the forefront of transformation, offering excellent opportunities for individuals to advance their careers and expertise with KPMG. Looking ahead, we anticipate continued evolution and success within the practice, fostering both personal and professional development, thereby creating new pathways for growth. In this ever-changing market environment, our professionals must be adaptable and thrive in a collaborative, team-driven culture. At KPMG, our people are our number one priority. With a wealth of learning and career development opportunities, a world-class training facility, and leading market tools, we help our people continue to grow both professionally and personally. If you're looking for a firm with a strong team connection where you can be your whole self, have an impact, advance your skills, deepen your experiences, and have the flexibility and access to constantly find new areas of inspiration and expand your capabilities, then consider a career in Advisory." Then job sentence: "KPMG is currently seeking a Manager - Infrastructure Project Advisory (Strategy & Technology) in Infrastructure and Projects Advisory for our Deal Advisory practice." We can combine into About the role section. Responsibilities bullet list: - Lead and manage complex infrastructure advisory engagements spanning asset management, transit operations, and technology implementations - Serve as primary client contact, building strong relationships and ensuring successful project delivery through workshops, stakeholder engagement, and strategic guidance - Develop high-quality client deliverables, including business processes, requirements, executive reports, governance frameworks, and operating procedures - Lead technology initiatives involving requirements gathering, process design, configuration management, and implementation of platforms such as IBM Maximo MAS9 and ERM systems - Manage project execution, resources, budgets, timelines, and quality standards while mentoring and developing junior team members - Support practice growth through proposal development, market intelligence, business development activities, and fostering a high-performing, collaborative team culture - Act with integrity, professionalism, and personal responsibility to uphold KPMG's respectful and courteous work environment Qualifications bullet list: - Minimum five years of recent work experience in critical infrastructure (rail, transit, or utilities) with proven experience in a management or technology consulting environment - Master's degree from an accredited college or university in a relevant field (Engineering, Business, Planning, or Technology) is preferred; minimum of a Bachelor's degree from an accredited college/university is required - Hands-on experience in the planning, configuration, or deployment of Enterprise Asset Management (EAM) technologies (IBM Maximo/MAS9, ServiceNow, or equivalent platform) within a transit or asset-intensive operations context - Experience in conducting business process re-engineering and drafting governance documents, SOPs, policies, and asset management strategies - Knowledge of asset management best practices and frameworks (such as ISO 55001); active membership in professional societies (for example, Institute of Asset Management) or an IAM Certificate is preferred - Strong project management, organization, and analytical skills, with the ability to manage multiple priorities in a fast-paced environment - Willingness and ability to travel - Applicants must be authorized to work in the U.S. without the need for employment-based visa sponsorship now or in the future; KPMG LLP will not sponsor applicants for U.S. work visa status for this opportunity (no sponsorship is available for H-1B, L-1, TN, O-1, E-3, H-1B1, F-1, J-1, OPT, CPT or any other employment-based visa) Benefits bullet list (from paragraph): - Comprehensive, competitive benefits package - Medical and dental plans - Vision coverage - Disability and life insurance - 401(k) plans - Robust suite of personal well-being benefits to support mental health - Personal Time Off per fiscal year (based on job classification, standard work hours, and years of service) - Calendar of holidays to be observed during the year - Two breaks each year where employees will not be required to use Personal Time Off (one at year end, one around July 4th) We could also mention "Total Rewards package includes a variety of medical and dental plans, vision coverage, disability and life insurance, 401(k) plans, and a robust suite of personal well-being benefits to support your mental health." Already covered. Pay section: - KPMG complies with local/state regulations regarding displaying salary ranges; ranges are available via the link: https://kpmg.com/us/en/how-we-work/pay-transparency.html/?id=M215DAS_3_26 - Any offered salary is determined based on relevant factors such as applicant's skills, job responsibilities, prior relevant experience, certain degrees and certifications and market considerations. Schedule section: - Depending on job classification, standard work hours, and years of service, KPMG provides Personal Time Off per fiscal year. - Each year KPMG publishes a calendar of holidays to be observed during the year and provides eligible employees two breaks each year where employees will not be required to use Personal Time Off; one is at year end and the other is around the July 4th holiday. We need to ensure we don't duplicate content: PTO and holidays already in Benefits; but we can keep them in Schedule as they relate to schedule. However might be duplication. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is okay if it's in original? But we should avoid duplicated lines. The original had PTO and holidays in benefits paragraph; we could keep them only in Benefits and not repeat in Schedule. However Schedule section would then be thin. Maybe we can combine schedule info into Benefits? But the instruction says we can have Benefits section; we could include schedule-related info there as part of benefits. However they asked to use headings Benefits, Pay, Schedule. If we include schedule info only in Benefits, Schedule section would be empty or filler, which we must not create. So we should either not include Schedule section if we don't have distinct schedule-specific content beyond what's already in Benefits. The posting mentions "standard work hours" and "Personal Time Off

Similar jobs