Problem Engineer

Job Overview

The Problem Management Engineer is responsible for preventing incidents from recurring.

Following every P1/P2 incident or upon identifying recurring incidents, the role holder initiates and coordinates Problem Records, facilitates blameless post-incident reviews (COE), documents Known Errors, and tracks Corrective and Preventive Actions (CAPA) until they are fully completed by the responsible teams.

In addition, the Problem Management Engineer translates lessons learned into operational runbooks, enabling the IPM Department to independently handle similar incidents in the future without waiting for L2/L3 teams.

Key Responsibilities

  • Initiate the Problem Management process in the following situations:
    • A P1/P2 incident has been closed.
    • The same incident with the same root cause has occurred at least twice within 30 days.
    • Ticket data indicates abnormal trends.
    • Tickets remain pending at the Knowledge Base (KB) stage.
  • Create a Problem Record in Jira within one business day, assign a priority level (High, Medium, or Low), and request the responsible team to appoint a Technical Owner.
  • Facilitate a blameless Cause of Error (COE) review within five business days, focusing on establishing the incident timeline, assessing business and operational impact, and identifying root causes using the 5 Whys methodology. The Technical Owner is responsible for conducting the technical Root Cause Analysis (RCA).
  • Document Known Errors and workarounds in the Known Error Database (KEDB). Work with Domain Owners to create or update runbooks, enabling the IPM Department to independently handle similar incidents in the future.
  • Develop and maintain a CAPA action plan, ensuring each action has an assigned owner from the responsible team and a clearly defined completion deadline (30, 60, or 90 days).
  • Facilitate weekly Problem Review meetings; escalate overdue CAPA actions to the Reliability Council on a monthly basis; and consolidate a monthly Top 10 list of major recurring problems.
  • Close Problem Records only after all CAPA actions have been completed and no recurrence has been observed during the 30-day monitoring period.
  • Review incidents reported within the previous 24 hours during Daily Ops Standup meetings.

Requirements

  • Bachelor’s degree in Information Technology, Computer Science, Computer Networks, or a related field.
  • At least 3 years of experience in Enterprise/Cloud operations at L2/L3 level, SRE, or infrastructure support.
  • Proficiency in root cause analysis methodologies such as 5 Whys, Fishbone Diagram, and incident timeline analysis, with the ability to critically challenge RCA reports when the findings are insufficient or unconvincing.
  • Strong understanding of ITIL 4 Problem Management and Knowledge Management practices. ITIL 4 Foundation certification is an advantage.
  • Understanding of Cloud technology domains, including IaaS, PaaS, and SaaS services, as well as common failure scenarios in each domain.
  • Strong coordination and facilitation skills, with the ability to lead meetings involving engineers from multiple technical teams.
  • Ability to produce clear, structured COE reports in both Vietnamese

Working Environment

  • Working location: 7th Floor, FPT Tower, no. 10 Pham Van Bach Street, Dich Vong ward, Cau Giay district, Hanoi.
  • Working hours:
  • Full time
  • 8h30 AM – 12h00 PM
  • 1h00 PM – 5h30 PM
Contact Person

Pham Thi Ha My (Ms.) – Talent Acquisition Team Leader
Email: [email protected]
Phone: 0962456194
FPT Smart Cloud (FCI) Co., LTD
Address: 7th Floor, FPT Tower, No. 10 Pham Van Bach, Cau Giay Dist, Hanoi
Websites: FPT Cloud | FPT AI

Đăng ký theo dõi ngay!

Đừng bỏ lỡ các thông tin mới nhất về các sản phẩm và dịch vụ của chúng tôi!
Đăng ký ngay