Bizops Engineer

• Support end-to-end availability, monitoring, and performance of critical payment platforms.
• Execute operational processes to ensure platform health and stability.
• Participate in capacity checks, readiness validations, and environment monitoring.
• Actively manage and coordinate incident triage and resolution.
• Serve as incident commander driving medium to high-severity incidents.
• Ensure timely updates, accurate impact assessment, and appropriate escalation.
• Contribute to root cause analysis with clear identification of actions and ownership.

• Participate in highlighting gaps and defining test cases required for a change in lower environments and validate lower environment test completeness.
• Ensure adherence to change governance processes (test case reviews, checklists, approvals, rollback readiness).
• Engage in creating change plans and support execution of production changes, deployments, and validations.

• Perform hands-on troubleshooting across:
• Application behaviour and dependencies.
• Infrastructure components (compute, network, storage).
• Database and performance issues.
• Collaborate with engineering, infrastructure and other technical teams to isolate and resolve issues efficiently.

• Improve system health monitoring using observability tools and alerts.
• Identify gaps in alerting and contribute to improving quality of alerting and dashboards.
• Ensure proactive detection of anomalies using observability tools.

• Contribute to automation initiatives to reduce toil and errors.
• Identify repetitive operational tasks and drive improvements.
• Support implementation of Dev Ops best practices.
• Leverage AI-driven tools to improve monitoring, incident detection, and operational efficiency, enabling faster troubleshooting and reduced manual effort in day-to-day operations.

• Work closely with engineering, program teams, and external partners during incidents and changes.
• Provide structured updates to stakeholders with clarity and consistency.
• Highlight operational and platform risks including test coverage gaps, infrastructure constraints, dependency risks.
• Escalate issues proactively and support mitigation tracking.
• Support onboarding and guidance of junior team members.
• Contribute to runbooks, documentation, and knowledge sharing.
• Drive consistency in execution and adherence to operational standards.

• Deep Operational Ownership (Built to Run Mindset)

A successful Lead SRE Engineer is fully accountable for the operational health of their program, not just responsive to incidents.

• Monitoring, alerting, and dashboards that reflect real customer impact.
• Emergency response and incident leadership, including clear communications and post-incident follow‑ups.
• Capacity planning and readiness aligned with product and business growth.
• Change management discipline, ensuring safe, compliant releases.

A Lead SRE Engineer is expected to operate at system dependency level, not just ticket or tool level.

• Have a strong understanding of application business logic and workflows.
• Have a clear grasp of upstream/downstream dependencies.
• Expertise in observability (alerts, dashboards, synthetic monitoring).
• Ability to drive automation to reduce manual toil and recurring issues.
• End to End ownership of tasks and activities.

Beyond technical skill, Leads are distinguished by how they lead during high‑severity situations.

• Takes command of major incidents, not waiting to be asked.
• Maintains calm, structured communication with engineering, product, and leadership.
• Ensures clear ownership of actions, timelines, and follow‑ups.
• Drives root cause analysis and systemic fixes, not just recovery.

A successful Lead SRE prevents incidents more than fight them.

• Identifies systemic risks before they become outages.
• Pushes for design, monitoring, or process improvements.
• Challenges “tribal knowledge” by insisting on documentation and runbooks.
• Drives improvements aligned with operational maturity models.