Skip to content
CV Rocket
Get started
How it worksThe enginePricingBlogContactSign in

Open nowPosted 34 hours agoWe saw it 95 min after it went up

Production Support & Incident Commander

Evismart16 open roles

Where
Taguig
Get the CV for this job

From $25 per CV, paid once. No subscription.

Your applicationOpen nowProduction Support & Incident CommanderEvismart · Taguig

  1. YouYes, apply to this one.

  2. CV RocketCV written for this posting.

  3. 25 readersRecruiter, hiring manager, skeptic. Round after round.

  4. CV RocketApplied on Evismart's own form.

The reply lands in your private mailbox

3×more interviews than doing it yourself with ChatGPT.

The clock on this job

Early applications get read.

8.1% of postings close within 7 days. Measured by our own scanner across the market. Evismart postings stay open a median of 17 days.

Share of postings closed within
  1. 1.7%1 day
  2. 3.6%3 days
  3. 8.1%7 days
  4. 15.0%14 days
  5. 33.9%30 days
This job: posted 34 hours ago

Evismart median: 17 days open

The posting

Incident Commander | SaaS Production Operations

Permanent night shift • Individual Contributor • Full onsite – BGC, Taguig

This is not an escalation coordinator role. We need someone who can make real-time production recovery decisions when systems fail and customers are already affected.

When an incident happens, your job is not: Follow procedure → identify resolver → escalate → wait → send updates.

Your job is: Understand what is actually affected → determine the fastest safe recovery path → make the call → direct the teams involved → keep the customer operational → stay on it until production is restored.

What this actually looks like

EviSmart is a live SaaS platform with multiple applications, services, dependencies and operational workflows.

When something breaks, the answer will not always be written in a runbook.

You need to be able to determine:

  • What is actually failing?
  • What is the customer impact?
  • Which systems or dependencies are involved?
  • Is the normal recovery path working?
  • How long should recovery reasonably take?
  • Can Production/Application Support restore it?
  • Do we actually need Engineering?
  • Is there a workaround or manual process that keeps the customer operational?
  • At what point do we stop waiting and change the recovery strategy?

Different failures have different recovery paths. During the incident, you own the clock and the decision.

If the normal recovery route isn't working, we expect you to recognize that quickly and change course rather than continue following a process that is no longer protecting the customer.

That can mean restoring the application, rolling something back, implementing a safe workaround, directing Support or Engineering, or switching operations to a manual process while the underlying issue is being resolved.

You stay accountable until production is operational again.

What we mean by Incident Commander

You command both the people and the recovery strategy.

Engineering may perform the permanent technical fix. Production Support may execute part of the recovery. Customer Support may need to communicate a workaround.

But during the incident, you are responsible for determining what needs to happen next and driving everyone toward recovery.

You need enough technical depth to investigate production issues yourself using things such as logs, monitoring, application behavior, databases, APIs, recent releases and system dependencies.

You also need enough judgment to know when to continue investigating, when to restore, when to escalate technically, and when the safest decision is to keep the customer moving another way.

Incident Management experience alone is not enough

You may have years of Incident Management experience and still find this role difficult.

Our production environment is a large, interconnected ecosystem. An issue in one part of the system can affect another application, workflow, team or customer process.

If most of your experience has been following established procedures, running bridges, coordinating resolver groups and escalating technical decisions to someone else, this is probably not the right role for you.

We need someone who can reason through an unfamiliar production problem even when:

the documentation is incomplete, the normal process isn't working, information is still coming in, teams disagree on the cause, and the person you would normally escalate to isn't available.

You won't know our ecosystem on Day 1. We can teach you that.

What is much harder to teach is the ability to analyze a complex system, make a defensible decision with incomplete information, take responsibility for that decision, and change course when the evidence tells you you're wrong.

If your background isn't a perfect match but you genuinely believe you can demonstrate that level of technical reasoning and judgment to us during the interview, we're willing to give you the opportunity to prove it.

We're likely to be interested if you come from

Production Support, Application Support, SaaS Operations, Site Reliability, Technical Operations, Incident Response, or another environment where you have personally handled business-critical production failures.

We're particularly interested in people who have worked with multiple interconnected applications or services and have personally made recovery decisions during live incidents.

The simplest test:

At 2 AM, production is down, the runbook isn't solving it, Engineering isn't available, and customers need to keep operating.

Can we trust you to figure out what needs to happen next, make the call, and own the outcome?

If yes, we want to talk to you.

From $25, paid onceGet the CV for this job

What happens when you press

One press. We do the rest.

  1. A CV for this posting

    Written against Evismart's own wording, from every piece of relevant proof in your profile.

  2. 25 readers review it

    Recruiter, hiring manager, skeptic and more read every draft, round after round. You get the best round.

    The review screen in CV Rocket: how each CV was read, round by round.

  3. We apply on Evismart's form

    Our application engine gets through the hardest forms there are. Where a question needs you, AI suggests the best answer. Don't want us applying from our IP addresses? Use our Chrome extension: we apply straight from your own browser.

    An application in CV Rocket: every answer filled in on the employer's form.

  4. Every reply, sorted

    Evismart's answer lands in your private mailbox, and we classify it on arrival: interview, question, rejection.

    The CV Rocket inbox: each employer reply classified as an interview, an action or a rejection.

  5. Reply with AI

    AI helps you write the email, checks it and sends it. We show you whether the recruiter read it.

  6. The interview in your calendar

    Full integration with your calendar. The invitation goes straight in.

    An interview invitation in the CV Rocket inbox, added to the candidate's calendar.
Get the CV for this job

From $25 per CV, paid once. No subscription.

Why it works

3×

more interviews than doing it yourself with ChatGPT.

ChatGPT writes a CV and never learns what happened to it. We see every reply. For each CV we know:

  • How it was written, and how the review scored it
  • When we applied, and how long after the posting went up
  • Which posting, which company, which city
  • Who got the interview, and who heard nothing

That is how we know which CVs get called.

Get the CV for this job

From $25 per CV, paid once. No subscription.

The numbers game

More applications. More interviews.

Every application goes out with its own CV, written for that posting and paid once. Send enough of them and the law of large numbers finds you the job.

Get the CV for this job
By hand5–10
With CV Rocket100
applications a day

Nearby

Live postings like this one

Same employer first, then the same role elsewhere.

Before you press

Straight answers

Get the CV for this job

From $25 per CV, paid once. No subscription.

What if my background isn't good enough?

We make the most of the background you have. The CV uses every piece of relevant proof your profile holds, and one of the 25 readers reads your whole profile and flags what the CV left out.

Do you really apply for me?

Yes, on the employer's own form, the hardest ones included. Where a question needs you, you answer it right there and AI suggests the best answer. Don't want us applying from our IP addresses? Use our Chrome extension: we apply straight from your own browser.

Is it a subscription?

No. You pay once per CV, from $25. Every application goes out with its own CV, written for that posting.

One job. One CV.
Paid once.

Pick the posting you want. We write for it, apply for you and catch the reply.

Get the CV for this job

From $25 per CV, paid once. No subscription.