Product Manager - Engineering Technology Integrations (Kansas City)
Burns & McDonnell · Kansas City, MO · 1 mo ago
MarketingFull-time
We need to produce HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting.
We need to extract:
- About the role: description of role, strategic leadership, etc. Probably first paragraph(s) before "The selected candidate will join..." etc. Could be "Description" part.
- Responsibilities: The bullet list of functions: External Collaboration, Internal Collaboration, etc. Those are responsibilities.
- Requirements: Required qualifications: Bachelor degree + 7 years relevant consulting experience, preferably transmission and distribution industry. Also maybe "Required Master Degree in Business Administration (MBA) or ability to achieve" is Preferred? Actually it says "Required Master Degree in Business Administration (MBA) or ability to achieve Preferred". That seems confusing: maybe it's "Preferred". We'll treat as Preferred qualification.
- Qualifications: maybe combine Required and Preferred? But we have separate sections: Qualifications and Skills. Could put qualifications (education, experience) under Qualifications, and skills under Skills.
- Skills: list of skills: facilitation, collaboration, organization, problem solving, planning, analytical, communication, ability to influence, etc.
- Benefits: Not mentioned. No benefits details. So we should not include Benefits section.
- Pay: Not mentioned. So omit.
- Schedule: It says "Schedule: Full-time". Also Travel: Yes, 15% of the Time. So we have schedule info. So we can include Schedule section with Full-time and travel 15%.
We also need to include maybe a short for section headings. Use
for metadata like Job ID etc. But instructions: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we can include a
with Job ID etc maybe at top? But they said we should not repeat job title as heading (the page already shows it). We can include a short paragraph for metadata like "Job ID: 264674 | Location: Kansas City, MO | Travel: 15%". However they said "fold minor metadata into a short
or drop it." So we can include a
with that. We must not include boilerplate like EEO, etc. We need to preserve all substantive information. So we need to include all responsibilities bullet points, qualifications, etc. We need to use
for section headings. Use - for any list of duties/requirements/benefits, and
for prose.
We need to output only HTML fragment.
Let's structure:
Job ID: 264674 | Location: Kansas City, MO | Schedule: Full-time | Travel: 15% of the time
Then sections:
About the role
... prose ...
Responsibilities
- External Collaboration: ... (list subpoints? Could keep as one li with semicolons or break into multiple li? Probably each bullet under External Collaboration and Internal Collaboration could be separate li. But we need to preserve all detail. Could break each function as li.
We have many bullet points under External Collaboration and Internal Collaboration. We'll create li for each bullet.
Similarly for Internal Collaboration.
We'll need to capture all.
Let's extract External Collaboration bullet points:
- Develop and maintain external vendor relationships and evaluate integration of their solutions into solutions from other vendors that serve to enhance project processes and workflows across the Burns & McDonnell (BMcD) enterprise.
- Evaluate external partnerships, licensing opportunities, and emerging applications that support middleware integration efforts.
- Research technical and industry expertise with respect to the competition.
- Coordinate product demonstrations from external vendors.
- Review scopes of work for external services requests related to application integration.
- Actively participate in related technical committees, professional organizations, seminars, trade shows, and conferences to promote BMcD’s capabilities and experience, as a leader in our industries.
- Understand emerging or disruptive technology and recognize opportunities for practical applications to enable new and evolving business lines and operating models.
- Remain technology neutral and unbiased toward any specific technology or vendor.
- Perform other duties as assigned.
- May also:
- Lead coordination and planning for BMcD’s involvement in industry conferences; write and present strategies, technical papers, white papers, industry conference presentations and business plans, as required.
- Serve as primary point of contact within BMcD for external product sales and support teams across multiple technology stacks.
We could treat "May also:" as part of responsibilities; we can include those as li as well.
Internal Collaboration bullet points:
- Define and present the product strategy and roadmap across engineering applications to internal stakeholders.
- Architect, design, guide development and actively implement with various global practices and business lines various software configurations and integration solutions to support complex business requirements across engineering applications.
- Consult on application architectures and data practices to support Information Technology and Operations Technology domains.
- Develop technical requirements for products by working with stakeholders (both internal and external) as needed, ensuring that stakeholder and market needs are attained.
- Coordinate with internal teams to align solutions with enterprise data governance, financial parameters, and risk analysis.
- Assess the impact of new and existing technology investment on the business.
- Understand emerging or disruptive technology, such as agentic AI integration, and evolve strategy/roadmap to cultivate opportunities for practical application to enable project execution.
- Monitor the current-state solution portfolio to identify opportunities to improve or replace deficient technologies or solutions misaligned with business requirements.
- Bridge silos between engineering tech stacks.
- Develop and implement product metrics and tools to evaluate cross-platform performance and adoption.
- Collaborate across internal Community of Practices to encourage and highlight successes in cross-platform integration.
- Develop and implement marketing collateral in conjunction with corporate and GP marketing teams.
- Coordinate with Corporate Quality for adherence to QA/QC processes.
- Coordinate with Corporate Change Management team for large change initiatives.
- Perform other duties as assigned.
- Comply with all policies and standards.
- May also:
- Define and present for approval the product strategy and roadmap to internal stakeholders.
- Manage internal Community(ies) of Practice for individual tech stack collaboration.
- Develop and manage Objectives and Key Results.
- Coordinate with IT software procurement team to review financial and usage information.
- Develop and implement marketing collateral in conjunction with corporate and GP marketing teams.
We need to ensure we don't duplicate similar lines (some appear twice). We'll keep as is.
Now Qualifications section: Required qualifications: Bachelor Degree in engineering, architecture, environmental science, business or related degree from an accredited program. and 7 years relevant consulting experience, preferably in the transmission and distribution industry.
Also maybe "Required Master Degree in Business Administration (MBA) or ability to achieve Preferred" is weird; treat as Preferred qualification: MBA or ability to achieve.
We'll put Required qualifications in
maybe.
Preferred qualifications: list many bullet points.
We could combine under Qualifications section with subheadings? But only allowed headings are the specified ones. We could put all qualifications (required and preferred) under Qualifications section as list.
But we also have Skills section separate.
Thus Qualifications: education and experience.
Skills: list of skills: facilitation, collaboration, organization, problem solving, planning, analytical, communication, ability to influence, etc.
Let's extract skills from text:
- Strong facilitation, collaboration, organization, and problem solving skills.
- Proven experience having led and completed projects from business proposal through post-production support preferred.
- Demonstrated success as to budget, savings and/or profit margins in completed projects.
- Ability to filter and distill relevant information and convey business and technical concepts to a diverse client base and internal technical teams.
- Excellent planning and analytical skills.
- Broad knowledge of project management methodologies and tools including the use of Microsoft Project or equivalent.
- Strong ability to influence or lead project execution and guide engineering teams through cultural and operational transitions.
- Strong analytical and problem-solving skills, including application data analysis and transformation at various layers of the architecture.
- Excellent written and verbal communication skills.
- Strong ability to ascertain customer concerns, consider alternatives, and provide customers with guidance to solve their questions.
- Strong organizational and prioritization skills to interact with multiple customers with differing needs.
- Ability to work independently and meet deadlines.
- Experience delivering presentations to senior-level executives and managers.
Also from Preferred qualifications: thorough understanding of multiple engineering and design application suites (e.g.: Autodesk, Bentley, Octave, and/or Esri, with flexibility to incorporate other emerging platforms) and how to integrate data, workflows, and business processes across/between them. Engineering and/or design experience utilizing more than one vendor's software suite. Experience integrating across multiple software suites on client projects. Experience in enterprise transformation projects using industry-standard solutions and middleware technologies.
These could be considered qualifications or skills. We'll put them under Skills maybe.
But we need to avoid duplication. We'll decide:
Qualifications: education (Bachelor degree) and years experience (7 years relevant consulting experience, preferably transmission and distribution). Also maybe MBA preferred.
Skills: all the skill-based bullet points.
Let's craft.
Now schedule section: we already included metadata p; but we could also have Schedule section with Full-time and Travel 15%. Since we already put schedule in metadata, but we could still have Schedule section. The instruction: include a section ONLY when the posting has real, specific content for it. We have schedule info: Full-time, Travel: 15% of the time. So we can have Schedule section.
We'll keep metadata p maybe for Job ID and location; but we could also put location in About the role? Not needed. We'll keep a short p for Job ID and location.
Now produce HTML.
Let's write.
We need to ensure no extra text outside HTML.
We'll output:
Job ID: 264674 | Location: Kansas City, MO
About the role
Burns & McDonnell’s Project Technology Department within Corporate Project Delivery is seeking a Product Manager of Engineering Technology Integrations to provide strategic leadership and tactical guidance across the enterprise. The selected candidate will join a specialized team focused on providing leadership, strategy, analysis and technology to verify that solutions meet business needs and align with enterprise governance, standards, and security. This role bridges product management and enterprise architecture with a specific focus on integrating data and workflows across engineering and design application suites. This Product Manager is responsible for strategic technology planning and internal marketing, gathering and prioritizing product and customer requirements, defining integration vision, and working closely with engineering and construction teams to deliver cross-stack product solutions. This position will co-lead the operational transition toward a technology-first strategy focusing on project lifecycle data integration and collaborating across stacks to define and implement transformational philosophies, technologies, and processes. This Product Manager may also serve as Product Manager of one or two software stacks. Finally, occasional engagement in proposals and client interviews may be required.
Responsibilities
- Develop and maintain external vendor relationships and evaluate integration of their solutions into solutions from other vendors that serve to enhance project processes and workflows across the Burns & McDonnell (BMcD) enterprise.
- Evaluate external partnerships, licensing opportunities, and emerging applications that support middleware integration efforts.
- Research technical and industry expertise with respect to the competition.
- Coordinate product demonstrations from external vendors.
- Review scopes of work for external services requests related to application integration.
- Actively participate in related technical committees, professional organizations, seminars, trade shows, and conferences to promote BMcD’s capabilities and experience, as a leader in our industries.
- Understand emerging or disruptive technology and recognize opportunities for practical applications to enable new and evolving business lines and operating models.
- Remain technology neutral and unbiased toward any specific technology or vendor.
- Perform other duties as assigned.
- Lead coordination and planning for BMcD’s involvement in industry conferences; write and present strategies, technical papers, white papers, industry conference presentations and business plans, as required.
- Serve as primary point of contact within BMcD for external product sales and support teams across multiple technology stacks.
- Define and
for prose. We need to output only HTML fragment. Let's structure:
Job ID: 264674 | Location: Kansas City, MO | Schedule: Full-time | Travel: 15% of the time
Then sections:About the role
... prose ...
Responsibilities
- External Collaboration: ... (list subpoints? Could keep as one li with semicolons or break into multiple li? Probably each bullet under External Collaboration and Internal Collaboration could be separate li. But we need to preserve all detail. Could break each function as li.
We have many bullet points under External Collaboration and Internal Collaboration. We'll create li for each bullet.
Similarly for Internal Collaboration.
We'll need to capture all.
Let's extract External Collaboration bullet points:
- Develop and maintain external vendor relationships and evaluate integration of their solutions into solutions from other vendors that serve to enhance project processes and workflows across the Burns & McDonnell (BMcD) enterprise.
- Evaluate external partnerships, licensing opportunities, and emerging applications that support middleware integration efforts.
- Research technical and industry expertise with respect to the competition.
- Coordinate product demonstrations from external vendors.
- Review scopes of work for external services requests related to application integration.
- Actively participate in related technical committees, professional organizations, seminars, trade shows, and conferences to promote BMcD’s capabilities and experience, as a leader in our industries.
- Understand emerging or disruptive technology and recognize opportunities for practical applications to enable new and evolving business lines and operating models.
- Remain technology neutral and unbiased toward any specific technology or vendor.
- Perform other duties as assigned.
- May also:
- Lead coordination and planning for BMcD’s involvement in industry conferences; write and present strategies, technical papers, white papers, industry conference presentations and business plans, as required.
- Serve as primary point of contact within BMcD for external product sales and support teams across multiple technology stacks.
We could treat "May also:" as part of responsibilities; we can include those as li as well.
Internal Collaboration bullet points:
- Define and present the product strategy and roadmap across engineering applications to internal stakeholders.
- Architect, design, guide development and actively implement with various global practices and business lines various software configurations and integration solutions to support complex business requirements across engineering applications.
- Consult on application architectures and data practices to support Information Technology and Operations Technology domains.
- Develop technical requirements for products by working with stakeholders (both internal and external) as needed, ensuring that stakeholder and market needs are attained.
- Coordinate with internal teams to align solutions with enterprise data governance, financial parameters, and risk analysis.
- Assess the impact of new and existing technology investment on the business.
- Understand emerging or disruptive technology, such as agentic AI integration, and evolve strategy/roadmap to cultivate opportunities for practical application to enable project execution.
- Monitor the current-state solution portfolio to identify opportunities to improve or replace deficient technologies or solutions misaligned with business requirements.
- Bridge silos between engineering tech stacks.
- Develop and implement product metrics and tools to evaluate cross-platform performance and adoption.
- Collaborate across internal Community of Practices to encourage and highlight successes in cross-platform integration.
- Develop and implement marketing collateral in conjunction with corporate and GP marketing teams.
- Coordinate with Corporate Quality for adherence to QA/QC processes.
- Coordinate with Corporate Change Management team for large change initiatives.
- Perform other duties as assigned.
- Comply with all policies and standards.
- May also:
- Define and present for approval the product strategy and roadmap to internal stakeholders.
- Manage internal Community(ies) of Practice for individual tech stack collaboration.
- Develop and manage Objectives and Key Results.
- Coordinate with IT software procurement team to review financial and usage information.
- Develop and implement marketing collateral in conjunction with corporate and GP marketing teams.
We need to ensure we don't duplicate similar lines (some appear twice). We'll keep as is.
Now Qualifications section: Required qualifications: Bachelor Degree in engineering, architecture, environmental science, business or related degree from an accredited program. and 7 years relevant consulting experience, preferably in the transmission and distribution industry.
Also maybe "Required Master Degree in Business Administration (MBA) or ability to achieve Preferred" is weird; treat as Preferred qualification: MBA or ability to achieve.
We'll put Required qualifications in
- maybe.
Preferred qualifications: list many bullet points.
We could combine under Qualifications section with subheadings? But only allowed headings are the specified ones. We could put all qualifications (required and preferred) under Qualifications section as list.
But we also have Skills section separate.
Thus Qualifications: education and experience.
Skills: list of skills: facilitation, collaboration, organization, problem solving, planning, analytical, communication, ability to influence, etc.
Let's extract skills from text:
- Strong facilitation, collaboration, organization, and problem solving skills.
- Proven experience having led and completed projects from business proposal through post-production support preferred.
- Demonstrated success as to budget, savings and/or profit margins in completed projects.
- Ability to filter and distill relevant information and convey business and technical concepts to a diverse client base and internal technical teams.
- Excellent planning and analytical skills.
- Broad knowledge of project management methodologies and tools including the use of Microsoft Project or equivalent.
- Strong ability to influence or lead project execution and guide engineering teams through cultural and operational transitions.
- Strong analytical and problem-solving skills, including application data analysis and transformation at various layers of the architecture.
- Excellent written and verbal communication skills.
- Strong ability to ascertain customer concerns, consider alternatives, and provide customers with guidance to solve their questions.
- Strong organizational and prioritization skills to interact with multiple customers with differing needs.
- Ability to work independently and meet deadlines.
- Experience delivering presentations to senior-level executives and managers.
Also from Preferred qualifications: thorough understanding of multiple engineering and design application suites (e.g.: Autodesk, Bentley, Octave, and/or Esri, with flexibility to incorporate other emerging platforms) and how to integrate data, workflows, and business processes across/between them. Engineering and/or design experience utilizing more than one vendor's software suite. Experience integrating across multiple software suites on client projects. Experience in enterprise transformation projects using industry-standard solutions and middleware technologies.
These could be considered qualifications or skills. We'll put them under Skills maybe.
But we need to avoid duplication. We'll decide:
Qualifications: education (Bachelor degree) and years experience (7 years relevant consulting experience, preferably transmission and distribution). Also maybe MBA preferred.
Skills: all the skill-based bullet points.
Let's craft.
Now schedule section: we already included metadata p; but we could also have Schedule section with Full-time and Travel 15%. Since we already put schedule in metadata, but we could still have Schedule section. The instruction: include a section ONLY when the posting has real, specific content for it. We have schedule info: Full-time, Travel: 15% of the time. So we can have Schedule section.
We'll keep metadata p maybe for Job ID and location; but we could also put location in About the role? Not needed. We'll keep a short p for Job ID and location.
Now produce HTML.
Let's write.
We need to ensure no extra text outside HTML.
We'll output:
- Develop and maintain external vendor relationships and evaluate integration of their solutions into solutions from other vendors that serve to enhance project processes and workflows across the Burns & McDonnell (BMcD) enterprise.
- Evaluate external partnerships, licensing opportunities, and emerging applications that support middleware integration efforts.
- Research technical and industry expertise with respect to the competition.
- Coordinate product demonstrations from external vendors.
- Review scopes of work for external services requests related to application integration.
- Actively participate in related technical committees, professional organizations, seminars, trade shows, and conferences to promote BMcD’s capabilities and experience, as a leader in our industries.
- Understand emerging or disruptive technology and recognize opportunities for practical applications to enable new and evolving business lines and operating models.
- Remain technology neutral and unbiased toward any specific technology or vendor.
- Perform other duties as assigned.
- Lead coordination and planning for BMcD’s involvement in industry conferences; write and present strategies, technical papers, white papers, industry conference presentations and business plans, as required.
- Serve as primary point of contact within BMcD for external product sales and support teams across multiple technology stacks.
- Define and
Job ID: 264674 | Location: Kansas City, MO
About the role
Burns & McDonnell’s Project Technology Department within Corporate Project Delivery is seeking a Product Manager of Engineering Technology Integrations to provide strategic leadership and tactical guidance across the enterprise. The selected candidate will join a specialized team focused on providing leadership, strategy, analysis and technology to verify that solutions meet business needs and align with enterprise governance, standards, and security. This role bridges product management and enterprise architecture with a specific focus on integrating data and workflows across engineering and design application suites. This Product Manager is responsible for strategic technology planning and internal marketing, gathering and prioritizing product and customer requirements, defining integration vision, and working closely with engineering and construction teams to deliver cross-stack product solutions. This position will co-lead the operational transition toward a technology-first strategy focusing on project lifecycle data integration and collaborating across stacks to define and implement transformational philosophies, technologies, and processes. This Product Manager may also serve as Product Manager of one or two software stacks. Finally, occasional engagement in proposals and client interviews may be required.
Responsibilities