What we’re building

‍

We’re an early-stage company building software that helps enterprises measure, understand, and improve connectivity performance across complex environments. Our system combines edge software running on Linux-based devices with cloud services that ingest and process telemetry at scale.

‍

The role

‍

You’ll own critical parts of the edge agent (Linux/OpenWrt-class environment) and contribute meaningfully to our Python backend (APIs, ingestion services, and operational tooling). This is a high-ownership role for someone who loves shipping reliable systems that work in real-world conditions.

What you’ll do

• Build and maintain a production-grade edge agent (service lifecycle, watchdog behavior, structured logs, resource constraints).
• Implement telemetry collection and active probing focused on network and device health.
• Design reliable edge→cloud delivery (local buffering, retries, idempotent batching, backpressure).
• Build and extend Python backend services:
  • ingestion endpoints, validation, and versioned schemas
  • device registry / fleet health primitives
  • event processing and operational debugging tools
• Improve system observability and operability (metrics, dashboards, alerts, and field-debug workflows).
• Collaborate with product and engineering to translate real customer problems into shippable features.

What we’re looking for

‍

Required

• Strong experience building production systems in Python (services/APIs/workers).
• Experience shipping software on Linux-based edge devices (routers/gateways/IoT preferred).
• Solid networking fundamentals (routing, DNS, DHCP, NAT, common failure modes).
• A track record of building reliable pipelines (retries, persistence, idempotency, resilience).
• Comfort owning problems end-to-end and operating what you build.

Nice to have

• OpenWrt familiarity (or similar constrained Linux environments).
• Wi-Fi and/or cellular telemetry experience.
• Experience with Postgres/Redis/queues, cloud deployment, and security fundamentals for device fleets.

Startup culture & how we work

• High ownership: you’ll ship meaningful systems and see them used quickly.
• Speed with discipline: we move fast, but we don’t cut corners on reliability for production-facing code.
• Simple > clever: we prefer pragmatic, maintainable designs and clear interfaces.
• Direct communication: small team, low ego, high accountability.
• Customer reality: we build for messy environments—power interruptions, flaky networks, imperfect inputs.

Why join

• Work on a technically deep problem at the intersection of networking, edge systems, and backend.
• Make foundational architecture decisions early.
• Competitive compensation + meaningful equity (early-stage).

To apply: Send your resume / LinkedIn and a short note about a system you built that had to run reliably in the real world.

How to apply