• Lead UI architecture and design decisions for web and responsive applications. • Define UI standards, best practices, and reusable component libraries. • Review code, enforce quality standards, and mentor UI developers. • Guide adoption of modern UI frameworks and design systems. • Design and develop complex, scalable, and responsive UI solutions. • Build reusable UI components using Angular / React / Vue and modern JavaScript/TypeScript. • Integrate UI with backend services via REST APIs and microservices. • Optimize applications for performance, security, and cross browser compatibility. • Partner with UX/UI designers to translate wireframes and prototypes into high quality implementations. • Work closely with backend engineers, architects, and DevOps teams. • Participate in Agile ceremonies (PI planning, sprint planning, reviews, retrospectives). • Ensure UI compliance with accessibility standards (WCAG / ADA). • Enforce secure coding practices and enterprise UI standards. • Support automated testing (unit, integration, UI automation).

• Serve as an RTX Ventures technical partner, providing insight into emerging technologies, producibility, and factory-centric application opportunities. • Support trade studies by analyzing technical options, assessing risks, and presenting recommendations to stakeholders. • Lead development, tracking, and reporting of Connected Factory metrics, including automation KPIs, Control Tower insights, and digital performance dashboards. • Support factory automation initiatives, including evaluation of automation opportunities, technology readiness, and deployment coordination with site teams. • Lead the Industry 4.0 (I4.0) Council and support the Quality Management System (QMS) Council, focusing on cross-BU QMS harmonization and integration into standard operating processes. • Act as a strategic partner for Producibility initiatives, ensuring manufacturability considerations are integrated into design, development, and scaling processes. • Provide MBDMI (Model-Based Definition / Model-Based Inspection) support to mature digital product lifecycle capabilities. • Collaborate across functional and site teams to drive best practice sharing, digital maturity acceleration, and continuous improvement in technical excellence. • Ensure alignment between enterprise initiatives, business unit strategies, and site-level deployment activities. • This position will require travel to various manufacturing sites.

• Rapid Prototyping & Innovation: Act as a specialized engineer who identifies interesting product opportunities. • Strategic Technical Leadership: Take ownership of responsibilities beyond coding, including managing complex technical projects. • Direct Collaboration with Leadership: Work directly with the CTO to solve high-level problems. • System Mastery & Evolution: Develop a deep understanding of our existing system. • Customer & External Engagement: Engage with users to understand their deep technical needs.

• Owning the vNode technical execution: Drive the architecture for how vNode wraps containerd, integrates with the kubelet, and exposes safe isolation primitives. You will set the bar for what ships, what gets deferred, and what gets redesigned. • Going deep on container runtimes and isolation: Lead the work where vNode meets containerd, Kata Containers, gVisor, runc, and the kernel. You will be the person who can explain (and improve) exactly what happens between a Pod spec and a process running under a constrained user namespace with a tight seccomp profile. • Shipping the kubelet integration surface: Own how vNode plugs into the node lifecycle: CRI, kubelet device plugins, cgroups v2, eviction, and the rough edges between Kubernetes' node model and a runtime that does not assume one tenant per node. • Raising the engineering bar: Run technical design reviews, set the pattern for testing isolation guarantees, and mentor the engineers shipping alongside you. You are not a people manager, but you are the engineer the team copies. • Being Customer Zero for vNode: Run vNode against vCluster Platform tenant clusters internally before customers see it. You will close the loop between what AI Cloud operators need and what vNode actually does in production. • Representing vNode externally: Contribute upstream where it matters (containerd, runc, Kubernetes SIG-Node), write the technical posts that explain why namespace-based isolation is the right answer, and represent vCluster Labs at KubeCon-class venues when the timing is right.