Principal Systems Architect-

IMDEX; Utah; On-site; USD 120,000 - 160,000; Full time

Job summary

IMDEX seeks a systems engineering leader to design and deliver integrated, system-level solutions that connect tools, sensing, data and decision platforms into coherent customer workflows. The role emphasizes building external and internal relationships across the Executive team and Strategic Business Units to align the roadmap with measurable outcomes.

From component outputs to customer-focused results, you will define requirements, architectures, and reusable patterns to accelerate pilots and

Qualifications

• Experience in systems engineering and cross-functional leadership.
• Ability to translate complex workflows into measurable outcomes.
• Strong stakeholder management across product, engineering and executive teams.

Responsibilities

• Map end-to-end customer workflows spanning tools, sensors, data acquisition/telemetry, analytics and decision points.
• Identify critical decision points, value drivers and constraints in complex operating environments.
• Translate workflow insights into clear system problem statements, user needs and measurable outcome hypotheses.
• Manage product-focused relationships with customer interfaces, Key Accounts, Commercial, Operations and Engineering.
• Providing product support to customers.
• Analyzing and monitoring products offered by competitors.

Job description

Design and deliver integrated, system-level solutions that connect IMDEX tools, sensing, data and decision platforms into coherent customer workflows, turning complex customer environments into repeatable, scalable solutions that deliver measurable outcomes. The role demands the ability to build key external and internal relationships and drive alignment across customer workflows, product development, engineering, the Executive team, and IMDEX's Strategic Business Units. The position will play an important part in IMDEX's transformation from a component to a system-level organization and from technology outputs to customer-focused outcomes. It requires a strong command of industry dynamics and competitive landscape to inform and align with the broader IMDEX product roadmap.

ACCOUNTABILITIES & EXPECTED OUTCOMES

Accountabilities

• Map end-to-end customer workflows spanning tools, sensors, data acquisition/telemetry, analytics and decision points.
• Identify critical decision points, value drivers and constraints in complex operating environments.
• Translate workflow insights into clear system problem statements, user needs and measurable outcome hypotheses.
• Manage product-focused relationships, such as customer interfaces, Key Accounts, Commercial, Operations and Engineering in accordance with the Product Operating Model.
• Providing product support to customers.
• Analyzing and monitoring products offered by competitors.

Expected Outcomes

• Documented workflow maps and stakeholder-aligned problem framing for priority use cases.
• Clear articulation of decision points and value drivers that informs solution prioritization and pilot selection.
• System-level outcome measures defined (e.g., time-to-decision, productivity, cost outcomes) and agreed for selected pilots.
• Improved alignment across Product, Engineering and customer stakeholders on what success looks like at a system level.
• Reusable workflow artefacts and narratives that can be applied across enterprise customers and regions.

Accountabilities

• Define system-level requirements including integration, interfaces, data flows, latency, performance and reliability.
• Design and validate integrated solutions across hardware, firmware, software applications, data platforms and analytics.
• Define interfaces and interoperability approaches that connect IMDEX components into coherent systems.
• Surface portfolio gaps, overlaps and integration priorities to inform architecture and investment decisions.
• Maintain a system-level view (e.g., block diagrams, workflow maps) to align stakeholders and guide design trade-offs.

Expected Outcomes

• Agreed system requirements and interface definitions enabling effective cross-team delivery.
• Validated solution architectures spanning tools, sensing, software and data platforms.
• Product development, system-level roadmap and plan/budget are prepared and communicated to relevant stakeholders. Product roadmap, priorities, decisions and trade-off rationale are kept visible and current in agreed systems of record.
• Reduced integration rework and clearer ownership across teams through early system-level definition.
• Repeatable integration patterns and reference architectures that can be applied across multiple customer workflows.

Accountabilities

• Support selected customer pilots and enterprise use cases, focusing on value validation rather than delivery volume.
• Partner with Product and Engineering to translate pilot learnings into roadmap, architecture and solution pattern decisions.
• Design pilot measurement approaches and capture evidence of outcome improvement (time, productivity, cost, risk).
• Contribute to development of repeatable solution constructs and delivery playbooks over time.

Expected Outcomes

• Successful delivery of targeted pilots with clearly reported value outcomes and lessons learned.
• Evidence-based recommendations feeding into product roadmap and platform architecture decisions.
• Growing library of repeatable solution patterns, reference implementations and internal guidance.
• Improved repeatability and scalability of integrated offerings (reduced bespoke rework across deployments).
• Stronger customer-facing narrative of system-level value from integrated IMDEX technologies (not isolated components).
• Convert customer outcomes into Product requirements, communicated to Engineering and used in the build.

Cross-functional leadership & stakeholder engagement

Accountabilities

• Work closely with Product and Engineering leaders and teams across tools, sensing, software and data to align on integrated system outcomes.
• Engage directly with enterprise customers to understand workflows and validate proposed solutions and outcomes.
• Operate as connective tissue across the portfolio, influencing architecture and prioritization without becoming reactive sales support.
• Communicate complex system concepts clearly through artefacts, narratives and decision-ready recommendations.
• Provide technical mentorship and thought leadership on systems engineering practices across relevant teams.

Expected Outcomes

• Improved cross-team alignment and decision velocity on integrated system architectures and priorities.
• Stronger engagement with enterprise customers on workflow and system-level challenges, leading to higher-quality pilots and designs.
• Clear internal positioning of the capability as system-level value creation.
• High-quality system artefacts that support stakeholder communication, governance and repeatability.
• Improved internal capability maturity through mentorship and consistent systems engineering practices.

LEADERSHIP AND PEOPLE

• Regularly challenges peers or superiors when the situation arises. Discussing the consequences of unacceptable behavior and offering