AI Software Engineer
Amphenol · Pennsylvania
Industrial vision, manufacturing ML, and internal AI tools.+ AI SOFTWARE ENGINEER · PENNSYLVANIA, US
I build systems that see, reason, and work.
From the first experiment to the last mile
of production.
Computer vision, language systems,
and production engineering.
01 / THE ENGINEER
I’m Shahab, an AI software engineer based in Pennsylvania. My work connects computer vision, language systems, and software delivery. I build research prototypes and tools used in production.
My Unity and XR background still shapes how I build: understand the environment, make interactions feel natural, and keep the system responsive.
Read my full resumeAmphenol · Pennsylvania
Industrial vision, manufacturing ML, and internal AI tools.Intact Financial · Hong Kong
Document intelligence, geospatial ML, and CI/CD.Molekiu · Hong Kong
OCR, GPU inference, edge models, and multilingual LLMs.The University of Hong Kong
Unity applications, spatial mapping, and a five-person research team.Hyr · Hong Kong
REST APIs, authentication, and backend performance.Applied Artificial Intelligence
The University of Hong Kong · 2022–2026
02 / SELECTED WORK
Explore ASCOTA, my computer vision pipeline for archaeological images, plus bank churn modeling and production AI systems.
EXPERIENCE / SYSTEMS IN PRACTICE
Inspect the architecture behind the work03 / THE LEARNING CIRCUIT
A small reinforcement learning experiment.
Train an agent in your browser and see
what it learns to value.
REWARD OBJECTIVE
Reach all four checkpoints with a penalty for each additional step.
Ready. Choose an objective and run a training session.
Tabular Q-learning in a simplified grid circuit. The neural network in the opening scene is a visual motif, not this agent’s model.
04 / BEYOND THE MODEL
A useful model needs a dependable system.
I work across the software and infrastructure
that make AI usable.
APIs, data models, and application logic that connect AI to the people using it.
Repeatable deployment, containerized tools, and cloud workflows that move work beyond a notebook.
Model execution tuned for the constraints of real devices, factory workflows, and latency.
Trace a request from API to retrieval to inference. Track latency, cost, and failure modes together.
Treat model quality as a release criterion, with regression datasets and repeatable checks before deployment.
Typed tools, bounded retries, durable jobs, and human review at consequential decision points.
Future engineering directions, alongside the shipped work above.