Software Engineer, Field & Operational Technology Solutions

Software Engineer, Field & Operational Technology Solutions

Quanta Services is seeking a Software Engineer, Field & Operational Technology Solutions to join our Corporate Information Technology team, reporting to the Senior Manager, Enterprise 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 is where those solutions get built. Working alongside a product owner who brings the vision and the field context, you are the engineer who turns concepts and requirements into working, production-grade software that operating companies depend on. This is a hands-on engineering role — you own the code, the data model, and the architecture, and you are accountable for what you ship all the way into production.

We are looking for a pragmatic builder who delivers working software, not a whiteboard architect. Priority build areas include fleet, procurement, project management, and safety.

Build Production Software

• Turn concepts and field requirements into working, production-grade applications, writing clean, maintainable full-stack code and taking real ownership of what you build;
• Move quickly, using AI-assisted development where it earns its place, without ever treating speed as an excuse for fragility; and
• Build across priority solution areas including fleet, procurement, project management, and safety.

Own the Architecture and Data Model

• Design the data models, APIs, and application architecture underneath each solution;
• Make the calls on how data is structured, how services talk to each other, and how a tool built for one operating company can generalize across many without collapsing under its own complexity.

Integrate with the Enterprise

• Build integrations and data pipelines against systems of record such as JD Edwards, construction and telematics platforms, and the Databricks lakehouse; and
• Ensure the tools you build read from and write to trusted enterprise data rather than to yet another disconnected copy.

Secure and Operate What You Ship

• Build to Quanta security standards, implementing authentication, two-factor, and role-based access control as a matter of course;
• Own reliability — when something breaks in production, you are the person who understands it and fixes it; and
• Build the logging, monitoring, and documentation that make that possible.

Harden and Make It Maintainable

• Take prototypes and rapidly built proofs of concept and turn them into software a team can maintain — version-controlled, documented, and structured so the next engineer can pick it up; and
• Treat knowledge that lives only in one person's head as a liability, and never build that way.

Partner with the Product Owner and the Field

• Work hand in glove with the product owner who sets the vision and carries the field relationships;
• Translate operational problems into sound technical designs and give honest feedback when an idea will not work or is not worth the cost; and
• Propose the simpler path when one exists — the partnership only works if you are candid.

• 7 or more years of professional software development experience, building and shipping applications that real users depend on;
• Strong full-stack ability — comfortable across a modern back end (Python strongly preferred) and a web front end, able to own a feature from database to interface;
• Solid command of relational databases and data modeling, with the judgment to design schemas that hold up as requirements grow;
• Experience designing and building REST APIs and integrating disparate systems, including third-party platforms with imperfect documentation;
• Disciplined engineering practice: fluent with Git-based version control, code review, testing, and thorough documentation as a default rather than an afterthought;
• A practical grasp of application security: authentication, two-factor, role-based access…