CMVISIONS

// About

Built by people who ship aircraft.

CMVisions was founded by Czar Carlo Balangue, an electronics engineer who moved into software the way most good embedded engineers do — by refusing to stop at the schematic.

A First Class MEng in electronics led to embedded software for unmanned aircraft, consumer electronics, and medical devices; then to startups, where the job description is “everything” — electronics, software, and mechanical in the same week. Today he leads systems and software engineering on a US eVTOL aircraft program, carrying flight software from first prototype toward a real production aircraft.

That range is the point of this consultancy. UAV problems don't arrive labeled “firmware” or “mechanical” — they arrive as “the aircraft does something we don't understand.” We're built to follow the problem wherever it goes.

CREDENTIALS

  • [✓]MEng Digital Communications & Electronics — First Class
  • [✓]Certified ScrumMaster (Scrum Alliance)
  • [✓]Secure Coding for Software Developers
  • [✓]Certified Security Testing Associate
  • [✓]TDD for Embedded C++

Employer & client names withheld — references on request.

// The team

Small crew, full coverage

Czar Carlo Balangue

FOUNDER / PRINCIPAL ENGINEER

Czar Carlo Balangue

LINKEDIN ↗
Lachezar Kozhuharov

DEVOPS / SOFTWARE ENGINEER

Lachezar Kozhuharov

LINKEDIN ↗
Dragostin Kozhuharov

SOFTWARE ENGINEER

Dragostin Kozhuharov

LINKEDIN ↗
Miles Gilbert

SOFTWARE ENGINEER

Miles Gilbert

LINKEDIN ↗
Anthony Rosbottom

TECHNICAL ARTIST

Anthony Rosbottom

LINKEDIN ↗
EE[ AWAITING VISUAL ]

PROFILE PENDING

Electronics Engineer

ME[ AWAITING VISUAL ]

PROFILE PENDING

Mechanical Engineer

// Operating principles

How we fly

Fly early, fly often

Simulation is a tool, not a verdict. We push toward real flight tests as early as the program allows, because hardware always has opinions the sim doesn't.

The whole system or nothing

Autopilot, payload, ground station, operator — a UAV is one system. We engineer across those boundaries instead of throwing problems over them.

Handover is the deliverable

A system your team can't own after we leave is a failed project, whatever the demo looked like. Documentation, tests, and knowledge transfer are in scope by default.