DevOps Engineer Apps and Agents

Job Essence Platform Engineering is Sapiens' delivery-enablement discipline — the job responsible for building, automating, and continuously operating the CI/CD pipelines, environment provisioning tooling, and Internal Developer Platform (IDP) self-service components that let product engineering squads ship software continuously, safely, and without operational friction. The role treats the platform itself as a product with internal customers whose experience is continuously measured and improved, and that same enabling purpose carries directly into leading the pool responsible for that machinery — coordinating delivery priorities, developing the engineers who build and operate it, and setting the reliability discipline, IDP roadmap, and capability direction that keep Sapiens' SaaS release model dependable as the organisation scales. Whether expressed as direct platform craft or as team leadership and capability stewardship, the purpose stays the same: make continuous, reliable software delivery possible for the whole engineering organisation.

Inclusion Rationale Platform Engineering exists as a single job because its core purpose — making continuous, reliable software delivery possible for the whole engineering organisation — never changes; only the scope of ownership and the weight of leadership expressed against it grows, from hands-on pipeline ownership through reliability-standard, team, and capability-direction ownership. Consistent with the organisation's preference for one connected capability ladder over separate manager and expert tracks, delivery-enablement work is best governed as a single job so that career progression, compensation, and accountability for platform reliability and team leadership all track the same underlying motion rather than splitting across parallel job codes. Separating the platform's design-authority work into a dedicated architecture job protects the distinct, longer-horizon technical-standards mandate that this broader operating and leadership role does not carry.

Outcomes• Self-Service Delivery Enablement

• Platform Reliability & Error-Budget Discipline
• Internal Developer Platform Maturity
• Platform Team & Capability Leadership

Core technical requirements

• Strong depth in CI/CD pipeline infrastructure and deployment automation, including rollback.
• Hands-on experience building Internal Developer Platform (IDP) self-service components, such as environment provisioning and deployment.
• Experience with container orchestration.
• Observability configuration: monitoring dashboards, alerting rules, log aggregation and distributed tracing.
• Automate cloud environments with infrastructure as code so that they are repeatable, consistent, and easier to operate.
• Design and improve cloud-native CI/CD pipeline templates that give application teams consistent and reliable delivery by default..

Platform-as-a-product and reliability

• Treats the platform as a product with internal customers and improves IDP adoption and deployment reliability.
• Defines reusable platform patterns that standardize how multiple squads build, deploy and observe software.
• Knows reliability standards, SLOs and error budgets for a SaaS release model. 
• Operate and improve the enterprise secrets management platform, including access policies, credential rotation, application integration, and self-service features.
• Manage the artifact repository platform so that software dependencies are governed, traceable, and checked for risk

AI-Enabled Engineering

• Use AI to improve how the platform is built and      run, such as automating routine operational tasks, analysing pipeline      failures, and triaging security findings, with appropriate controls in      place.
• Apply AI coding assistants and agents to      accelerate the development of infrastructure as code, pipelines, and      automation, and review generated code for quality and security before      release.
• Deliver platform capabilities that allow      application teams to run AI workloads securely, including access to large      language model APIs, model hosting, and AI agent tooling such as MCP      servers

  Problem solving

• Solves ambiguous, cross-team delivery problems, such as redesigning release configurations or provisioning flows to cut recurring failures and toil.
• Builds durable automation that other platform engineers adopt, rather than fixing each recurrence personally.

Influence and collaboration

• Influences software engineers and adjacent engineering leads to adopt common patterns over local workarounds.
• Works with Software Engineering, Cloud Infrastructure Engineering, Site Reliability and Platform Architecture.
• Provides hands-on technical coaching and code review discipline and guides day-to-day work of other contributors on shared components.

Impact and ownership

• Owns a significant platform workstream, for example self-service deployment architecture, environment automation standards or observability-first delivery instrumentation.
• Has a track record of higher pipeline success rates and fewer platform-layer incidents.
• Has driven practices adopted across multiple squads.
• Accountable for reliability across releases, with local governance over how changes are introduced.

• Build, automate, and operate the CI/CD pipelines, deployment automation, and Internal Developer Platform (IDP) self-service components that let product engineering squads provision environments, deploy, and roll back software without requiring individual support.
• Design and maintain the observability infrastructure for the delivery layer — monitoring dashboards, alerting rules, log aggregation, and distributed tracing — giving the organisation the visibility needed to detect and resolve platform issues before they affect engineering velocity.
• Own the delivery commitments, reliability standards, and error-budget governance for the SaaS release model — setting SLO thresholds, arbitrating trade-offs between release velocity and platform stability, and reporting platform health transparently to engineering leadership.
• Coordinate with Software Engineering, Cloud Infrastructure Engineering, Site Reliability, and Platform Architecture to align delivery-automation standards, resolve cross-team dependencies, and keep the boundary between operating the platform and designing it clean.
• Lead the platform engineering pool's day-to-day delivery and on-call execution — sequencing priorities across roadmap and incident load, conducting structured feedback and growth planning, and coaching engineers toward greater technical and leadership depth as the sub-family's scope grows.
• Set the Platform Engineering capability strategy and workforce direction — determining the skills mix, tooling investment, and operating model needed to keep continuous delivery dependable, and making the hiring and resourcing decisions that keep the pool aligned to the organisation's scaling delivery needs.