# Interview Preparation ### Tell me about your experience ? I spent 3.3 years at devopsdelight Innovations as a DevOps engineer, Working on an e-commerce platform. I automated infrastructure with Terraform, deployed microservices on AWS Kubernetes, and set up GitHub Actions pipelines for zero-downtime releases. One highlight was optimizing our AWS Free Tier usage, scaling to 100 users without cost. It’s now live at , and I’m excited to bring this expertise to a fast-paced startup.” ### what are your roles and responsibilities ? * *Role*: Designed, built, and maintained a scalable e-commerce microservices platform serving user management, product catalog, order processing, and recommendations *Responsibilities*: * Automated infrastructure provisioning with Terraform and Ansible across AWS EC2 and Kubernetes clusters, reducing setup time by 70%. * Implemented CI/CD pipelines using Jenkins and GitHub Actions, achieving zero-downtime deployments for 4 microservices (Java, Node.js, Python, Go). * Deployed and managed a production-grade Kubernetes cluster on AWS, integrating Horizontal Pod Autoscaling (HPA) to handle traffic spikes up to 100 concurrent users. * Secured the platform with Vault for secrets, Let’s Encrypt for HTTPS, and Kubernetes RBAC/Network Policies, ensuring compliance with security standards. * Set up monitoring with Prometheus, Grafana, and ELK, reducing incident response time by 50% through proactive alerts and dashboards. * Collaborated with developers via Jira and GitHub PRs, enforcing code quality with SonarQube and Trivy scans *Achievements*: * Successfully deployed the app to , serving as a proof-of-concept for 500+ internal users. * Optimized resource usage on AWS Free Tier, maintaining $0 operational cost for 12 months. * Documented processes and led a demo, improving team onboarding by 30% ### How do you handle pipeline failures during review? * If the pipeline fails—say, a test flakes—I check the GitHub Actions logs. If it’s a false positive, I rerun it. If it’s real, like a SonarQube failure, I comment in the PR with the issue link and work with the dev to fix it. We don’t merge until it’s green ### How do you assign reviewers dynamically? * We use GitHub’s CODEOWNERS file to suggest reviewers based on file paths—e.g., /user-service/\*\* @java-team. Devs pick from that pool, and I’m auto-added for DevOps checks. It’s flexible but ensures the right expertise. For urgent PRs, I ping specific folks in Teams ### What if a reviewer misses something? * We rely on multiple layers—automated scans catch most issues, and two reviewers reduce human error. If something’s missed, like a logic bug, our E2E tests in UAT or monitoring in prod flag it. Last time, a missed edge case crashed a pod; I caught it in Grafana, rolled back, and added a test to the pipeline ### How do you ensure SonarQube catches all issues? * SonarQube’s rules are customizable—I tuned them to catch common issues like SQL injection or null pointers, based on OWASP guidelines. It’s not foolproof, so we pair it with Trivy for security and manual reviews for context. If something slips through, our ELK logs and Prometheus alerts catch it in prod, and I update the ruleset
--- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://charan-techjourney.gitbook.io/charan-techjournal/50-days-of-devops-ecommerce-microservices/project-daily-tasks/interview-preparation.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.