Careers
We are a small, remote-first team in the United States running carrier interconnects, number inventory, and AI voice traffic that other companies build products on.
What it is like to work on carrier infrastructure
Nobody thanks you when a call connects. That is the job.
Voice is an unusual thing to build on in 2026. The protocols are older than most of the people writing them, the failure modes are analog, and the feedback loop is a human being deciding, in about two seconds, whether to hang up. When something goes wrong you cannot read a stack trace; you read a packet capture, a carrier's signaling, and a pattern across thousands of calls.
Because we hold the interconnects ourselves, the fix is usually ours to make. A degrading route gets pulled the same day rather than escalated upstream and argued about for a week. That is the part people tell us they cannot get anywhere else: the problem stops at your desk, and so does the authority to solve it.
The traffic is real from your first week. AgentTech Dialer runs production insurance calling on these rails, and AI Voice Agents run on them at $0.10 a minute, so there is no staging environment where the stakes are pretend.
How the team works
Remote-first across the United States, small enough that the person who ships a change is the person who explains it.
- Remote-first, US-based. The team works from wherever they are in the United States. Carrier and customer work runs on US business hours, and network coverage runs around the clock.
- Written before scheduled. Decisions land in writing so someone three time zones away can pick them up without a meeting. Calls happen when the writing is not enough.
- Whole surfaces, not tickets. The surface area is wide: signaling, routing, numbers, messaging, recording, billing records. You own a piece of it end to end rather than a slice of someone else's backlog.
- Customers reach engineers. Platform customers get a shared channel with the people who run the routes. That means your work is visible, and so are the questions about it.
- Coverage is shared. Production voice does not stop at 6pm, so being on call is part of the team's rotation rather than one person's permanent problem.
Open roles
There is no application portal. Email us and a person reads it.
Voice Network Engineer
SIP signaling, media path, and route quality across our own interconnects. You will read packet captures, tune codecs and jitter for machine listeners, and pull bad carrier paths before customers notice.
Apply by emailCarrier Relations Manager
Interconnect agreements, rate negotiation, quality disputes settled with CDRs and traces, and capacity planning. The escalation path ends with you rather than moving one layer up.
Apply by emailPlatform Engineer
The API and control plane customers integrate against: number provisioning, programmable routing, recording pipelines, CDR export, and the sub-account model platforms bill from.
Apply by emailSolutions Engineer
Scope a platform's traffic, price it against the rate card, design the routing and porting plan, run the test calls, and stay on through cutover.
Apply by emailNOC Engineer
Live traffic, per-route answer-seizure and post-dial delay, carrier health, failover behavior, and incident updates that go out while the incident is still open.
Apply by emailHow to apply
Send a resume and a few sentences about what you have run in production to contact@solvedtele.com, with the role in the subject line. Applications go by email; there is no portal, no account to create, and no timed assessment. If none of the roles above fit but you have worked on voice at scale, write anyway and say what you would want to own.
FAQs
Applying here
How do I apply?
By email. Send a resume and a short note to contact@solvedtele.com with the role name in the subject line. There is no application portal on this site.
Are these roles remote?
Yes. The team is remote-first and based in the United States. Carrier and customer work runs on US business hours, and coverage for production traffic is shared across the team.
Do I need telephony experience?
For the network and carrier roles, yes: SIP, RTP, and the way carriers actually behave are hard to pick up on the job. For platform and solutions roles, strong systems work plus real curiosity about the phone network is enough. Say which one you are in your note.
What happens after I send the email?
A person on the team reads it. If there is a fit, the first conversation covers what you have run in production, what you want to own here, and compensation, so nobody spends four rounds finding out the range does not work.
Something else? Contact us
Tell us what you would want to own.
Resume and a few sentences to contact@solvedtele.com. That is the whole process to start.