Turn this role into an interview — a resume and cover letter built around what this employer wants.
TTEC Digital seeks an Engineering Technical Lead for a full-time, fully remote role in the United States. You’ll lead a squad building a real-time, event-driven platform combining voice, desktop, and AI functionalities, using Go services, AI/ML pipelines, and connectors to CCaaS/CRM/telephony.
You will mentor engineers, set patterns, and demonstrate velocity with rapid delivery. Expect a startup-like cadence, bold experimentation, and high-impact outcomes across enterprise deployments.
At TTEC Digital, we coach clients to ensure their employees feel valued, and fully supported, because an amazing customer experience is an employee first process. Our vision is the same, a place where employees know they can thrive.
TTEC Digital seeks an Engineering Technical Lead to join our team. This role is a full-time and fully remote opportunity!
We’rean innovation group inside TTEC (NASDAQ: TTEC), building the next generation of AI CX tools —automated QA, conversational analytics, knowledge assist, and agentic automation— for the world’s biggest brands and the millions of customers they serve. We move like an early-stage startup, backed by the scale, distribution, and enterprise client base of a companythat’sbeen obsessed with customer experience since 1982.
This is the rare seatwheregetting in early actually matters at scale. TTEC is a public company at an AI inflection point. Ship the right products into thousands of live enterprisedeploymentsand youdon’tjust move a metric — you move the trajectory of the company and the value of the stock. The leverage is real, and the work compounds.
Self-starters and do-erswith grit — hackers in the best sense, with a startup mentality and a show-me bias: working software over slides, prototypes over proposals.
Wanttolearn,lovenew technology. This platform is built on the latest technology, and that technology changes and advances monthly. You adapt to change quickly — new tools, new models, new priorities — without drama.
Master debuggers and problem solvers. You love solving complex problems, youthink outside the box, and you multitask across domains without losing the thread.
AI-native. You work with AI on all levels — you understand the technology around you (LLMs, SLMs, RAG, knowledge graphs, agents, training, eval) and you use AI tools daily to exponentially increase your velocity.
Distributed-systemsliterate. High-efficiency, event-driven, low-latency systems are our world; you understand what that demands.
Innovators who ship. Youdemonstrateideas easily, fail fast, and move forward. You make committed timelines and hit them.
You consider yourself exceptional — and you like winning. So dowe.
No one will have everything in this description. We’re looking for well-rounded, smart people who move fast.
9+ years hands-on; same language bar (HIGH++ Go, 3+ languages) and same AI, debugging, and velocity bar as the Senior Software Engineer role — you must out-code the squad you lead.** **
Has led a squad and shipped a hard real-time or platform product end-to-end, on committed timelines.
Sets patterns by shipping them; owns the code-review bar and raises the engineers around you.
Owns delivery — moves blocked work,doesn’tjust report it.Show-mementality: your squad demos working software every Friday.
Keeps the respect of senior engineers through technicalcredibility, andmanages change without drama — priorities and tech will shift under you.
Event-driven systems in production (NATS / Kafka / Redpanda-class) — you think in pub/sub. Heavy WebSocket, real-time, low-latency.
Mid-tier or better hands-on AI experience in the code and product —you’vebuilt with LLM APIs, embeddings, RAG, or model serving, not justchattedwith a bot. And you use AI-assisted development daily to multiply your velocity.
Strong ++ for data graph/knowledge graph background, or hands-on AI/ML model experience (training, serving, eval).
Efficiency in development — we deal in speed. You ship clean code fast, unblock yourself, and your estimates hold.
A master debugger — you read unfamiliar code, a stack trace, or a flaky partner API and see it; you know where the breakpoint goes.
GCP preferred. Voice (SIP/RTP/SIPREC), CCaaS/CTI, or desktop-adjacent experience a strong plus depending on track.
Track emphasis: