I’m Joshua Belke, a Senior Full Stack Developer at Magnetism Labs. I build end-to-end products where latency, reliability, and operator experience matter—from AI-powered applications and autonomous-system tooling to transaction-heavy commerce platforms.
My sweet spot is turning an ambitious idea into an operational system: product architecture, interfaces, APIs, data, infrastructure, and the last mile to production.
| Focus | What that means in practice |
|---|---|
| Applied AI | Retrieval, vector data, model-integrated workflows, and practical AI products built around real users and real data |
| Drones & mission systems | TAK/C2 integrations, geospatial interfaces, UAS symbology, telemetry, and 2D/3D operational visualization |
| High-throughput platforms | Concurrent services, fast APIs, resilient data movement, caching, observability, and systems designed for sustained load |
| Ecommerce | Marketplaces, transaction flows, platform integrations, and scalable customer experiences from storefront to fulfillment |
| Environment | Focus | |
|---|---|---|
| 2020 | NATO Innovation Hub | Full-stack delivery for defense innovation and operational technology |
| 2018 | DevaCurl | Ecommerce and digital platform engineering |
| 2014 | United Rentals | Enterprise applications and transaction-intensive systems |
Across those environments, I learned to move between product thinking and systems thinking: understand the mission, make the tradeoffs explicit, and leave behind software that can be operated—not just demonstrated.
|
NATO and MIL-STD-2525 symbology as a service for TAK, C2/C4ISR, UAS displays, GIS, simulation, and 3D engines.
|
A Rust wrapper around rsync for reliable gigabyte-scale synchronization, with a focus on simple operation and efficient data movement.
|
|
A multi-node vector database starter for natural-language interrogation of datasets, with ready-to-use API collections.
|
I care about the details that make software usable in the real world: compatibility, deployment, instrumentation, failure modes, and clear documentation.
|
| Principle | In practice |
|---|---|
| Own the whole path | Move comfortably from user workflow and interface design through services, data, infrastructure, and release |
| Measure the hard parts | Benchmark latency and throughput, instrument production behavior, and optimize from evidence |
| Design for operations | Treat deployment, observability, failure recovery, security, and documentation as product features |
| Respect the domain | Build around standards, operator constraints, and integration boundaries instead of forcing generic abstractions |
My work has crossed defense innovation, autonomous systems, direct-to-consumer commerce, and large-enterprise platforms. The domain changes; the engineering standard does not: understand the operation, make the system observable, and ship something people can depend on.
I’m open to senior individual-contributor work, architecture leadership, and ambitious collaborations involving AI, autonomous systems, high-throughput platforms, or commerce. If that sounds like your problem space, start a conversation.