Skip to content
Cenotian
Watercolor study of an industrial robot arm

USA, alternatively Europe

Head of Technical Qualification, Emerging Robotics

You test, tear down and decide when emerging robotics companies are ready for our clients' factories - and help them get there.

You own the emerging-robotics lane: building the qualification standard for startups whose products may be exceptional while their delivery record, certification, manufacturing controls and commercial discipline remain unproven. Your work separates a compelling concept from a product that can be built, accepted, serviced and trusted.

Context

Cenotian manages large automation programs for industrial end customers across the US and Europe. Technical Qualification Services (TQS) is the independent evidence layer behind supplier selection, financing and deployment.

Position overview

This is a builder's role with direct field accountability. You conduct qualifications personally, partner with founders and their technical and manufacturing teams, and turn the method into a paid service the market seeks out. Extensive travel to startup shop floors.

Reports to:
Head of Special Missions Group before launch; Co-founder / CEO after launch
Location:
USA, alternatively Europe

Key responsibilities

  1. 01

    Define the qualification standard

    • Build the startup-specific methodology in line with Cenotian's broader qualification architecture: hard gates, scoring dimensions, evidence standards, escalation rules, requalification triggers, reasons to decline.
    • Assess companies through the risks they create in a deployment: completion, acceptance, performance, integration, continuity, service.
    • Distinguish strong evidence from polished self-reporting, paid pilots from commercial deployments, serial readiness from a founder-supported demonstration.
    • Keep the method comparable across companies while preserving expert judgment for genuinely novel technology.
  2. 02

    Qualify the company, team and product

    • Assess founder execution, technical depth, knowledge concentration, hiring gaps, commercial traction, delivered-unit history, and the gap between pilots and repeat orders.
    • Inspect product architecture, bills of material, software dependencies, certification status, manufacturing controls, field reliability, and service evidence from the exact product generation proposed for deployment.
    • Test whether founders and technical leaders can explain limitations and failure modes without retreating into product narrative.
  3. 03

    Determine integration and deployment readiness

    • Define what an integrator or operator must provide before the product works in a live application: interfaces, safety systems, data infrastructure, operator workflows.
    • Set the application envelope, proof-of-concept design, FAT and SAT, acceptance criteria and support responsibilities.
    • Determine whether the deployment model repeats across customers, sites and geographies without the founders becoming the permanent integration team.
  4. 04

    Turn evidence into decisions

    • Produce concise qualification reports: what was observed, what was independently verified, what remains unproved, what Cenotian can rely on.
    • Give viable companies a prioritized readiness plan across BOM, sourcing, manufacturing flow, testing and deployment model - each recommendation tied to an operating or economic mechanism.
    • Sequence recommendations into an evidence roadmap toward larger work packages and pools of end-customer spend.
    • Defend inconvenient conclusions when founder charisma, investor reputation or strategic interest points the other way.
  5. 05

    Build a market-facing service

    • Turn the internal method into a paid service for robotics companies, enterprise operators, integrators, OEMs and capital providers: packages, pricing, turnaround, deliverables.
    • Build the Cenotian Validated designation as a difficult, credible signal of integration readiness.
    • Win the first mandates personally. Protect qualification independence from commercial pressure; make rejection private, specific and useful while the external standard stays uncompromised.
  6. 06

    Place qualified companies into enterprise programs

    • Work with Value Engineering to match qualified products to funded work packages, define evidence gates and acceptance criteria for paid proofs of concept, and support shortlisting and award.
    • Follow products through pilot, acceptance and rollout so field outcomes improve future qualification decisions. The end customer retains selection and award authority.
  7. 07

    Build the evidence system and team

    • Create the ontology, scorecards, versioned deployment records, and monitoring and requalification triggers; use AI tooling to accelerate review without delegating judgment.
    • Recruit and calibrate technical qualification engineers and a specialist partner network; own capacity, delivery cost, margin and quality - and make the second qualification faster and more consistent than the first.

You'll know it's working when

Qualification conclusions change real admission, sourcing, financing, pilot and deployment decisions.

Strong technology with weak delivery infrastructure gets precise conditions and an improvement plan rather than unearned approval.

Enterprise buyers and integrators trust the Cenotian conclusion even when it is negative, and strong startups seek out the designation.

Candidate profile

What we require

Personal standard

Background paths

  • 01End-to-end product leader of a high-growth robotics platform

  • 02Robotics founder who cracked manufacturing

  • 03Robotics engineer turned venture investor

Organizational context

You work most closely with the CEO, your qualification engineers and specialist partners, Special Missions Group, Finance and Underwriting, Commercial, Enterprise Value Engineering, and Data and Engineering.

Apply for this role

Up to 2000 characters.