No open roles. Still worth reading
There is nothing to apply to on this page today and it is not going to pretend otherwise. What follows is what the work actually consists of, so that a speculative note from the right person arrives with something specific to aim at rather than a guess about what we might need.
No open roles listed right now
This page lists roles when there are roles, and there are none today. Nothing further down is a vacancy in disguise, and there is no talent pool to join. A speculative note is still read: send it through the contact form, say what you build, and point at something you have shipped that survived contact with real users.
The state of the company, put plainly
A candidate deciding whether to write to a company with no vacancy is really asking three questions. Here they are answered in the order they get asked.
Blue Mesh was built inside Netstratum Inc. and is being established as a separate company, with Netstratum now a customer, not a parent. No date is settled.
Deployments go private cloud, on-premises and fully air-gapped, the last as an appliance on NVIDIA DGX. A missing dependency means a site visit.
No headcount, office list, benefits table, salary band or equity story, and no hiring process beyond the contact form. None of it is settled enough to publish.
What you would actually be working on
Each line below describes the product rather than the workplace. That is on purpose: the product is checkable before you talk to anyone, and it is the part of the pitch that would still be true if everyone here were unpleasant.
Multi-agent orchestration
A Leader Agent decomposes a task and directs specialist sub-agents across systems the enterprise already runs, with no manual handoff between steps. The engineering problem is what happens on step four when step two was subtly wrong.
Voice that holds up on a phone line
Low-latency voice over SIP, running on models the customer hosts. The hardest live deployment is phone companionship for older adults: no app, hearing difficulty, long pauses that are not the end of a turn, and no second attempt at a first impression.
Deployment into environments that say no
Private cloud, on-premises, or fully air-gapped on an appliance. These constraints arrive at the start of a design rather than as a late request, which is a materially different and more interesting job than adding them afterward.
Governance as a feature, not a wrapper
Role-based access, encryption, an audit trail on every decision, and human checkpoints on the consequential steps. If you have ever watched a good model get rejected by a security review, this is the work that answers the review.
- About Blue Mesh Where the company came from, the four modules, and the boundary: what the platform deliberately does not do.
- Trust and security The deployment and governance constraints the engineering answers to, written for a customer's security reviewer.
- BM in a Box The strict end of the work: the whole platform as a shippable appliance with no path to the internet at all.
Nothing to apply to. A note is still read
Tell us what you build and where you think it fits, and point at something that shipped. The contact form reaches the team directly and for now that is the entire process. When a role opens, it appears on this page.