Technology Stack and Tooling Questions

Focuses on familiarity with common technologies and the rationale for choosing them. Includes knowledge of databases both relational and nonrelational, caching layers, message queues, containerization and orchestration, monitoring and logging tools, continuous integration and continuous delivery pipelines, and cloud versus on premise tradeoffs. Candidates should understand the role each tool plays in a system, when to adopt a technology based on system requirements and constraints, and tradeoffs in terms of operational complexity, cost, performance and team capability.

HardTechnical

129 practiced

Design a 30-60-90 day onboarding checklist and a short hands-on certification exercise for new engineers to become productive on your stack (Kubernetes, PostgreSQL, CI/CD pipelines, logging/observability). Include success criteria, mentor assignments, and time estimates for each stage.

Sample Answer

**30-60-90 Day Onboarding Plan (Engineering Manager view)**

**30 days — Learn & Observe (est. 4 weeks)**- Goals: access, context, small wins- Activities: account access, org chart, architecture walkthroughs (K8s, Postgres, CI/CD, logging), attend sprint ceremonies, shadow mentor- Mentor: Senior Engineer A (platform)- Time est.: 20% meetings, 60% self-study, 20% hands-on- Success criteria: can explain service topology, deploy a non-prod feature branch to dev cluster, run basic Postgres queries, open a ticket with reproducible steps

**60 days — Contribute & Automate (weeks 5–8)**- Goals: own small infra/task, improve automation- Activities: fix bug in deployment manifests, add CI test, tune monitoring alert threshold- Mentor: DevOps Lead B- Time est.: 50% coding/infra, 30% reviews, 20% learning- Success criteria: merged PR that updates Helm/manifest, adds pipeline job, and adds an observability dashboard panel

**90 days — Lead & Improve (weeks 9–12)**- Goals: independent ownership, mentor new joiner- Activities: design/implement a small reliability or performance improvement, run on-call shadow rotation- Mentor: Engineering Manager (you) + rotation with SRE- Time est.: 60% delivery, 20% mentoring, 20% strategy- Success criteria: leads a retrospective, delivers measurable improvement (e.g., 20% faster deploys or 30% fewer alerts)

**Hands-on Certification Exercise (2–3 days)**- Scenario: Add a new microservice "metrics-worker" - Create Dockerfile and Helm chart; deploy to dev namespace - Create CI pipeline job: build, test, push image, deploy - Provision Postgres schema and add migration; seed sample data - Add logging/metrics: Prometheus metric, Grafana panel, and an alert rule- Deliverables: PR with code, CI YAML, Helm chart; runbook with rollback steps; demo recording- Assessment: reviewer checklist (functioning deploy, passing pipeline, DB migrations applied, dashboard visible, alert fires on simulated fault)- Passing criteria: all items green, PR reviewed and approved by mentor, demo to team

Mentorship cadence: weekly 1:1 with assigned mentor; biweekly demo to team; manager check-ins at 30/60/90.

MediumTechnical

116 practiced

Your production cluster is experiencing intermittent CPU spikes that lead to request throttling. As an EM, describe the step-by-step investigation approach you would lead with the team using monitoring, tracing, and profiling tools. Include what dashboards, traces, and telemetry you would inspect and what short-term mitigations you might apply.

MediumTechnical

84 practiced

Your team uses Jira inconsistently: missing fields, poor sprint hygiene, and unreliable reporting. As an Engineering Manager, outline concrete steps to improve Jira usage: permission schemes, required fields, issue templates, sprint cadences, dashboard creation, and automation rules. Include change-management tactics to get buy-in.

EasyBehavioral

81 practiced

Describe how you would assess a candidate's practical familiarity with Docker and container basics during hiring. Propose specific interview tasks (take-home or live), red flags to watch for, and how you would calibrate different seniority levels (junior vs senior engineer).

MediumTechnical

91 practiced

Write a Kubernetes Deployment manifest (YAML) for a stateless service named 'webapp' with 3 replicas. Include CPU and memory requests/limits, liveness and readiness probes against /health, and a rollingUpdate strategy with maxUnavailable: 1 and maxSurge: 25%. Also define a ClusterIP Service exposing port 8080. (Provide a concise, correct manifest.)

Unlock Full Question Bank

Get access to hundreds of Technology Stack and Tooling interview questions and detailed answers.

Join thousands of developers preparing for their dream job.