We show our work
Every conclusion REAP reaches links to the exact command output that supports it. We hold ourselves to the same standard: decisions come with the evidence, and “I think” is followed by “here is why.”
Careers
Build the layer that proves the network is healthy.
REAP is a small, venture-backed team in San Jose, California, whose founders built switching and data-center platforms at Cisco (opens in a new tab), Juniper (opens in a new tab) and Pensando (opens in a new tab) and hold 32 granted US patents between them. We are hiring across engineering, solutions engineering and go-to-market.
How we work
Evidence over opinion, in the product and in the company
Safety is the product
Agents that touch production networks earn trust one bounded step at a time. Guardrails, evaluations and audit trails are not features we add later; they are how the platform is built.
Design partners are in the room
Design partners shape the roadmap in weekly reviews. Engineers join pilots, watch investigations run on real estates and hear what a senior network engineer says when the answer is wrong.
Small team, real scope
Ownership of a whole problem (a connector, an agent, a segment of the market) rather than a slice of a ticket queue. Ship, measure, revise.
Where we hire
Teams and locations
| Team | What the work is | Where |
|---|---|---|
| Engineering | Reasoning engine and agent harness, collectors and connectors (CLI, SNMP, syslog, gNMI (opens in a new tab)), knowledge graph, evaluations, platform services | San Jose · remote (U.S.) |
| Solutions engineering | Pilots from week 0 to the business review: discovery, deployment, incident replays, findings reports, customer training | San Jose · U.S. regions |
| Go-to-market | Enterprise sales, partner programs, analyst relations, content grounded in evidence | U.S. remote |
| Security and trust | Security engineering, compliance program (SOC 2 (opens in a new tab)), customer security reviews | San Jose · remote (U.S.) |
Open roles are posted on the REAP LinkedIn page (opens in a new tab). If you do not see your role, introduce yourself anyway; we read every note.
What to expect
The process
- Introduction. A short note through the contact form or LinkedIn (opens in a new tab), with what you have built and what you want to build next.
- Conversation. Thirty minutes with a founder or the hiring lead about the role, the team and your questions.
- Working session. A practical exercise close to the real work (reasoning through an incident, designing a connector, scoping a pilot) with the team, not alone.
- References and offer. We move quickly and tell you where you stand at every step.
Principles
What we ask of each other
Say the true thing
Design targets are targets until measured. A demo is not a customer result. We label evidence levels internally and externally.
Respect the operator
Network engineers carry the pager. The product exists to give them evidence at 2 a.m., not to replace their judgment.
Never disparage
Competitors, incumbents and the tools customers already run are described accurately and respectfully. REAP sits above them.
Introduce yourself.
Tell us what you have built, what you want to build, and which team fits. A person replies within two weeks.