Avionics, embedded systems, and practical AI

I build software for machines that have to work in the real world.

My favorite problems live at the edge of code and hardware: flight software, navigation interfaces, computer vision, automation, and AI tools that make engineering work less messy.

  • Ada
  • C
  • Python
  • ARINC 429
  • RAG
  • OpenCV

What this site is really about

Good engineering is mostly making uncertainty smaller.

I like systems where the answer is not obvious at first. You have to read the old code, understand the interface, find the signal in the noise, and make the fix boring in the best possible way.

That thread runs through my avionics work, robotics project, manufacturing software, and AI tools: build a clear model, verify it, and leave the system easier to reason about than it was before.

Systems I keep coming back to

A quick reel of what I build.

Flight software, AI tooling, and robotics all ask for the same thing: make the system easier to trust.

Verify // Flight software 01

Correctness under pressure.

Flight software taught me to turn complex behavior into something testable.

  • Flight planning and navigation interfaces
  • Legacy Ada, automated tests, and verification

Selected work

A few projects that shaped how I think.

Avionics interface concept
RTX Collins Aerospace Ada · C · Python · ARINC 429

C-130T flight management modernization

My current work at Collins Aerospace is the kind of engineering I like: old code, real constraints, a lot of interface details, and a product that has to behave predictably.

  • Flight-plan and navigation data workflows
  • Legacy Ada, C, Python, and ARINC 429 interfaces
  • Verification work across normal, invalid, and failure paths
Robotics arm and autonomous platform concept
Software Lead OpenCV · Kalman · PySerial · Unity

Automated foosball table

I led the software side of a six-person build that turned a normal foosball table into a computer-vision and motion-control problem.

AI data and retrieval system concept
AI Systems BM25 · TF-IDF · Transformers · RAG

Retrieval-augmented generation pipeline

I built this to understand the parts of RAG that actually matter: retrieval quality, chunking, citation grounding, and where hallucinations sneak in.

Technical depth

How I work when the details matter.

A short version of the habits underneath the projects.

Flight Software

Start with the interface, then prove the behavior.

In avionics work, I care about the unglamorous things that decide whether a change is trustworthy: timing, shared resources, interface assumptions, and tests that cover failure cases.

01

Reverse-engineer enough of the legacy system to avoid shallow fixes.

02

Validate message handling against interface requirements, including failure behavior.

03

Leave behind automation, reviews, and clearer coordination points.

4.0

M.S.E. Artificial Intelligence GPA at the University of Pennsylvania

3.92

Rutgers double major GPA: Computer Science and Mechanical Engineering, Aerospace Concentration

10

OpenAI research tasks reviewing technical and analytical model behavior

National Merit

National Merit Scholar, Rutgers Presidential Scholar, Summa Cum Laude graduate

Contact

If the work has real constraints, I probably want to hear about it.

I’m especially interested in avionics, embedded systems, robotics, AI infrastructure, and tools that make engineering teams sharper.

hrcomazing@gmail.com GitHub

A short note with the context and constraints is enough to start.