Hi A***y, I hope you’re doing well. I came across your profile and was impressed by your hands-on experience at P***s T***s,especially your work with Kubernetes, VMware Tanzu, ELK Stack, Prometheus, and Jenkins. I’m J*****e, an HR Recruiter at StrategyBrain, and we’re partnering with T***s S***s to find a Cloud DevOps Engineer. Your background in container orchestration and AWS infrastructure seems like a great fit. Would you be open to a brief chat to explore this role further? Looking forward to hearing from you. Best regards, J*****e HR Recruiter, StrategyBrain

Hi A***y, Great to hear from you! I’d love to set up a quick chat,are you available tomorrow (Tuesday) at 3:00 PM IST or Thursday at 4:00 PM IST? Let me know which slot works best, or feel free to suggest another afternoon time. In the meantime, here’s a brief overview of the Cloud DevOps Engineer role at T***s S***s and how it aligns with your background: 1. Key Responsibilities • Design, implement, and maintain CI/CD pipelines with Jenkins and Git to streamline deployments. • Deploy and manage containerized applications on Kubernetes and VMware Tanzu for high availability and scalability. • Architect and manage AWS infrastructure (provisioning, autoscaling, cost optimization). • Build and configure monitoring/logging solutions using ELK Stack, Prometheus, and Grafana. • Collaborate with development and operations teams to troubleshoot performance issues and implement best practices. 2. Why You’re a Fit Your hands-on experience with Kubernetes, AWS, ELK Stack, Jenkins and VMware Tanzu directly matches our tech stack,this role will let you leverage your existing skills while taking ownership of critical cloud-native initiatives. 3. Career Growth & Impact • Clear path to Senior DevOps Engineer or Cloud Architect roles as you drive our cloud strategy. • Opportunity to influence tooling choices and best practices across the organization. • Dedicated learning budget and support for certifications to keep your skills sharp. 4. Resources & Benefits • Collaborative, mid-sized team with cross-functional mentorship. • Competitive salary, performance bonuses, and stock-option opportunities. • Flexible PTO, health coverage, and access to training programs. Please let me know which time works for our call and if you have any questions about the role or company. I’m looking forward to speaking with you! Best regards, J*****e HR Recruiter, StrategyBrain

Hi A***y, Great questions. 1. Remote Work T***s S***s is a remote-first organization. You can work fully remotely, with optional in-person meet-ups or team offsites in Mumbai if you’d like, but there’s no mandatory daily office attendance. 2. Salary Range For this Cloud DevOps Engineer role, the budgeted base salary is INR 15,00,000,25,00,000 per year, plus performance bonuses and stock-option opportunities. I hope this gives you a clear picture. Looking forward to our chat on Thursday at 4:00 PM IST,please let me know if there’s anything else you’d like me to cover! Best, J*****e HR Recruiter, StrategyBrain

Hi A***y, Great questions,happy to provide more detail: 1. Team Size & Structure - You’ll join a tight-knit Cloud & DevOps group of about eight engineers, led by our Cloud Infrastructure Manager. - The team blends senior and mid-level Cloud Engineers with an SRE specialist. - We operate in a flat, agile setup: you’ll own projects end-to-end and collaborate closely with backend developers, QA, security and product stakeholders. 2. Stock-Option Vesting - At joining you receive an initial option grant (amount based on level/experience). - Vesting runs over four years with a one-year cliff (25% vests after 12 months, then the balance vests monthly over the next 36). - We also offer performance-tied refresh grants on an annual basis. Let me know if you’d like any additional color before Thursday. Looking forward to our discussion at 4:00 PM IST! Best, J*****e HR Recruiter, StrategyBrain

Hi A***y, Great question,here’s a high-level view of how on-call and incident response works on our Cloud & DevOps team: 1. Rotation Model • We run a weekly primary/secondary on-call rota among the eight engineers. Each person typically takes one week as primary and one week as secondary every two months. • The primary engineer owns initial triage and remediation; the secondary steps in if the primary is unavailable or the issue escalates. 2. Alerting & Tools • We use PagerDuty for alerting (integrated with CloudWatch, Prometheus, ELK, etc.), with notifications sent via Slack and SMS as needed. • All runbooks and escalation paths live in Confluence,these are regularly reviewed and updated after each incident. 3. Incident Workflow • When an alert fires, the primary on-call acknowledges it within 5 minutes, consults the relevant runbook, and begins remediation. • If the issue can’t be resolved within 30 minutes, it’s escalated to the secondary on-call or to our SRE specialist, depending on severity. • Major incidents trigger a Zoom “war room” with stakeholders (Dev, QA, Security) to collaborate in real time. 4. Post-Incident Practices • After resolution, we run a blameless postmortem within 48 hours to capture root causes, action items, and preventive measures. • Learnings are shared in our weekly team sync to continuously improve our processes. I hope that gives you a clear picture. Let me know if you’d like more detail before our call. Looking forward to chatting on Thursday at 4:00 PM IST! Best, J*****e HR Recruiter, StrategyBrain