systems integration · embedded · robotics · automation · digital twins

Systems integration, worked through in the open.

A systems-integration and technical-delivery lead working where hardware meets software. I write about the engineering, and I'm building a cyber-physical systems project in the open, about how autonomous systems detect their own faults and fail safely.

Engineering writing · open build logs · async-first.
Andrew Michelis
Andrew Michelis · Based in Athens · Working across Europe
SYS Readiness Check · Sample Result
44
Unstable
Score: 44 out of 100
Structure & Interfaces
25
Validation & Readiness
38
Definition Clarity
50
Change / Risk Exposure
50
Execution Control
58
Structure & Interfaces — Fragile Validation — Fragile
Take your own check →

What I work on

Where hardware meets software

Systems integration & delivery

The seams between subsystems, teams, and disciplines, where integration risk hides. Requirements framing, interface ownership, readiness, and getting complex programs to a validated state.

Embedded, robotics & automation

Embedded systems, sensing and actuation, ADAS and perception, industrial automation, and the control and coordination problems of embodied systems.

Digital twins & cyber-physical systems

Modelling physical assets, telemetry and edge compute, sim-to-real, and the fidelity problem of keeping a digital model honest to the hardware.

Building in the open

Autonomy Health & Integrity

Selected writing

All writing →

Why integration milestones fail

What actually breaks at the seams between subsystems, and what to check before a milestone.

Read →

Validation gaps: “we tested it” is not “it works”

The difference between testing activity and actual evidence of readiness.

Read →

Interface ambiguity: the silent killer

Why interfaces go unowned, and the structural reasons no team sees the boundary.

Read →

Diagnostic tools & sample work

Async · no call required

Alongside the writing, I keep a small set of diagnostic tools open. No pitch and no funnel: if a milestone is looming and a structured outside read would help, they are here, entirely async. Below is a redacted look at what they produce.

Redacted Checker Result
44
Unstable
SYS Lane · [Redacted client]

Top risk clusters: System Structure & Interfaces (Fragile), Validation & Readiness (Fragile), Definition Clarity (Unstable).

See full sample →
Redacted 48h Review Memo

Executive Summary

The system is progressing under compressed timelines with critical interface assumptions undocumented. The primary risk is structural — ownership and validation criteria are implicit.

Interface ownership gap Missing readiness evidence
See full sample →
Try the SYS Readiness Check Request a 48h Structured Review See the full sample pack

What Others Say

Professional references & client feedback

About Andrew

Athens · Remote & onsite across Europe

Systems Integration & Technical Delivery Lead

I work at the boundary between hardware, software, and delivery, helping technical teams reduce execution risk when complexity outgrows clarity. My focus is the seams: unclear interfaces, fragile handoffs, incomplete validation, and progress that leans too heavily on a few key people.

Over a decade delivering complex hardware-plus-software programs, I work systems-first and artifact-led, turning ambiguous problems into executable plans with clear ownership and defensible readiness.

MSc, Systems Automation & Robotics (NTUA) · PMP® · Athens, Greece.

Domains

Embedded & hardware Mechatronics Automotive / ADAS Industrial automation Robotics & connected systems Digital twins Prototype-to-production

Currently

Building an open, simulation-first project on how autonomous systems detect their own sensor faults and fail safe: sensor fusion, a digital twin with drift detection, fault detection and isolation, and a safe-state layer. Writing up each milestone. Open to senior systems-integration and robotics / automation roles.

The tools and code: open-source work · github.com/andrewmichelis

Get in touch

Response within 1–2 business days