System Engineer - Solution Integrations

Responsibilities

Own technical readiness across DaaS and partner application integrations.

Create reference architectures, integration diagrams, data flow views, deployment patterns, validation plans, and technical readiness checklists.

Define the technical baseline for secure data acquisition, buffering, monitoring, cloud processing, customer delivery, and steady state support.

• Identify integration gaps, network constraints, cybersecurity requirements, vendor dependencies, and operational risks before PoCs or pilots begin.

Cybersecurity and OT Readiness

• Create reusable cybersecurity and OT evidence packages for customer IT and OT reviews.
• Maintain standard topology diagrams, data flow diagrams, firewall rule templates, DMZ, VLAN, VPN, and routing patterns, identity and access assumptions, logging evidence, and remote access patterns.
• Support customer cybersecurity, MoC, and OT approval processes with clear technical documentation and repeatable review artifacts.
• Ensure integration patterns account for segmentation, auditability, hardening, patching, remote access, change control, and customer approval expectations.

Data Standards and Assurance

• Define standards for source to target data assurance, data mapping, customer naming conventions, unit handling, latency, completeness, frequency, validity, and source versus target comparison.
• Define how data quality signals are monitored, surfaced, alerted, and acted on across internal teams and customer facing workflows.
• Create reusable templates for customer standards management, data mapping, endpoint setup, and delivery validation.

Pre PoC Validation and Technical Gates

• Define pre PoC validation gates for customer and partner opportunities.
• Validate that required systems, data sources, endpoints, access paths, network assumptions, and support expectations are understood before delivery begins.
• Create repeatable technical validation plans for PoCs, pilots, partner integrations, and production deployments.
• Develop repeatable validation procedures, troubleshooting methodologies, and diagnostic playbooks that improve deployment success, reduce integration risk, and accelerate issue resolution.
• Provide clear go or no go input when technical readiness is incomplete or customer commitments create delivery risk.

Vendor and Partner Coordination

• Work with vendors and partner engineering teams to define integration responsibilities, data handoffs, technical boundaries, support expectations, and escalation paths.
• Define how partner platforms fit into the NOV service wrapper for industrial data acquisition, data delivery, video, file workflows, operational communications, analytics, and customer endpoints.
• Translate partner capabilities and constraints into practical implementation plans for NOV teams and customer facing stakeholders.
• Track vendor readiness risks and make unresolved dependencies visible early.
• Help turn recurring partner integration patterns into reusable templates and documented standards.

Edge to Cloud Flow and Customer Delivery

• Support architecture and readiness for data movement from edge environments into cloud services, platform APIs, customer applications, partner systems, or external delivery endpoints.
• Validate end to end data flows, connectivity, access, authentication, security, monitoring, and operational handoff requirements across edge systems, networks, cloud services, APIs, partner platforms, and customer environments.
• Lead technical investigations and troubleshooting activities across edge, network, cloud, partner, and customer environments to identify and resolve integration, connectivity, deployment, and data quality issues before and during customer delivery.
• Partner with product, engineering, operations, implementation, support, SRE, cybersecurity, and customer facing teams to make deployments repeatable and supportable.
• Reduce one off delivery by documenting common integration patterns, technical assumptions, and deployment requirements.
• Drive technical improvements that reduce dual stack complexity, manual mapping, custom connector work, and one off deployment risk.

Technical Documentation and Governance

• Maintain integration documentation, readiness checklists, technical decision records, and reusable implementation templates.
• Define standards for what technical evidence is required before customer or partner execution begins.
• Turn lessons from PoCs, pilots, and partner deployments into improved architecture patterns, validation gates, and implementation guidance.
• Maintain reusable artifacts for customer reviews, internal readiness checks, partner onboarding, and steady state support.