Yunus Simsek — Professional Profile

A resume-derived source for conversations about enterprise engineering, leadership, and applied AI.

Evidence basis: owner-provided resume; self-reported claims, not independently verified

Currency: Present refers to the supplied resume. Current employment and project status have not been reconfirmed. Do not infer completion of the planned Q2 2026 Grafana migration.

Engineering leader and senior technical contributor with 12+ years of experience reported in enterprise technical support, escalation engineering, platform troubleshooting, and team leadership. The resume lists Team Lead, US & Lead Engineer (IC5), Account Escalation Engineering at ServiceNow as the most recent role. Builds AI-assisted internal tools and designs agentic concepts to address operational problems.

Location: Orlando, Florida, United States

Identity reference: LinkedIn. This profile does not independently verify LinkedIn contents.

The professional story

A foundation in production systems

Reported facts: The resume begins with remote database administration in 2012, followed by Oracle DBA/EBS DBA work serving enterprise clients. It reports RAC upgrades, an 800GB+ EBS database migration, and subsequent Oracle support and performance engineering roles.

Interpretation: This progression suggests a foundation in diagnosing production behavior across database and application layers. It does not establish expertise in every infrastructure discipline.

Related source records: dbadirect, data-intensity, oracle-support, oracle-performance.

From diagnosis to escalation ownership

Reported facts: At ServiceNow, the listed roles progress from performance support to SWARM mentoring and Account Escalation Engineering. The resume describes SQL tuning, API latency investigations, observability, and cross-functional defect resolution.

Interpretation: A recurring theme is turning ambiguous technical symptoms into a diagnosis that engineers and customers can act on.

Related source records: servicenow-performance, servicenow-swarm, servicenow-escalation.

Scaling expertise through people and tools

Reported facts: The most recent listed role combines US team leadership for 10+ engineers with personal ownership of high-severity escalations. Responsibilities include coaching, onboarding, hiring panels, and executive-facing root cause narratives.

Interpretation: The profile supports a picture of a hands-on leader who works through technical problems while building team capability. The $50M+ figure describes combined customer contract value, not revenue he personally generated.

Related source records: servicenow-lead.

Applying AI to operational problems

Reported facts: The resume lists independently built AI-assisted internal applications, browser scripts, and automation. It separately identifies Catch Me Up and DB Diagnoser as agentic concepts.

Interpretation: His AI story is grounded in applying development tools to work he understands. It supports practical AI-assisted building; it is not evidence of training foundation models or conducting ML research.

Related source records: supporthub, escalation-portal, catch-me-up, db-diagnoser.

Project stories and evidence

SupportHub

Status: Built and shipped, according to resume

Contribution: Independently built with AI-assisted development

Turned 10+ CLI scripts into a full-stack Flask/React application so engineers could use terminal-only utilities through a web interface.

Problem described in source: The resume describes terminal-only utilities that were not accessible to all engineers regardless of technical background.

What he did: He webified 10+ CLI scripts into a Flask/React application using AI-assisted development.

Outcome and evidence: The reported delivered result is a web interface to existing utilities. Adoption rates, time savings, and maintenance outcomes were not supplied.

Interpretation: This suggests an emphasis on making existing engineering capability easier for a broader team to use.

Evidence limit: No public demo, code, or measured adoption data supplied.

Escalation Engineering Portal

Status: Built, according to resume

Contribution: Independently built with AI-assisted development

Internal portal with 10+ tools, including SQL formatting, PostgreSQL query building, and explain-plan visualization, intended to reduce context switching.

Problem described in source: The resume identifies engineer context switching as a problem the portal was intended to reduce.

What he did: He built an internal portal with 10+ tools, including a SQL formatter, PostgreSQL query builder, and explain-plan visualizer.

Outcome and evidence: The portal is reported as built. Reduced context switching is an intended benefit; no measured reduction was supplied.

Interpretation: The project suggests attention to the workflow around technical diagnosis, alongside the diagnosis itself.

Evidence limit: No quantified time savings supplied.

Escalation Lifecycle Blueprint

Status: Developed, according to resume

Contribution: Independently developed with AI assistance

Interactive HTML/React page mapping escalation stages to relevant tools.

Problem described in source: The resume describes a need to surface the right tools at each escalation stage.

What he did: He developed an interactive HTML/React page that visualizes stages and associates them with tools.

Outcome and evidence: The page is reported as developed. The source does not quantify adoption or escalation-resolution improvement.

Interpretation: This connects process design with practical access to engineering tools.

Idea Portal

Status: Launched, according to resume

Contribution: Built a ServiceNow-based portal

Captures team-driven innovation ideas and makes bottom-up improvements more visible.

Celebration Flow

Status: Built, according to resume

Contribution: Built using Microsoft Power Automate and a Claude artifact

Reads Excel data, alerts managers ahead of birthdays and work anniversaries, and provides a link for generating personalized celebration cards.

Catch Me Up

Status: Agentic concept; not established as shipped

Contribution: Designed the concept

Proposed account-escalation catch-up across a date range using case changes, task updates, and alerts.

Problem described in source: The proposed problem is reconstructing what changed on an escalated account between two dates.

What he did: He designed a concept combining case changes, task updates, and alerts into a catch-up experience.

Outcome and evidence: Concept only: implementation, deployment, accuracy, and time saved are not established.

Interpretation: The concept reflects an interest in using agents to reduce the effort of recovering operational context.

DB Diagnoser

Status: Agentic concept; not established as shipped

Contribution: Designed the concept

Proposed agentic diagnostics for slow queries, memory issues, and CPU bottlenecks across application and database servers. Reduction in triage time is an intended benefit, not a measured result.

Problem described in source: The proposed problem is manually identifying slow queries, memory issues, and CPU bottlenecks across application and database servers.

What he did: He designed an agentic diagnostic concept addressing those categories of issues.

Outcome and evidence: Concept only: no deployed agent, evaluation results, or measured triage savings are supplied.

Interpretation: The concept extends his database and performance background toward AI-assisted investigation.

Tampermonkey scripts and Python automation

Status: Authored, according to resume

Contribution: Authored browser scripts and Python automation

Automates JIT access, escalation closure, health checks, and SharePoint folder creation.

SharePoint Escalation Site

Status: Built and maintained, according to resume

Contribution: Built and maintains the team's site

Central knowledge, tooling, and process documentation for Escalation Engineering.

Enterprise Command Center Analyzer

Status: Built and adopted across Oracle Support teams, according to resume

Contribution: Built the analyzer at Oracle

Detects Enterprise Command Center installation issues.

Career timeline

Team Lead, US & Lead Engineer (IC5) — Account Escalation Engineering | ServiceNow

Dates: February 2024 – Present in the supplied resume

Staff Engineer — Account Escalation Engineering | ServiceNow

Dates: June 2023 – February 2024

Staff SWARM Performance Support Engineer | ServiceNow

Dates: 2021 – June 2023

Staff Performance Support Engineer | ServiceNow

Dates: 2020 – 2021

Senior E-Business Performance Engineer | Oracle

Dates: 2018 – 2020

Technical Support Engineer | Oracle

Dates: 2016 – 2018

Oracle DBA / EBS DBA | Data Intensity & Clear Measures

Dates: 2014 – 2016

Junior Oracle DBA | dbaDIRECT

Dates: 2012 – 2014

Questions worth asking

What connects his career stages?

Interpretation: a progression from production database work to enterprise performance diagnosis, escalation ownership, team leadership, and AI-assisted operational tools. The career timeline and project records provide the reported facts behind that reading.

How does he lead?

The resume reports coaching, onboarding, hiring participation, mentoring, executive communication, and leadership of 10+ escalation engineers while remaining personally involved in high-severity cases. It does not provide direct reports' testimonials or an independently assessed leadership style.

Which AI work is built and which is conceptual?

SupportHub and the Escalation Engineering Portal are reported as built with AI assistance. Catch Me Up and DB Diagnoser are explicitly concepts. AI-assisted development does not mean every resulting application contains an AI agent at runtime.

Which opportunities does the profile suggest?

Interpretation: enterprise escalation engineering, performance/support engineering leadership, and operational tooling are supported by the listed experience. Suitability for a particular role requires comparing its requirements with the facts and evidence gaps; no target role or availability has been specified.

Did the Grafana migration launch?

Not established. The resume describes a planned Q2 2026 go-live. This profile does not confirm completion.

What should a recruiter validate in conversation?

Current role and scope; personal contribution and adoption of internal tools; the basis of reported metrics; deployed versus conceptual agentic work; and desired next role and availability.

Skills

Support And Leadership: Technical support, Root cause analysis, Escalation management, Incident resolution, Coaching, Hiring panels, Onboarding, Executive communication

Ai And Development: AI-assisted development, Agentic workflow concepts, Python, JavaScript, Flask, React, Tampermonkey, OpenAI API / ChatGPT, Microsoft Power Automate

Platforms: ServiceNow, Oracle EBS, OCI, WebLogic, Apache, ITSM

Observability: Splunk, Grafana, Kibana, Snowflake, P99 latency, API performance, Transaction volume dashboards

Databases: Oracle 11g/12c/19c, PostgreSQL, SQL tuning, Query optimization, RAC, RMAN, Indexing

Education

Certifications

Recognition

Interpretation Limits

Source provenance

The owner supplied Yunus_Simsek_Resume.pdf privately. The original PDF is not hosted. The resume is not explicitly dated. Profile processed on 2026-10-01. Reported metrics are not independently verified.

Personal interest in AI and career development comes from the owner’s website brief. Project stories add labeled interpretations of the resume; they do not add new measured outcomes or undisclosed implementation details.