Enterprise Scale
I design and support systems for enterprise environments exceeding 100,000 devices, where reliability, observability, lifecycle management, and repeatable automation matter as much as the first successful deploy.
About
I build systems for large enterprise environments and practical tools for the real world. The common thread is simple: understand the problem deeply, make the workflow cleaner, and leave something useful behind.
I'm Jonathon Poe, a senior systems engineer and enterprise mobility architect with a background that spans mobile development, automation, cloud platforms, full stack software, and AI-assisted tooling. I spend a lot of time where software meets operational reality: device fleets, APIs, managed platforms, diagnostics, deployment workflows, and the small details that decide whether a system is pleasant or painful to run.
Professionally, I work at enterprise scale, designing solutions for environments with more than 100,000 devices. That kind of scale has shaped how I think. Good engineering is not just code that works once. It is maintainable behavior, clear failure modes, automation where humans should not be doing repetitive work, and enough documentation that the next person can move faster.
Away from formal work, I am still usually building something. Sometimes that is a mobile app, an automation workflow, an LLM experiment, a CAD model, or a 3D printed part. Sometimes it is a project sparked by curiosity with my son Alexander nearby, asking the kind of questions that make you look at familiar things differently. That is the best version of engineering to me: practical, curious, and connected to real life.
I design and support systems for enterprise environments exceeding 100,000 devices, where reliability, observability, lifecycle management, and repeatable automation matter as much as the first successful deploy.
My work does not stop at screens and APIs. I build automation systems, mobile tools, CAD models, hardware projects, and 3D printed parts that solve practical problems in the physical world.
Many personal projects begin with a simple question, a rough sketch, or something my son Alexander and I can learn from together. Engineering is my profession, but building is also how I relax and explore.
The Full Mobile Stack
One interview question I get often is some version of: how can one person genuinely specialize across web, native mobile, and mobile device management? It is a fair question. Most careers force those lanes apart. Mine kept pulling them together.
I am comfortable calling myself a unicorn in that space because I have lived the full loop: building the software users touch, understanding the native platforms it runs on, and managing the enterprise fleets that deploy, secure, support, and measure it. That range lets me see problems from more than one seat at the table, which is often where the real solution shows up.
The portals, dashboards, APIs, data flows, and automation surfaces that support mobile operations.
Android and iOS applications, platform behavior, device capabilities, diagnostics, and field workflows.
MDM policy, enrollment, compliance, deployment, app lifecycle, fleet visibility, and enterprise support reality.