Edge · Web · Mobile · Automation

Systems that actually work outside the demo.

A decade shipping computer vision into production, much of it converted and running on-camera and on-NPU for enterprise clients in Japan. Mobile, cloud and agent work across Asia, Europe and Africa alongside it.

{{ termText }} ⌘K
{{ statYears }}+ years shipping production systems
{{ statSystems }} systems shipped across six fields
{{ statRepos }}+ repositories contributed to, public and private
{{ statFps }} fps detection and tracking, on edge hardware
How I work

You get the number that flatters me and the one that doesn't.

One number without the other is a claim nobody can check, so each system reports the flattering framing and the unflattering one side by side and says which is fair to which measurement. The evidence below is what that discipline produced; it grows, the standard does not.

{{ pr.figure }} {{ pr.title }} {{ pr.body }}
{{ s.stage }} {{ s.name }}
{{ ch.label }}
{{ chainNote }} click a system for its numbers, decisions and limits
{{ detail.id }} {{ detail.label }} {{ detail.sub }} {{ detail.repoName }} {{ detail.metaLine }} {{ detail.status }}

{{ detail.oneLiner }}

metric baseline paired
{{ row.label }} {{ row.aVal }} {{ row.aLabel }} {{ row.bVal }} {{ row.bLabel }}
{{ s }}
{{ t.label }}
{{ n.glyph }} {{ n.body }}
About

I'm an engineer who takes systems from idea to production — and keeps them running.

Over the past decade I've shipped software for enterprise clients across Asia, Europe, and Africa: real-time vision systems on factory floors, encrypted mobile deployments, cloud pipelines, interactive 3D applications, and autonomous automation that runs businesses day to day. Seven of those years were edge AI for Japanese enterprise clients — models converted and shipped onto vendor NPUs and on-camera accelerators, where the toolchain turns out to be most of the work. Whatever the field, my specialty is the same: building things that actually work outside the demo.

Published research
5 documents
15 citations
3 h-index
Founder-level ownership As co-founder & CTO of a sports analytics startup, I've built everything from perception pipelines to cloud inference architecture — I think about your whole system, not just my ticket.
Production standards My systems run for enterprise clients in Japan, where reliability expectations are unforgiving. Clean, maintainable, monitored — not demos.
Clear communication I confirm scope precisely before work starts, flag risks while they are still cheap to fix, and deliver on the date I gave you.
Prior work

A decade of production systems I can't show you.

Most of my output belongs to the companies that paid for it — client deployments, proprietary architectures, internal tooling. I can say what the work was and which silicon it ran on, and nothing more specific than that. The repositories above exist because a claim nobody can check is worth very little, so the method is demonstrated on work I own outright.

{{ c.figure }} {{ c.label }}
{{ a.name }} {{ a.body }}
Shipped onto
{{ pf }}
Stack

What I reach for, and where it runs.

outlined in green = used in a repo above; click to open it
{{ g.name }}
{{ i.label }}
Experience

A decade of production systems.

employers withheld · the work is proprietary
{{ t.when }}
{{ t.role }} {{ t.tag }}
{{ tlDetail.when }} {{ tlDetail.role }} {{ tlDetail.org }}
{{ tlDetail.detail }}
{{ pt }}
Contact

Tell me what you're building — I'll respond with a concrete approach, not a template.

{{ n.label }}
{{ sendNote }}

Ahmed Mohsen E.

AI & Computer Vision Engineer
{{ bootLine }}
{{ introTag }} skip →
shown once {{ introPct }}
esc
{{ r.tag }} {{ r.label }} {{ r.hint }}