Senior Backend 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 design and build the services behind Plura's AI voice and messaging platform: the real-time paths that carry a live call, the messaging pipelines that submit, track and bill every SMS and RCS segment, and the APIs the product and our customers' systems call. The work sits where telephony, data and product meet, and you will own it end to end.

This is a senior role. You will make architecture calls, set standards for the engineers around you, and be trusted with the parts of the system where a bug costs a customer a conversation.

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

• Build and operate the services that place, receive and route calls on Plura's own carrier network, with latency budgets measured in milliseconds.
• Design the messaging pipeline: outbound and inbound SMS, MMS and RCS, delivery receipts, fallback handling, and per-segment usage records that feed billing.
• Own the platform APIs, from workflow execution to usage reporting, with versioning, idempotency and rate limits done properly.
• Integrate carrier and registry systems: 10DLC and toll-free registration through The Campaign Registry, RCS agent registration through our RCS provider, and the FCC-side records our carrier license requires.
• Model usage and billing data so that what a customer sees in their usage screen reconciles to the cent with what we are charged.
• Write the runbooks, dashboards and alerts that let the team sleep.
• Review code, mentor engineers and raise the bar on testing and observability.

What you'll work with

• TypeScript across the product surface; Node.js services; Postgres as the system of record.
• Real-time voice infrastructure, SIP and WebRTC, streaming speech-to-text and text-to-speech vendors, and LLM orchestration for live conversations.
• Stripe for the price book, wallets, metered usage and invoices; HubSpot as the customer record.
• Carrier and registry APIs (The Campaign Registry, our RCS provider, number providers), webhooks in both directions.
• Vercel and cloud infrastructure, containers, CI/CD, and structured logging and tracing.

What you'll bring

• 6+ years building backend systems in production, with real ownership of services that had to stay up.
• Strong TypeScript or Node.js, and deep comfort with Postgres: schema design, migrations, query performance.
• Experience with real-time or event-driven systems: message queues, websockets, streaming, or telephony.
• A habit of designing for failure: retries, idempotency, backpressure, and clear failure modes.
• Clear written communication. You can explain a design in a page and a decision in a paragraph.

Nice to have

• Telecom experience: SIP, SBCs, STIR/SHAKEN, carrier interconnects, or messaging aggregators.
• Usage-based billing systems or ledger design.
• Experience with LLM-driven products and the latency and cost trade-offs that come with them.