次の仕事の機会を見つけましょう

職種、スキル、勤務地で求人を検索できます。応募書類を準備する前に募集要件を確認しましょう。

魅力的な職種名を見つけることは、仕事探しの出発点です。業務内容、応募条件、働き方を自分の経験と照らし合わせましょう。このガイドでは、候補の絞り込み、応募書類の準備、提出先の確認を順番に進めるためのポイントを紹介します。

操作画面は日本語です。企業が掲載した求人の職種名や説明文は原文のまま表示され、英語の場合があります。

条件をクリア

検索結果: 12,971

← 検索結果に戻る

Technical Support Engineer

Omilia

リモート勤務

勤務地
Remote (Philippines, United States)
勤務時間
Full Time
掲載日
2026年11月20日

応募する前に、企業のウェブサイトで現在も募集中かどうかと詳しい条件を確認してください。

仕事内容

操作画面は日本語です。企業が掲載した求人の職種名や説明文は原文のまま表示され、英語の場合があります。

About the company 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. Role Purpose 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. Accountabilities 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. Key Responsibilities 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 tickets when a fix is required, and assign cases to the appropriate team when assistance outside Technical Support is needed. Handle user management and service requests, including requests that need approval. Monitor health check calls and real-time metrics from the OCP alerting services during the shift, analyse every Severity 1 and Severity 2 alert, and proactively notify a customer by email when an alert relates to an issue on the customer's side. Send customer and partner notifications for upcoming NLU model updates and other platform changes. Create and update knowledge base articles, troubleshooting techniques, frequently asked questions and How-To documents in Confluence. Take part in the weekly case review calls, sharing customer requests, expectations and the severity of business impact, and organise or join conference calls with customers, partners and Omilia teams to resolve issues quickly. Use AI-assisted troubleshooting tools (for example Claude with internal Model Context Protocol (MCP) connectors) to speed up investigation, while validating results and following Omilia's data handling policies. Work an 8.5-hour shift on a weekly rota with two days off per calendar week, usually one weekend day per week, and no more than five consecutive days; working hours may fall outside traditional business hours, including evenings, nights, weekends and public holidays as scheduled. Requirements Required: Academic degree in Computer Science, Information Technology, Engineering or related field, or equivalent professional experience. 2 to 4 years of working experience in technical support for software as a service (SaaS) or cloud platforms, contact center or telephony solutions. Strong troubleshooting skills and experience reading application logs. Solid knowledge of web technologies and application programming interfaces (APIs); computer networks (the Internet protocol suite (TCP/IP), firewalls); voice and telephony basics (Session Initiation Protocol (SIP), Voice over Internet Protocol (VoIP), interactive voice response (IVR), call flows); operating systems (Linux) and scripting (bash, Python); and basic Structured Query Language (SQL). Understanding of conversational AI concepts (ASR, NLU, intents, dialog flows). Experience with ticketing systems, preferably Jira Service Management, and with Confluence and Slack. Familiarity with incident management and severity-based SLAs. Strong written and verbal communication skills, including clear status updates to customers. Willingness to work shifts on a rota, including evenings, nights, weekends and public holidays. Verbal and written proficiency in English. Nice to have: Experience with OCP or another conversational AI or virtual agent platform. Experience in a 24x7 follow-the-sun support team. Experience with cloud platforms and monitoring or observability tools. Experience using AI-assisted tools for troubleshooting. A service management certification or similar. Benefits Fixed compensation; Long-term employment with the working days vacation; Development in professional growth (courses, training, etc); Being part of successful cutting-edge technology products that are making a global impact in the service industry; Proficient and fun-to-work-with colleagues; Apple gear Omilia is proud to be an equal opportunity employer and is dedicated to fostering a diverse and inclusive workplace. We believe that embracing diversity in all its forms enriches our workplace and drives our collective success. We are committed to creating an environment where everyone feels welcomed, valued, and empowered to contribute their unique perspectives without regard to factors such as race, color, religion, gender, gender identity or expression, sexual orientation, national origin, heredity, disability, age, or veteran status, all eligible candidates will be given consideration for employment. Originally posted on Himalayas

検索して比較し、応募を準備しましょう

次の仕事で活かしたい職種やスキルから検索を始めましょう。勤務地と職種の条件を調整し、求人を開いて担当業務を比較してください。結果がない場合は、短い検索語を試すか、条件を一つずつ外してみましょう。

必須条件と歓迎条件を分けて確認し、勤務時間、報酬、勤務地が掲載されている場合は目を通しましょう。リモート勤務でも、居住国、就労資格、勤務時間帯が指定されることがあります。現在の募集状況と詳しい条件は企業に確認してください。

募集要件に関連する実際の経験を選び、自分の役割と貢献を説明しましょう。数値は根拠がある場合にのみ使ってください。企業の応募方法に従い、送信前に連絡先、内容、PDFの表示を確認しましょう。

応募前の確認リスト

仕事探しに関するよくある質問

英語の求人が表示されるのはなぜですか?

職種名や説明文は企業が作成したものです。条件や要件を変えないように原文を掲載しています。操作画面とこのガイドは日本語です。日本語の検索で見つからない場合は、「software engineer」のように、掲載言語の職種名やスキル名でも検索してみてください。検索語が自動翻訳されるわけではありません。

リモート求人なら、どの国からでも働けますか?

必ずしもそうではありません。居住国、就労資格、勤務時間帯が指定されている場合があります。元の求人ページで条件を確認してください。記載がない場合は、自分の居住地から応募できると判断する前に企業へ確認しましょう。リモートという表示だけでは、勤務地の制限がないことは分かりません。

検索結果が出ない場合はどうすればよいですか?

より一般的な職種名や一つのスキルで検索し、条件を一つずつ外してみてください。同じような仕事でも企業によって呼び方が異なります。特定の求人が見つからなくなった場合は、企業の採用ページで求人番号を探しましょう。検索条件を広げても、終了した募集が再開するわけではありません。

ResumizeAIから応募が送信されますか?

応募ボタンは外部サイトを開きます。企業または採用サービスの案内に従い、そのサイトで送信を完了してください。ResumizeAIで応募書類を作成しただけでは応募は送信されません。リンク先が企業のトップページの場合は、該当する募集を探してから手続きを進めましょう。

応募書類とカバーレターはどう調整すればよいですか?

募集要件と、自分が説明できるプロジェクト、業務、成果を結び付けます。経験していない技術や実績を加えず、関連する経験を分かりやすく示してください。カバーレターでは応募理由を具体例とともに伝えます。指定された言語とファイル形式に従い、送信前に両方の書類を確認しましょう。