As an Enterprise Browser DevOps Engineer , you will be responsible for the reliability, availability, and performance of the firm's secure enterprise browser platform. You will treat operations as a software problem: define service levels, engineer away toil, and keep the platform production-ready as it scales.

Reporting to the platform's lead engineer, you will share production ownership and on-call duties with SRE and incident response teams, removing single points of failure on a system people depend on to do their jobs. You will lead incident response, root cause analysis, harden the platform against mass-impact events, and build the automation, monitoring, and access controls that let a small team run a large environment safely.

•       Engineer, test, and deploy access and identity controls — group policy and SAML-based role.

•       Manage safe change through browser version and extension lifecycle, including staged rollout, validation, and fast rollback.

•       Eliminate toil by building automation for deployment, configuration, monitoring, and health checks.

•       Define service-level objectives and deliver the observability, performance analytics, and capacity insight that keep the platform healthy at scale.

•       Production reliability and lead incident response during outages and mass-impact events, driving tier-4 troubleshooting and blameless post-incident review to permanent fixes.

•       Operated business-critical production systems, owning reliability, availability, and on-call.

•       Software-driven operations: Linux administration and coding (Python, Bash) with infrastructure-as-code and configuration management.

•       Delivered endpoint or enterprise browser controls, including group policy, SAML/SSO, and extension governance.

•       Built CI/CD, observability, and automated health checks that reduce toil across the deployment lifecycle.

•       Led incident command and root-cause analysis, turning findings into lasting reliability improvements.

•       Site reliability practices such as SLOs/SLIs, error budgets, and blameless postmortems.

•       Enterprise browser, or VDI/thin-client platform experience.

•       Progressive delivery patterns such as canary and feature-flagged rollout with automated rollback.

•       Regulated-environment delivery with audit logging and controls.

•       Telemetry analytics using SQL and operational dashboards.

•       Treats operations as a software problem and engineers toil away.

•       Calm and decisive as incident commander under mass-impact events.

•       Measures reliability and lets data drive priorities.

•       Owns production as one of a small, senior team.

The team runs an Enterprise browser as a production, web-first platform — a complete work environment for the firm's user base. It is hands-on, owning reliability, access controls, browser lifecycle, and the automation that lets a lean team keep a regulated platform available at scale without a separate operations function.