• Own one of our core platform areas end-to-end: observability or CI/CD — you drive its architecture, reliability, and roadmap. • Drive technical initiatives end-to-end: gather requirements, write the design doc, decompose into tasks, implement, deliver to production, and own the operational health afterwards. • Drive clarity in ambiguous situations by defining requirements, assumptions, and next steps. • Design for reliability and scale: evolve the architecture of our platforms — topology, integration points, scaling approach, and reliability model. • Support developers: deploy and monitor applications on both on-premise servers and Kubernetes (Helm), troubleshoot builds and deploys, help teams with metrics, alerts, and logs; participate in chat duty in developer support channels. • Automate away toil: repetitive operations, provisioning, and maintenance should be codified, not performed by hand. • Investigate production incidents as the senior escalation point for your area: drive resolution, lead post-mortems, implement systemic fixes. Participate in on-call rotations and raise the bar for how on-call works. • Mentor less experienced engineers through design discussions, reviews, and pairing; catch debt-inducing shortcuts at the review stage. • Use AI in all aspects of day-to-day work: researching, troubleshooting, developing.

• Own one of our core platform areas end-to-end: observability (VictoriaMetrics, Grafana, Graylog / VictoriaLogs, fluent bit, exporters, alerting) or CI/CD (Jenkins scripted pipelines, Harbor, Nexus, build agents) — you drive its architecture, reliability, and roadmap. • Drive technical initiatives end-to-end: gather requirements, write the design doc, decompose into tasks, implement, deliver to production, and own the operational health afterwards. • Drive clarity in ambiguous situations by defining requirements, assumptions, and next steps. • Design for reliability and scale: evolve the architecture of our platforms — topology, integration points, scaling approach, and reliability model. • Support developers: deploy and monitor applications on both on-premise servers and Kubernetes (Helm), troubleshoot builds and deploys, help teams with metrics, alerts, and logs; participate in chat duty in developer support channels. • Automate away toil: repetitive operations, provisioning, and maintenance should be codified, not performed by hand. • Investigate production incidents as the senior escalation point for your area: drive resolution, lead post-mortems, implement systemic fixes. Participate in on-call rotations and raise the bar for how on-call works. • Mentor less experienced engineers through design discussions, reviews, and pairing; catch debt-inducing shortcuts at the review stage. • Use AI in all aspects of day-to-day work: researching, troubleshooting, developing.

• Own one of our core platform areas end-to-end: observability (VictoriaMetrics, Grafana, Graylog / VictoriaLogs, fluent bit, exporters, alerting) or CI/CD (Jenkins scripted pipelines, Harbor, Nexus, build agents) — you drive its architecture, reliability, and roadmap. • Drive technical initiatives end-to-end: gather requirements, write the design doc, decompose into tasks, implement, deliver to production, and own the operational health afterwards. • Drive clarity in ambiguous situations by defining requirements, assumptions, and next steps. • Design for reliability and scale: evolve the architecture of our platforms — topology, integration points, scaling approach, and reliability model. • Support developers: deploy and monitor applications on both on-premise servers and Kubernetes (Helm), troubleshoot builds and deploys, help teams with metrics, alerts, and logs; participate in chat duty in developer support channels. • Automate away toil: repetitive operations, provisioning, and maintenance should be codified, not performed by hand. • Investigate production incidents as the senior escalation point for your area: drive resolution, lead post-mortems, implement systemic fixes. Participate in on-call rotations and raise the bar for how on-call works. • Mentor less experienced engineers through design discussions, reviews, and pairing; catch debt-inducing shortcuts at the review stage. • Use AI in all aspects of day-to-day work: researching, troubleshooting, developing.

• Own one of our core platform areas end-to-end: observability (VictoriaMetrics, Grafana, Graylog / VictoriaLogs, fluent bit, exporters, alerting) or CI/CD (Jenkins scripted pipelines, Harbor, Nexus, build agents) — you drive its architecture, reliability, and roadmap. • Drive technical initiatives end-to-end: gather requirements, write the design doc, decompose into tasks, implement, deliver to production, and own the operational health afterwards. • Drive clarity in ambiguous situations by defining requirements, assumptions, and next steps. • Design for reliability and scale: evolve the architecture of our platforms — topology, integration points, scaling approach, and reliability model. • Support developers: deploy and monitor applications on both on-premise servers and Kubernetes (Helm), troubleshoot builds and deploys, help teams with metrics, alerts, and logs; participate in chat duty in developer support channels. • Automate away toil: repetitive operations, provisioning, and maintenance should be codified, not performed by hand. • Investigate production incidents as the senior escalation point for your area: drive resolution, lead post-mortems, implement systemic fixes. Participate in on-call rotations and raise the bar for how on-call works. • Mentor less experienced engineers through design discussions, reviews, and pairing; catch debt-inducing shortcuts at the review stage. • Use AI in all aspects of day-to-day work: researching, troubleshooting, developing.