> Markdown version of [/jobs/ext/4662425-senior-software-engineer-ai-native](https://www.wearedevelopers.com/jobs/ext/4662425-senior-software-engineer-ai-native). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Senior Software Engineer (AI-Native) - **Company:** TELEGENT INC. - **Location:** Pleasant Grove, UT, United States - **Experience:** Expert - **Contract:** Permanent contract - **Skills:** Automatic Call Distributor, Application Programming Interfaces (APIs), Artificial Intelligence, Data Analysis, Microsoft Azure, C++ (Programming Language), Cloud Computing, Information Systems, Command-Query Responsibility Segregation (Software Development), Relational Databases, Cursor, Shard (Database Architecture), Linux, Distributed Systems, Enterprise Messaging Systems, Software Engineering, SQL Databases, Data Streaming, TypeScript, Management of Software Versions, Test-Driven Development (TDD), Claude Code, Multi-Agent Systems, Caching, Rate Limiting, Git, Information Technology - **Published:** November 10, 2026 - **Apply:** https://www.careerbuilder.com/job-details/senior-software-engineer-ai-native-pleasant-grove-ut--c329bb6c-074e-4bbf-9254-8f9ea1cee223 ## About the Role Software Engineering, Artificial Intelligence (AI), Cellular Telephone, Artificial Intelligence (AI), Call Routing, Mobile Devices, Information Technology & Information Systems, System Lifecycle, Test Driven Development (TDD), Typing, You've written enough code and built enough systems at scale to show real mastery. You get the git versioning jokes and the Linux memes, and your servers hiccup in fear of Kai Lentit, * Product and application engineering. A track record of shipping customer-facing services and APIs at scale, from design to production. * Distributed systems and data. Deep, hands-on experience across transactional, wide-column, streaming, analytical, ledger, cache and object stores, and the judgment to use each one well. * Reliability at scale. Replication, consistency, sharding, and read and write access patterns, with RPO and RTO in mind. * Cloud and infrastructure. Azure first, plus multi-region and multi-provider deployments. * Languages. Fluent in TypeScript for product, services and APIs, and Go for high-throughput services, plus SQL. * AI-native. You practice enterprise-grade agentic coding, not vibe coding, and you move easily across coding clients and harnesses. You arrive with your own setup of agents, skills and automations, and ideas on how to make ours better. * Ownership and judgment. You take work from idea to production without hand-offs, raise problems early, and help keep the team pointed in the right direction. ## Description * Deliver the product roadmap. Design, build and ship new capabilities across messaging (SMS, MMS and RCS), voice and carrier integrations as services on the new platform. * Build on the target architecture. Use the right store for each feature, follow the patterns and standards already set, and extend them where the roadmap needs it. * Own features end to end. From design through testing, release and monitoring in production, including the rollout and rollback plan. * Keep services reliable at scale. Watch performance and failure behaviour as partners and traffic grow, and fix what holds us back. * Retire legacy workflows as you go. When a feature moves to the new platform, switch off the legacy workflow it replaces, with no downtime. * Keep the platform on track. Work with engineering leadership on architecture decisions, raise risks early, and hold the standard: small, versioned, reversible changes behind PRs with CI. * Grow together. Collaborate closely with engineering, product and leadership in an AI-native environment, learning from each other and raising the bar as a team. The platform you will build on: * Relational database: The transactional system of record, with real keys and integrity * Wide-column store: High-throughput message and call records (append-heavy, the hot path) * Event streaming: The event and streaming backbone between producers and consumers * Analytics store: Analytics and reporting over message and call volume * Ledger: The accounting and usage ledger * Cache: Caching, hot lookups and rate limiting * Object storage: Large payloads, MMS media and archives, * Telecom or messaging platforms: SMS, MMS, SIP or carrier integrations * CQRS and event-driven designs in production * Billing or ledger systems, where every entry is append-only and auditable * Building to SOC 2 controls from the first line of code * Rust or C/C++ for performance-critical paths in the ledger and data plane How we work * Learn, assess, benchmark, prepare solutions. Every responsibility runs this arc, done fast. Your first deliverable is your own assessment and 100-day plan. * AI-first. Design and implementation are agent-driven across Claude Code, Cursor, Codex and multi-agent workflows, so one engineer moves at the pace of a team. * End-to-end ownership. Engineers take their work from design through deployment and production. * Small, reversible changes. Versioned, behind PRs with CI, with release tags and documentation that updates as the code does. * Security from the start. New systems are built to SOC 2 controls, with architecture decisions recorded as ADRs.