Turn this role into an interview — a resume and cover letter built around what this employer wants.
EviSmart is seeking a Global Continuity Lead to own incident response and platform continuity during night operations. You will be the lead incident response person on shift, investigate issues, determine safe restoration paths, and coordinate with Engineering and DevOps to minimize disruption for 2,000+ dental labs on our platform.
The role emphasizes business continuity, proactive monitoring, and clear communication with stakeholders during active incidents.
Job Description:
Why EviSmart
How We Work We ship before we're 100% certain. We write things down because we have two offices and memory is lossy. We debate loudly and move without resentment. We treat the customer's real problem as more important than an elegant internal process. If you've spent time waiting for permission to try something obvious — you'll notice the difference here immediately.
Production Support & Incident Response Lead
When something goes wrong in production overnight, you are the person leading the response.
EviSmart is looking for a Global Continuity Lead to own incident response and platform continuity during our night operations.
This is not a role where you simply monitor dashboards, create a ticket, and wait for Engineering.
You will be the lead incident response person on shift. You are expected to investigate first, understand what is happening, determine the safest way to restore operations, bring in the right technical people when necessary, and remain accountable for the incident until the platform is stable.
Our platform supports 2,000+ dental labs, so an issue in production can quickly become a real business problem for our customers. The goal is simple: keep cases moving and minimize disruption.
What you'll own:
You will be responsible for the health and continuity of the platform during your coverage.
That means:
The role's ownership of monitoring, incident command, proactive customer communication, post-mortems and backup development is explicit in the operating playbook.
What this role is NOT
This is not a traditional Service Delivery Manager or ITIL governance position.
It is also not a pure DevOps or Software Engineering role.
You don't need to be the person who writes the permanent code fix for every problem. But you do need enough technical depth to investigate intelligently before asking someone else to solve it.
If your normal incident process is:Alert → Create ticket → Escalate → Wait
this probably isn't the right role.
We're looking for someone whose instinct is closer to:
Detect → Investigate → Isolate → Restore or Work Around → Escalate Intelligently → Command Through Resolution → Prevent Recurrence
The kind of person we're looking for
You may currently be an:
Senior Application Support Engineer, L2/L3 Application Support Engineer, Production Support Engineer, Application Operations Engineer, Technical Operations Engineer, Platform Support Engineer, or similar.
More important than your current title is how you operate.
You are someone who:
Here's a good way to know whether you'll enjoy this role.
It's 2 AM.A production issue is preventing a customer from processing cases. The permanent fix requires an engineer who isn't immediately available.
What do you do?
We're looking for someone who doesn't stop at "I'll escape it."
We want someone who starts asking:
What's actually broken?
What's the business impact?
What changed?
What can I verify myself?
Can I safely restore the previous working state?
Is there another way to keep the customer's operation moving?
Who genuinely needs to be involved?
What can we do now instead of waiting until morning?
That's the mindset we're hiring for.
What success looks like
Your first 90 days are designed to progressively prove that we can trust you with the night.
First 30 days: Learn the platform and prove you can troubleshoot real issues and identify the correct workaround without being walked through every step.