Pedros builds its digital products in-house, and every one of them has to be hosted, deployed and paid for. The Platform and Engineering Manager is the deeply technical owner of that whole chain: the hosting infrastructure across AWS, Azure and Private Hosted Environments, the applications that run on it, how they are deployed, and the risks that come with running it.
The role leads the software development team and is expected to stay hands-on. It is a technical leadership role with people responsibility, and suits a senior engineer taking a first step into management.
The risks the role exists to control are cost, security, resource use and monitoring, consumption forecasting, and the ability to recover when something fails.
Responsibilities :
Hosting Infrastructure and Platform
Own hosting end to end for Pedros applications and internal systems across AWS, Azure and private hosting, from design and deployment to availability, backup and recovery, including the applications that run on it.
Make sure every application is deployed correctly for its hosted environment: configuration, dependencies, scaling, security and performance.
Decide where each workload should run and why, weighing cost, performance, security and data-protection requirements, within the standards set by the Head of Enterprise Technology and GRC.
Keep architecture, runbook and configuration documentation accurate and current.
Deployment and DevOps
Own container orchestration, environments and the CI/CD pipelines used to deploy Pedros software.
Automate provisioning and deployment with infrastructure-as-code so releases are repeatable, reviewed and reversible.
Set the technical release standard, including testing and rollback, and hold the team to it.
Build security checks (dependency, secrets and code scanning) into the pipeline instead of adding them at the end.
Change Control
Act as first approver for changes to hosted systems and deployments raised through the change control process run by IT Operations.
Assess technical risk, rollback and cost impact before approving, and decline or send back changes that are not ready.
Keep change records for deployments complete so they can be evidenced for audit.
Cost Awareness and Spend Motivation
Keep sight of the hosting and cloud budget and how it is being consumed against plan.
Identify where spend is needed, such as capacity, resilience, security tooling or platform changes, and motivate for it with a clear business case.
Design and deploy systems cost-effectively: choose the right size, service and hosting option for each workload and avoid over-provisioning.
Estimate the running cost of new deployments and vendor proposals before commitment, and raise cost concerns early.
Apply cost controls in every deployment across AWS and Azure: resource tagging, alerts, right-sizing and clean-up of unused resources.
Forecast consumption for compute, storage, data transfer and licences, and report cost trends, consumption against budget and options to reduce cost to the Head of Enterprise Technology and GRC.
Resource Monitoring and Capacity
Run monitoring, alerting and logging for hosted platforms and applications, with clear capacity and performance thresholds and escalation paths, and keep IT Operations informed so they can support users.
Plan capacity ahead of demand, such as promotions, new brands and peak trading periods.
Lead the technical response when hosted systems fail, and run post-incident reviews.
Business Continuity and Recovery
Maintain the classification of every system by criticality (for example, tiers based on business impact and data sensitivity), and keep the register current as systems are added or retired.
Keep each system's hosting, backup and failover design aligned with its agreed Recovery Point Objective (RPO) and Recovery Time Objective (RTO), and flag where the design cannot meet them.
Own the technical side of business continuity and disaster recovery planning: recovery runbooks, backup verification and scheduled restore and failover tests.
Report test results, gaps and remediation plans to the Head of Enterprise Technology and GRC. RPO and RTO targets are agreed with the business and the Head of Enterprise Technology and GRC, not set by this role alone.
Security Standards Implementation
Implement the security standards, policies and baselines set by the Head of Enterprise Technology and GRC across infrastructure, containers, pipelines and cloud.
Manage vulnerability and patch remediation, and keep evidence that controls are operating for audit and POPIA-related requirements.
Report control gaps and exceptions to the Head of Enterprise Technology and GRC. Exceptions to standards are not self-approved.
Vendor Relationship Management
Manage hosting, cloud, tooling and development-house vendors day to day: performance against SLAs, escalations and value for money.
Make sure vendors meet Pedros security and data-protection requirements, and provide technical input to vendor assessments and agreements.
Team and Technical Leadership
Lead the software development team: set priorities, agree objectives, and run performance conversations and appraisals.
Set engineering standards for code review, testing, documentation and deployment, and make sure they are followed.
Coach engineers and build a development path from Junior to Intermediate to Senior.
Manage workload, on-call cover for hosted systems and leave cover, and contribute to headcount planning.
Reduce single-person dependency on critical systems by documenting them and sharing ownership across the team.
NOTE:
This role designs, deploys and implements controls and owns delivery. It has sight of the cloud budget and motivates for spend, but does not own it. IT Operations owns user support and the change control process, and this role is the first approver of changes.
Policy, risk acceptance and assurance over those controls sit with the Head of Enterprise Technology and GRC. Changes to systems this role has built need an independent approver after this role's first approval.
Requirements
7+ years in infrastructure, DevOps, software or security engineering, with recent hands-on ownership of production systems.
Proven experience designing, building and running a production system end to end.
Working experience with AWS, Azure and private hosting environments, including deciding where workloads should run.
Experience running containerised workloads and CI/CD pipelines in production.
Practical secure-SDLC knowledge: dependency, secrets and code scanning in pipelines, and vulnerability triage.
Practical cost and capacity management: budgeting, forecasting consumption and controlling spend on cloud or hosted infrastructure.
Solid monitoring and alerting practice, and security fundamentals including vulnerability management.
Experience with backup, disaster recovery and business continuity: designing to RPO and RTO targets, classifying systems by criticality, and running recovery tests.
Experience leading or mentoring engineers, formal or informal. Formal line management is not required, but the appetite and aptitude for it are.
Experience working with vendors, including SLAs, renewals and cost.
Clear written and verbal communication, and the ability to explain technical risk and cost to non-technical stakeholders.