Wireless Systems Architect

Our custom ASIC is returning from fabrication. Our commercial protocol stack spans a novel MAC and PHY architecture, multi-hop mesh routing, and location tracking. The tech is proven, the TAM is gargantuan, and the founders have signed LOIs and conditional orders worth several billion dollars in ARR across applications ranging from supply chain logistics to laptop and cattle tracking.

• Bachelor’s degree in Computer Science, Computer Engineering, Electrical Engineering, or equivalent \n

• Deep wireless protocol systems experience: has owned specifications from concept through implementation handoff in a commercial wireless product spanning multiple protocol layers \n

• MAC and PHY layer fluency across the full stack: can reason about waveform behavior, frame structure, MAC scheduling, and cloud protocol logic \n

• Wireless communications background: understands duty cycle constraints, link budgets, and the specific failure modes of low-power wide-area wireless, * Quantitative systems analysis: comfortable with link budget calculations, capacity modeling, and the kind of back-of-envelope physics that validates whether a system concept is achievable, * Experience working at the interface between system design and firmware or protocol implementation: has been on both sides of a specification handoff and understands what makes it work or fail

You will own the translation layer between system-level architecture and working implementation. The system architecture here is deep, fast-moving, and technically demanding, spanning waveform design, novel MAC and PHY protocols, multi-hop mesh routing, GPS processing algorithms, and the software stack from endpoint firmware through cloud.

\n

\n

What You’ll Do:

\n

\n \n

• Translating system-level concepts into implementable specs across endpoint firmware, network-side software, and cloud protocol logic \n

• Architecture review: evaluating proposed system designs for implementability, identifying constraints and failure modes before they reach the implementation teams \n

• Interface definition: owning the specification of boundaries between protocol layers and between teams \n

• Simulation environment requirements: utilizing AI and defining what the simulation environment needs to validate against feature specifications \n

• System-level link budget and capacity analysis \n

\n

\n