Senior Site Reliability Engineer

Join us at Entrust  

At Entrust, we’re shaping the future of identity centric security solutions. From our comprehensive portfolio of solutions to our flexible, global workplace, we empower careers, foster collaboration, and build solutions that help keep the world moving safely.  

Get to Know Us  

Headquartered in Minnesota, Entrust is an industry leader in identity-centric security solutions, serving over 150 countries with cutting-edge, scalable technologies. But our secret weapon? Our people. It’s the curiosity, dedication, and innovation that drive our success and help us anticipate the future. 

Position Overview:

The Instant Financial Issuance as a Service (IFIaaS) Cloud Service includes a wide array of components including web services, application servers, and databases hosted in an on-prem environment. The Sr. Site Reliability Engineer (SRE) will be responsible for ensuring that the SaaS platform is reliable, available, and performant, as well as scalable, secure, and cost-effective. Ultimately, the individual will be responsible for the platform uptime, functional management of all the IFIaaS cloud environments, applications, networks, scoping projects, and the resolution of application and network issues.

Responsibilities:

• Own SLOs/SLIs for availability (99.9%), latency, error rate, and quality of service across microservices.

• Design/operate end‑to‑end observability: metrics, logs, traces, synthetic checks, real‑user monitoring (RUM).

• Instrument services (Windows services, APIs, background jobs) with structured logs and trace context.

• Build health probes and SLA monitors for critical transactions and cross-service dependencies.

• Monitor system issues using various metrics, such as uptime, latency, error rate, throughput, and availability

• Deploy and maintain monitoring and on-call tools i.e.: Splunk on-call, Prometheus, Datadog, etc.

• Lead incident response (triage, comms, coordination, real-time mitigation) and conduct blameless postmortems with actionable follow-ups.

• Maintain and continuously improve runbooks, escalation paths, on call rotations, and paging policies.

• Implement MTTA/MTTR reduction programs.

• Stand up war room protocols and ensure stakeholder updates during incidents.

• Forecast compute, storage, network needs, track headroom against growth and peak patterns.

• Conduct performance profiling and bottleneck analyses (CPU, memory, I/O, thread pools, connection pools).

• Optimize resource allocation on VMware (DRS, affinity rules, reservations) and Windows VM tuning (kernel, TCP stack, NICs).

• Validate scaling strategies (horizontal vs. vertical) and implement auto-scaling where supported.

• Standardize gold images, configuration baselines, and desired state for Windows Server (PowerShell DSC or equivalent).

• Manage patching (OS, middleware, runtime) with maintenance windows aligned to error budgets.

• Ensure backup, snapshot, and restore strategies meet RPO/RTO; regularly test restores.

• Maintain secure baselines (CIS benchmarks for Windows/VMware), vulnerability management, and patch cadence.

• Support compliance audits (PCI-CP, PCI-DSS, SOC 2/ISO 27001), produce evidence (configs, logs, access reviews), and remediate gaps.

• Automate provisioning (VM templates, DSC/Ansible for Windows, Terraform for VMware) and configuration drift detection/correction.

• Build runbooks to reduce toil (deploy, scale, rollback, etc)

• Create reliability guardrails (pre‑flight checks, change freeze rules, policy controls) as code.

• Continuously refactor scripts/runbooks into idempotent automation.

• Collaborate with development teams and other stakeholders to identify potential risks, such as security vulnerabilities, performance bottlenecks, deployment issues, or configuration errors

• implement various risk mitigation strategies, such as patching, backup, redundancy, encryption, or testing

• Collaborate with product teams and other teams to understand the user needs, expectations, and satisfaction. 

• Coach engineers on SRE principles, incident handling, and reliability centric design.

• Lead knowledge sharing, runbooks qual