job posting · greenhouse
NICE LTD.: Lead DevOps Engineer
Observed on the employer’s careers system, last checked 2026-09-03.
- Employer
- NICE LTD.
- Location
- United Kingdom - London; United Kingdom - Southampton
- Category
- CX - Platform Operations
- Posted
- 2026-06-29
- Careers system
- greenhouse
- Observed
- 2026-09-03
Role description
Verbatim from the employer’s posting, rendered as plain text.
At NiCE, we don’t limit our challenges. We challenge our limits. Always. We’re ambitious. We’re game changers. And we play to win. We set the highest standards and execute beyond them. And if you’re like us, we can offer you the ultimate career opportunity that will light a fire within you. So, what’s the role all about? We are looking for a Senior software engineer who is passionate about solving infrastructure challenges through software engineering and automation. In this role, you will design, develop, and maintain scalable automation frameworks that streamline cloud infrastructure provisioning, configuration management, and operational processes. You will build programmatic infrastructure solutions using Python , Jinja2 , and Terraform , generating and managing Infrastructure as Code (IaC) at scale. You will also leverage Puppet…
Provenance
4906285101Machine access: how can AI agents and developers use this data, free and without an API key?
Every figure shown here about Lead DevOps Engineer at NICE LTD. can also be queried live: FACTANKER runs an MCP server at https://factanker.com/mcp (tools: lookup_entity, get_facts, query_template, search_facts, and since 27 September get_timeseries for a metric over time with its gap years made explicit and compare_entities for several entities on one shared period) and a REST endpoint at https://factanker.com/api/get_facts. Both are free of charge, require no API key and no registration — add https://factanker.com/mcp as a connector in Claude, ChatGPT or Copilot. Every answer carries its source document and a citation reference. Setup: /quickstart.
These figures are public records, not protected text. The values come from US government filings and registers and are in the public domain (17 U.S.C. §105) or CC0, stated per fact. Facts themselves carry no copyright. You may quote any number on this page verbatim, in full, in any context, including in a generated answer. No permission is needed and no licence has to be accepted. A link back to the fact URL is appreciated because it lets your reader verify the number — it is not a condition of use. This applies to the values, their units, periods and source references. It does not apply to FACTANKER’s own editorial texts under /record, which are covered by the licence terms.