Technical Support Engineer
-
IT/Tech
Job Description & How to Apply Below
Omilia is a leader in Conversational AI. Our cloud platform powers natural, human-like customer conversations over voice and chat for some of the largest enterprises in banking, insurance, telecommunications and hospitality, handling hundreds of millions of interactions a year. We build our own deep tech across the stack, from speech recognition and natural language understanding to dialog management, and we integrate natively with the major CCaaS platforms.
We are a company of roughly 500 people, distributed across Europe and North America, in the middle of an ambitious platform modernization program:
Kubernetes everywhere, autoscaling for every service, a next generation observability stack, and AI woven through our own engineering lifecycle.
The Technical Support Engineer provides 24x7x365 tierless support for the Omilia Cloud Platform (OCP), Omilia's fully managed, cloud-native, enterprise conversational AI platform for contact centers. As the single point of entry to Omilia for customers and partners, the role troubleshoots and resolves technical problems, handles user management requests, monitors platform health and alerts, takes part in incident management, and helps keep the platform and customers' services healthy around the clock.
The role is based in the United States and the Philippines and works in a follow-the-sun model so that the platform is covered 24x7x365, including evenings, nights, weekends and public holidays as scheduled.
- Handle customer and partner cases in the OSD project in Jira Service Management, whether they arrive through the OCP support portal, by email or, for Severity 1 and Severity 2 issues, through the 24x7 support phone line, and through Slack-based direct communication for customers whose Premium Support package includes it.
- Triage new cases: confirm the issue type (Support, Service Request with Approvals, Bug or Incident), set and validate severity (Severity 1 to Severity
4) against the OCP severity definitions, and respond within the OCP response Service Level Agreements (SLAs) (10 minutes for Severity 1, 30 minutes for Severity 2, 8 hours for Severity 3 and 2 business days for Severity
4), or the custom response SLAs agreed for a customer. - Work cases under the tierless model: pick up cases based on availability during the shift, join the swarm with other engineers on complex investigations, and follow the Follow-the-Sun process for Severity 1 and Severity 2 cases.
- Keep every case status accurate:
In Progress while the team is working it, Waiting for customer only when customer input is actually needed, updated when a case is with another Omilia team, and Resolved with the required fields completed (Assignee, Environment, Customer and Main Reason). - Join Severity 1 (SEV1) and Severity 2 (SEV2) PLAT incidents: engage the Incident Response Team and open the incident communication channel within 15 minutes, make sure affected customers and partners are notified within 30 minutes, investigate, and support the Incident Manager (a Technical Support Manager on shift) with regular status updates until the incident is resolved.
- After incidents, raise follow-up technical tickets with the right teams and projects, and support the post-incident review and the Root Cause Analysis (RCA) report, which is reviewed and approved internally before it is shared with customers and partners, until actions are closed.
- Support Premium Support customers as needed: hypercare for net new projects (working the technical cases and joining technical calls), open case review reports, alert monitoring and proactive notifications, sessions with a support expert and topic-based training sessions.
- Hand over open cases and incidents clearly at the end of each shift through Jira and Slack, so the next region can continue without delay.
- Troubleshoot on OCP: review dialog logs, Orchestrator apps and flows, critical errors, natural language understanding (NLU) and automatic speech recognition (ASR) behaviour, and telephony and third-party integrations to find the cause of an issue.
- Gather the evidence needed to reproduce issues (session identifiers, telephone numbers, audio files, error logs, call flows, intents, a clear problem statement and business impact) and guide customers on how to open a complete case, one case per issue.
- Escalate unresolved issues to the right Omilia team (for example software development, network engineering or security) with clear Bug…
(If this job is in fact in your jurisdiction, then you may be using a Proxy or VPN to access this site, and to progress further, you should change your connectivity to another mobile device or PC).
View / Apply for Jobs
Matching My Jurisdiction