Software Engineer
MaiaEdge
Software Engineer
About MaiaEdge
MaiaEdge builds networking hardware that connects AI data centers and cloud infrastructure. Our flagship product, the PBC-2000 Path Border Controller, is purpose-built for private WAN automation — the backbone of AI infrastructure operators, colocation providers, and service providers.
We're an early-stage, well-funded startup based in Burlington, MA — small team, real product, real customers, and growing fast. Good people, good culture, and work that actually matters. If you want to build something that ships, you're in the right place.
The Role
We're hiring a Software Engineer to help build the cloud-side systems that keep our network devices configured, connected, and talking to each other correctly. You'll work alongside the engineer who owns our cloud-config API layer — the async communication system between our UI, our edge devices, and the cloud services that manage them, spanning device state and topology, real-time health and SLA processing, identity and auth, and our AWS-hosted cloud infrastructure.
Most of the day-to-day is a Go backend, but where you land on any given week depends on where the need is — concurrency and race conditions, database and event-stream design, integrations with cloud providers and third-party identity services, and sometimes work that spills into adjacent parts of the stack. You don't need to walk in knowing all of it; you need to walk in able to learn it fast.
You'll be one of our earlier engineering hires, which means real ownership, real visibility, real growth. No layers, no hand-holding, just good work with good people. We're a small team, so pitch in on whatever needs doing — no task too small if it moves things forward.
What You'll Do
- Build and maintain backend services in Go that manage device state, configuration, and network topology
- Work with protobuf-defined APIs connecting our UI, edge devices, and cloud services
- Reason about state consistency and concurrency — what happens when two things happen at once, or a device goes offline, returns stale data, or falls out of sync
- Work with the databases and event-streaming systems that back our real-time device and network data
- Integrate with third-party services — identity/auth providers like WorkOS, email, and other cloud APIs — and with AWS infrastructure more broadly
- Dig into an unfamiliar codebase, ask good questions, and get productive without needing everything explained twice
What We're Looking For
You need to think in systems — you notice edge cases, you ask what happens when something fails, you don't just describe the happy path.
- 0–5 years of experience building backend services or APIs (internships and co-ops count)
- Comfortable in at least one statically-typed or compiled language (Go, Java, C, Rust, or similar) — proof you can pick up a new one matters more than knowing Go specifically
- Some grounding in networking fundamentals, multi-threaded or concurrent programming, and databases — coursework counts, it doesn't have to be production experience
- Comfort working with cloud infrastructure (AWS or similar) and third-party APIs
- Experience designing or working on a non-trivial API — you can talk through the inputs, the state it managed, and what could go wrong
- A degree in Computer Science, Electrical/Computer Engineering, or equivalent hands-on experience
- A self-starter who wants to learn — you go find the answer before you wait to be told
Nice to Haves
- Exposure to distributed systems — protocol stacks, consensus, or just genuine curiosity about how packets get where they're going
- Experience with protobuf, gRPC, or other schema-defined API tooling
- Familiarity with AWS services (ECS, Lambda, API Gateway) or managed data stores (Postgres, Redis, or similar)
- Experience integrating identity/auth providers or other third-party APIs end-to-end (auth flows, retries, latency tradeoffs)
Reporting
You'll report directly to the VP of Engineering and work day-to-day alongside the engineer who owns the cloud-config platform.