Data Center Constructability Engineer

About the Role

Armada is hiring a Data Center Constructability Engineer to support the Galleon and Leviathan product lines — a brand-new capability for the company. As we scale Modular Data Center (MDC) deployments across a growing number of sites and geographies, we need someone who can own the constructability thread that runs from early site due diligence and design review through pre-construction planning, fabrication, installation, and commissioning, and make sure what gets designed can actually be built, on schedule, everywhere we operate.

You will review Leviathan/Galleon MDC and site designs for buildability, validate deployment methodologies (crane and access, sequencing, tolerances, and fit-up) before they're locked in, and build the standardized, repeatable construction playbooks that turn site execution into a repeatable process instead of a one-off plan per site. You'll also be the constructability point of contact linking Armada's product and engineering teams with fabricators, general contractors, and local delivery partners, supporting pre-construction planning and reviewing design packages and shop drawings to make sure what's designed matches how it will actually be built in the field.

What You'll Do (Key Responsibilities)

• Constructability review & product feedback loop — Review Leviathan/Galleon MDC and site designs (civil, structural, architectural, mechanical, electrical, piping, controls, ICT, IT) at each stage gate and feed constructability input directly into product development — modularity, transport and lifting constraints, ISO container/skid interfaces, installation sequencing, and commissioning strategy — catching buildability issues while they are still cheap to fix, before they are locked into issued-for-construction drawings.

• Deployment methodology validation & site-specific risk assessment — Validate deployment methodologies for Leviathan across candidate and active sites worldwide (crane selection and access, laydown and site logistics, erection/installation sequencing, tolerances and fit-up), and own early constructability due diligence that flags site-specific vendor, access, or execution risk before it causes late-stage redesign or slips a deployment.

• Standardized, repeatable construction playbooks — Develop and maintain repeatable construction playbooks, sequencing plans, and methods of procedure for single-unit and campus-scale Leviathan deployments, turning site execution into a repeatable, SKU-like process instead of a one-off plan per site and region.

• Hands-on constructability analysis for new products & first-of-a-kind sites — Personally lead constructability analysis (crane/lift studies, transport and logistics modeling, installation sequencing) for new Armada products or site conditions where no vendor, GC, or prior-site precedent exists yet, establishing the buildability basis in-house before handing execution off to local contractors and fabricators.

• Pre-construction planning & cross-discipline coordination through execution — Act as the constructability point of contact linking Armada product engineering with civil, structural, architectural, mechanical, electrical, piping, controls, ICT, and IT disciplines, fabricators, and general contractors; support pre-construction planning (schedule, cost, logistics, procurement lead times) and review design packages and shop drawings for buildability, ensuring what is designed can actually be fabricated, transported, and installed as sequenced and on schedule.

• Constructability governance, documentation & readiness sign-off — Build and maintain constructability guidelines, buildability/site-readiness checklists, and review workflows by geography; track open constructability items and lessons learned across active sites; and provide the final constructability sign-off confirming a site's design and execution plan are buildable and ready to proceed to construction.

• Own the integration architecture across Armada’s systems landscape: define how systems connect, what data flows where, and how changes in one system propagate downstream.
• Map and maintain a clear picture of Armada’s full systems stack — data structures, APIs, field mappings, and integration dependencies.
• Monitor upstream vendor release notes and system changes; assess downstream impact before changes propagate; coordinate remediation across functions before issues surface in production.
• Manage integration sequencing: when multiple teams are building systems that integrate with each other, determine what goes in first, flag bridging risks, and prevent rework from parallel implementations.
• Define and govern integration patterns, including APIs, iPaaS, middleware, and data warehouse/lakehouse patterns.
• Evaluate build vs. buy decisions and integration approaches with a bias toward simplicity, scalability, and security.
• Partner with data and engineering teams to ensure trustworthy reporting and analytics with clean data definitions.

Orphan System Stewardship

• Serve as interim owner for any system that doesn’t have a clear functional home — including systems in transition as Armada scales (e.g., CLM, HRIS tools, and adjacent G&A tooling).
• Proactively identify orphan systems, stabilize them, and plan for handoff to a functional owner when one is in place.
• Anticipate near-term orphan systems tied to new implementations and hiring plans; ensure continuity of ownership through each transition.
• Ensure system design supports clean, auditable processes and reduces operational overhead for the functions that will eventually own them.

Cross-Functional Systems Coordination

• Run a regular cross-functional systems review: pull together system stakeholders across the organization to review roadmaps, active implementations, and integration dependencies — not to dictate, but to surface conflicts and drive alignment before they become rework.
• Facilitate trade-off conversations when system needs across functions conflict: help stakeholders understand the cost of their requirements on adjacent teams’ systems, and reach compromises that minimize aggregate work across the org.
• Serve as Armada’s internal authority on systems governance: establish and maintain company-wide standards for integration patterns, data quality, access controls, and change management — without owning or overriding what GTM and R&D manage directly.
• Partner with RevOps and R&D systems counterparts to ensure interoperability across the full company systems landscape, with clean definitions for shared core objects (customer, product, employee, asset, etc.).
• Own system-level compliance posture: role-based access, audit trails, segregation of duties, and data protection practices across all systems — including those managed by other functions.
• Support audits and future compliance readiness (e.g., SOC 2/SOX-aligned controls) as a company-wide function, regardless of which team owns a given system.

G&A and Core Business Systems

• Own the strategy, roadmap, and execution for Armada’s G&A systems ecosystem: Finance/ERP, HRIS/ATS, Legal, procurement, and adjacent business operations tools.
• Run these systems like a product: define outcomes, prioritize ruthlessly, and deliver measurable improvements in cycle time, data quality, and user experience.
• Manage vendor relationships, contract renewals, tool rationalization, and licensing strategy for owned systems.

Automation and Workflow Efficiency

• Identify and eliminate manual work through automation: workflows, orchestration, document processing, approvals, and self-service.
• Enable AI-assisted internal workflows (routing, summarization, exception handling, reconciliation support, employee self-service) with strong security and governance guardrails.

Operating Model and Governance

• Establish the operating model for systems work: intake, prioritization, documentation standards, testing, change management, training, and post-launch support.
• Partner with the VP of Business Operations on roadmap prioritization and cross-functional alignment.

AI Enablement

• Define Armada’s internal AI tech stack, ensuring interoperability across systems and alignment with company data architecture.
• Build and own an AI-first operating model: standardized tooling, workflows, and clear expectations for how teams leverage AI in daily work.