freehire launches on Product Hunt on 26 August.

Follow →

Senior Edge + Backend Software Engineer

Summary

Build and own an on-device agent and Python backend for an AI-driven connectivity intelligence platform, shipping resilient edge software and scalable data pipelines.

About the role

We’re building an autonomous site-level connectivity intelligence platform for enterprise environments. This role owns the

Loaction

New York, NY

Job Type

Full-time

Experience

5 - 10

Remote work policy

On-site

Visa sponsorship

No

Preferred Time Zone

About the role

We’re building an autonomous site-level connectivity intelligence platform for enterprise environments. This role owns the on-device agent and key parts of the device-facing middleware, and also contributes broadly to our Python backend as we scale from pilots to fleets.

You’re a “full-stack systems” engineer: comfortable shipping reliable software on edge devices and building clean backend services, APIs, and data pipelines in Python.

What You’ll Build

Device software (primary ownership)

  • Edge agent runtime on OpenWrt/Linux:
    • service lifecycle, watchdog, structured logging, resource controls
  • Telemetry & probes:
    • device health (CPU/mem/disk/uptime/temp where available)
    • network health (interfaces, IP, routes, gateway reachability, DNS config)
    • internet probes (ping/DNS/HTTPS timing, loss/latency/jitter derived)
    • private cellular telemetry: RSRP/RSRQ/SINR, RAT, band/channel, cell ID/PCI, attach/detach, SIM state
    • Wi‑Fi telemetry: passive scans (SSID/BSSID, RSSI, channel, band, density), link stats when associated (best‑effort)
  • Store‑and‑forward reliability
    • local spooling (SQLite or equivalent), bounded storage, backoff/retry, idempotent batching, backfill after outages
  • Evidence bundles + symptom events
    • snapshot capture on triggers, consistent schemas, versioning, compatibility discipline
  • Hardware abstraction layer to support multiple device SKUs over time

Middleware + backend (meaningful ownership)

  • Secure ingestion APIs (Python):
    • schema validation + versioning, compression, auth, rate limiting
  • Device registry & fleet health:
    • identity, capability discovery, last‑seen/heartbeat, data completeness scoring
  • Backend product primitives:
    • event processing, correlation inputs, incident objects, site‑level rollups
    • data models and query patterns supporting “evidence‑first” RCA
  • Ops tooling:
    • dashboards, ingest failure triage, replay tools, offline detection
  • Edge config delivery:
    • site profiles, enabled playbooks, cadence, feature flags

Responsibilities

  • Architect and implement the edge agent to be production‑grade (unattended, self‑healing, resilient to flaky power/backhaul).
  • Own devicecloud schemas and compatibility strategy.
  • Build and operate core Python backend services and data pipelines.
  • Establish testing and release discipline for edge + backend:
    • unit/integration tests, network fault injection, replayable fixtures
  • Drive security/reliability best practices:
    • per‑device identity, TLS everywhere, least privilege, safe upgrade path

Required Qualifications

  • Strong experience building production Python systems (services, APIs, workers).
  • Real‑world experience shipping software on Linux edge devices / routers / IoT gateways.
  • Strong networking fundamentals; can debug real failures quickly.
  • Experience with telemetry pipelines: batching, retries, idempotency, persistence, backpressure.
  • Operational mindset: observability, debugging, “you build it, you run it.”

Preferred / Nice‑to‑have

  • OpenWrt (procd, packaging, filesystem constraints, iptables/nftables).
  • Cellular: ModemManager, QMI/MBIM, AT commands, SIM/attach state.
  • Wi‑Fi: iw, nl80211 concepts, scan/link stats.
  • Backend infra: Postgres, Redis, queues/workers, time‑series/event storage.
  • AWS: deploying Python services, secure ingestion patterns, metrics/logging.
  • Device fleet security: keys/certs, enrollment, signed updates.

Culture & operating principles (internal clarity)

  • Ownership is real: if it breaks in the field, we fix it—fast—and we harden it so it doesn’t recur.
  • Bias to shipping: meaningful progress weekly; small PRs; tight feedback loops.
  • High standards on reliability: correctness > cleverness; explicit contracts; versioned schemas.
  • No “throw it over the wall”: edge + backend are one system; we optimize the whole loop.
  • Low ego, high velocity: debate the idea, not the person; be direct and respectful.

What Success Looks Like

  • 30+ day unattended stability on devices in real environments.
  • No data loss during outages (bounded spool + backfill works).
  • Ingestion is resilient and idempotent; device registry and fleet health are reliable.
  • Evidence bundles and symptom events are consistent and useful to downstream RCA.

About Eino

Eino is building the world’s first Connectivity Digital Twin—a deeply technical, AI‑driven simulation platform that models real‑world environments and their connectivity layers.

We solve hard, physical‑world problems using advanced AI, high‑performance backend systems, geometric computation, and rich large‑scale data.

Every engineer at Eino works on highly challenging problems and collaborates with a team of exceptional, experienced builders.

We are well‑funded by strong investors, have real customers, and a clear roadmap to reshape how the world understands connectivity.

This is a rare opportunity for a hungry, entrepreneurial engineer to join a rocket‑ship Seed/Series A startup at the ground level, help architect the core backend, and grow into the owner of critical product infrastructure.

See also

Tailor your CV for this role?

We couldn't check your fit for this role — add a CV to your profile to see it next time.

A new version of freehire is available