About this Role

Quanta Services (NYSE: PWR) is a Fortune 300 company and the largest specialty contractor in North America, with $23B+ in annual revenue, 50,000+ employees, and 200+ operating companies. Quanta's Corporate IT organization supports the enterprise with shared technology services, infrastructure, cybersecurity, and business applications.

Historically, Quanta bought its operational technology, defaulting to third-party platforms that were never designed for our industry.

This is changing. With a modern enterprise data platform (Databricks) and an empowered Corporate IT team, Quanta increasingly builds targeted solutions of its own, integrated with our systems of record and grounded in how the work actually happens in the field. This role sits at the center of that shift. The Product Owner sees where a solution should exist and does not yet, forms a clear view of what to build and why, and then drives it all the way from concept to a working tool that people rely on. This is a hands-on delivery role in equal parts vision, build, and implementation.

Priority solution areas are fleet, procurement, project management, and safety.

What You'll Do

Set the Vision (Now and Ongoing)

You will look across the operational landscape, procurement, project management, and safety, and identify where a solution should exist but does not. You will form a clear point of view on what to build, what it should do, and what it is worth, and you will frame that vision so operating company leaders, field users, and Corporate IT all rally behind it. Much of the value you create begins here, in seeing the opportunity before anyone has written a requirement.

Ground It in the Field (Now)

Vision without field reality is just another tool nobody asked for. You will spend meaningful time on site, walking workflows alongside foremen, project managers, procurement staff, and operational leadership, so that what you build reflects how the work is actually done. You will map where inefficiency, duplicated effort, and data gaps live: the six windows someone clicks through to get one answer, the equipment that sits idle for months because nobody had visibility on it, the purchase that gets shotgunned because nobody knew it was already on hand. People in the field will tell you things face to face that they would never put in a ticket.

Own Solutions from Concept to Production (Core)

This is the heart of the role. You will own solutions end to end: framing the concept, defining requirements, shaping the design, and partnering with engineering and data teams to prototype, build, and harden real applications on the Databricks platform, including AI-assisted and rapidly developed tools. You will design the roadmap, prioritize ruthlessly, balance a single operating company's needs against a coherent enterprise design, and keep pushing until the solution is live and doing real work rather than sitting as a promising demo.

Implement in the Real World (Core)

Shipping is not the finish line, implementation is. You will lead the unglamorous work that makes a solution actually land: integrating with systems of record such as JD Edwards, migrating and cleaning real data, handling cutover, training users, and staying close through early production until the tool is genuinely relied upon. You will define what success looks like in measurable terms and iterate relentlessly on real usage and real data.

Drive Adoption (Ongoing)

A tool nobody uses is worth nothing. You will secure both top-down sponsorship and bottom-up buy-in, build solutions people genuinely want, and turn skeptical users into advocates. You will know the difference between a real complaint and cultural resistance, and you will make sure that what works for leadership does not quietly create more work for the crews in the field.

Partner with Engineering and Data, Not Replace Them

You own the problem, the requirements, and the outcome. Engineers and data teams own the code and the architecture. This separation is the point. Your value is operator judgment and field credibility, not writing production software yourself.

Champion Actionable Data

You will push for consistent, trusted metrics that leaders at every level can align on, from cost per mile to cost per man hour, so decisions are made on data everyone agrees with rather than on spreadsheets and tribal knowledge.

Contribute an Operator's Voice to Build-versus-Buy

You will bring a hands-on operator's perspective to enterprise agreement and platform decisions, helping Corporate IT judge where a third-party tool still earns its cost and where Quanta is better served building its own.

What You'll Bring

• 10+ years of progressive experience in construction, utility, energy, or a comparable industrial or field-driven industry, including hands-on operations experience at an operating company, business unit, or a supplier serving that industry.
• Deep, practical knowledge in two or more of the following: fleet and equipment management, procurement and strategic sourcing, project management, or safety operations. You have not just used these functions, you have run them.
• A builder's track record: you have taken solutions from a blank page through design, build, and rollout to real, sustained use, not just proposed them or managed a backlog. You can point to things you conceived that people still rely on today.
• Proven ability to see an unmet need and turn it into a concrete solution, defining what to build and why before anyone hands you a specification, and the drive to shape the work in an ambiguous, first-of-its-kind role.
• Hands-on implementation experience: standing up a new tool or process in a live environment, including data migration, integration with existing systems of record, user training, cutover, and the follow-through required to make it stick.
• Direct experience owning outcomes end to end, whether running a business, a division, or a function, with the commercial judgment that comes from being personally accountable for cost, margin, or P&L.
• The ability to translate messy, real-world operational problems into structured requirements that technical teams can build against, and to hold the line on scope so a solution stays focused and actually ships.
• Fluency in the language and daily reality of field work: you can walk a job site, a yard, a tool room, or a shop floor, quickly understand how the work is done, and earn the respect of the people doing it.
• Strong stakeholder skills across every level, from field crews to executive leadership, and the credibility to earn an operator's trust quickly.
• Willingness and ability to travel frequently to operating company and field locations.

Strongly Preferred

• A portfolio of operational tools, systems, or processes you personally conceived, delivered, and put into production, ideally ones that are still in daily use.
• Direct experience in the electric power, utility, or infrastructure services sector, including familiarity with the equipment, tooling, and workflows those crews depend on every day.
• Experience on both sides of the vendor relationship, having sold to or supplied industrial customers as well as purchased on their behalf, with a real understanding of how pricing, lead times, availability, and service actually work.
• A background in equipment, tooling, rental, or asset-heavy operations, including exposure to the full lifecycle from acquisition and calibration through utilization, transfer, and disposal.
• Experience standing up procurement, sourcing, or purchasing discipline where little existed before, including vendor management, quoting workflows, and requisition-to-consumption tracking.
• Experience partnering with software or data engineering teams to ship internal tools to production, including familiarity with AI-assisted development and modern cloud data platforms (Databricks a strong plus).
• Exposure to enterprise operational systems (i.e., ERP such as JD Edwards; construction platforms such as Procore, HCSS, Autodesk, or InEight; telematics; or requisition, consumption, and warehousing workflows).
• Experience working across multiple operating companies or business units and reconciling different ways of working into a single common approach.
• A background that blends operations and technology, whether formally trained or self-taught, paired with a genuine enthusiasm for building.

Education

• Bachelor's degree in business, engineering, information systems, or a related field, or equivalent professional experience. We are hiring for judgment and field credibility, not credentials.

LOCATION & TRAVEL

Location: Remote / distributed (U.S.). A corporate presence in Houston, TX is available but not required; the team already spans multiple states.

Travel: 25-50% to operating company and field sites. There is no substitute for being on the ground with the people who use what you build.