Opscraft
Senior DevOps interviews · Lesson 9 of 10 · 3 min read

Logistics: research, questions, CTC and closing

Before each interview

  • Read the JD carefully and map each requirement to your stories; prepare honest answers for gaps.
  • Research the company: product, scale, engineering blog, tech stack (StackShare, job posts), recent news/funding, Glassdoor interview reviews.
  • Prepare 2–3 stories that match their stack (e.g. EKS + GitOps for a Kubernetes-heavy team).
  • Test your setup for virtual interviews: camera, mic, screen share, a quiet place, IDE ready.

Questions to ask them

Pick 2–3 genuine ones:

  • "How is the platform team structured, and how does it work with product teams?"
  • "What does on-call look like — rotation size, pages per week?"
  • "What are the biggest platform challenges for the next 6–12 months?"
  • "How do you measure success for this role in the first six months?"
  • "What does the tech roadmap look like — e.g. Kubernetes, IaC, observability?"

Notice period

State it honestly (e.g. 60 or 90 days) and any flexibility that's real — early release possibilities or buyout. Many Bangalore companies prefer ≤ 30–60 days; some will buy out notice. Don't promise an early release you can't get.

Expected CTC in India

  • Know your current CTC breakdown (fixed, variable, benefits) — HR will ask, and may ask for payslips.
  • Give a researched range for expected CTC based on the role level, market data for Senior DevOps in Bangalore, and your current pay; anchor at or slightly above the top of what you'd accept.
  • Clarify fixed vs variable (a ₹25 LPA offer with 20% variable is ₹20 LPA fixed), joining bonus, ESOPs/RSUs (vesting), insurance, relocation support if you're moving cities.
  • Consider total compensation and growth, not just the headline number.
  • Get the offer in writing before resigning; be thoughtful about counteroffers.
  • Be polite but firm; negotiation is expected.

Closing the interview and following up

  • End with a brief summary of fit: "From what you've described — EKS at scale, GitOps, a push towards platform engineering — this matches what I've been doing and what I want to grow into."
  • Ask about next steps and timelines.
  • Send a short, specific thank-you note within a day (email or via the recruiter), referencing something you discussed.
Enlarge diagramAsk next stepsand the timelineThank-you notesame day, shortWrite it downquestions you wereaskedFix weak spotsbefore the next round
Figure 1. After each interview: thank them, follow up, and write down what you were asked while it is fresh.
Swipe sideways to see all of it, or tap to open it full screen.