Infrastructure Engineer

Why Plura

Every business that talks to customers at scale has the same problem. Calls go to voicemail, texts go unanswered, and the people who could fix it are already at capacity. Contact centers spend most of their budget on agent labor and still answer leads in hours when the standard is seconds.

Plura is an FCC-licensed carrier and an AI communications platform for voice, SMS and RCS. Our AI agents answer and place calls, run text conversations, and hand off to people only when a person is needed. Because we own the carrier layer, compliance is built into the network: STIR/SHAKEN attestation, real-time DNC screening, quiet-hours enforcement and carrier registration happen inside the platform, not in a third-party tool bolted on afterward.

We are a small team with a live product, real customers and a lot left to build. If you want your work to reach a phone in someone's hand within a week of shipping it, this is that kind of company.

About the role

You will own the infrastructure that runs Plura's voice and messaging platform: the environments our services deploy to, the pipelines that ship them, and the observability that tells us what is happening on a live call. When a customer's campaign places thousands of calls an hour, the systems you run are the reason it works.

This is a builder's role, not a ticket queue. You will set the standards for how we deploy, scale and watch the platform, and then build them.

How we work

• Remote-first across the US, with the sales team anchored in Las Vegas.
• Two-week sprints with a written ticket for every change and a clear owner for every outcome.
• Small team, wide scope. You will touch more of the product than a job title suggests.
• We use AI in our own work every day, from compliance review to code, and we expect you to.
• Direct communication, short meetings, decisions written down.

What you'll do

• Design and run the cloud infrastructure for real-time voice and messaging services: compute, networking, storage, and the edge pieces that carry media.
• Build and maintain CI/CD so that a merge to main becomes a safe, observable production deploy without a human babysitting it.
• Own observability end to end: metrics, logs, traces, alerting, and the dashboards on-call actually uses.
• Manage the telephony-adjacent infrastructure our carrier license depends on: interconnects, media servers, and the security posture around them.
• Run capacity planning and cost management for a platform whose load is spiky by nature.
• Lead incident response and the postmortems that make the next incident smaller.
• Handle secrets, access, backups and disaster recovery, and keep our SOC 2 controls true in practice.

What you'll work with

• Containers and orchestration, infrastructure as code, and a cloud provider you know well.
• Vercel for the web surfaces; managed Postgres; queues and streaming for the messaging pipeline.
• Voice infrastructure: SIP, RTP, WebRTC, and the network tuning real-time audio needs.
• CI/CD tooling, observability stacks, and the scripting to glue them together.

What you'll bring

• 5+ years running production infrastructure for a service people depend on around the clock.
• Strong infrastructure-as-code practice and real experience with container orchestration at scale.
• Networking depth: load balancing, DNS, TLS, VPCs, and the debugging skills to trace a packet.
• An observability mindset. You instrument first and guess second.
• Calm under an incident and rigorous after one.

Nice to have

• Telecom infrastructure: SBCs, media servers, carrier interconnects, or VoIP at scale.
• Experience supporting a SOC 2 or similar audit as the infrastructure owner.
• Cost optimization work on a spiky, usage-driven workload.