EY Global Delivery Services ( EY GDS) DevOps Engineer interview questions & guide 2026

The following questions reflect patterns observed in recent interviews. While specific technical queries depend on your project team's stack, you should expect a rigorous focus on your hands-on ability to write scripts and manage cloud infrastructure.

Scripting and Automation

These questions test your proficiency in the languages that power modern DevOps workflows. You must be comfortable writing functional code under pressure.

• Write a Python script for the Fibonacci series.
• Write a Groovy script for declarative and scripted pipelines.

Preparation for this role requires a balance of theoretical knowledge and practical, "keyboard-first" skills. You should be prepared to demonstrate not just what you know, but how you apply it to solve infrastructure hurdles.

Role-related Technical Proficiency – You will be evaluated on your ability to write clean, functional code in languages like Python, Groovy, or YAML. Do not rely on high-level concepts; be ready to sit down and write actual syntax for pipelines, manifests, or scripts.

Cloud Infrastructure Expertise – Interviewers look for deep familiarity with cloud-native tools. You should be able to explain the "why" behind your architecture choices, such as why one service (e.g., Databricks) might be chosen over another (e.g., Azure Data Factory) to meet specific business requirements.

Problem-Solving and Logic – You will face scenarios where you must debug or design a system from scratch. Structure your answers by stating the goal, identifying the constraints, and explaining the step-by-step logic you would use to reach a solution.

The interview process at EY Global Delivery Services ( EY GDS) is designed to be efficient but highly demanding. Candidates typically navigate a sequence that begins with preliminary screenings followed by one or more rounds of technical deep dives. The pace is often rapid, with many processes concluding within two to four weeks.

You should expect the process to focus heavily on your practical skills. Because the work is highly specialized, interviewers often skip generalities to focus on whether you can handle the specific tooling used within their pipelines. Whether conducted remotely or in person, the rigor remains consistent: be prepared to demonstrate your technical competence through live coding or detailed architectural explanations.

This visual timeline illustrates the typical progression from initial screening to technical evaluation. Candidates should use this to gauge the intensity of their preparation; ensure that your technical stack knowledge is sharp before the first technical round, as these are often the "make or break" moments in the process.

Scripting & Coding

This is a non-negotiable area. You will be evaluated on your ability to automate tasks efficiently. Strong candidates write clean, modular code that considers edge cases.

• Python/Groovy – Ability to write logic-based scripts.
• YAML – Proficiency in writing configuration and manifest files.
• Example: You may be asked to write a script that automates a common CI/CD task or performs a mathematical operation to test your logical flow.

As a DevOps Engineer, your primary responsibility is to ensure the seamless flow of code from development to production. You will spend significant time designing and maintaining CI/CD pipelines, which requires a deep understanding of both the application code and the underlying infrastructure. Collaboration is key; you will work closely with development teams to integrate their applications into the cloud environment, ensuring that scalability, security, and performance are baked into the design from the start.

Beyond pipeline management, you will act as a guardian of infrastructure stability. This involves monitoring system health, managing cloud resource costs, and responding to incidents. You are expected to be the primary point of contact for infrastructure-related issues, meaning you must be comfortable debugging complex issues in a production-like environment and proposing long-term architectural improvements to prevent recurrence.

To be competitive for this position, you need a mix of deep technical expertise and the ability to work in a fast-paced, collaborative environment.

• Must-have skills:
  • Proficiency in Terraform for infrastructure as code.
  • Strong scripting skills in Python, Groovy, or Ruby.
  • Experience with Azure DevOps or AWS cloud platforms.
  • Hands-on experience with Kubernetes manifests and orchestration.
• Nice-to-have skills:
  • Experience with data-heavy tools like Databricks.
  • Knowledge of advanced networking configurations (DNS, VPC routing).
  • Ability to lead or mentor junior team members on automation best practices.

Q: How long does the interview process typically take? The process is generally fast, often concluding within two to four weeks. Be prepared to move quickly once you enter the pipeline.

Q: What is the most common reason candidates are not successful? The most frequent feedback relates to a lack of deep, hands-on experience with the required scripting languages or infrastructure tools. Theoretical knowledge is rarely enough; you must prove you can build and fix things.

Q: What should I focus on for the technical round? Focus on your ability to write scripts for CI/CD pipelines and manage cloud infrastructure. Practice your coding and be ready to explain your logic for complex architecture decisions.

Q: How can I best prepare for the behavioral aspects? Even in technical roles, EY Global Delivery Services ( EY GDS) values clear communication. Be ready to explain your past projects and how your technical interventions improved efficiency or solved a specific problem.

• Know your CV inside out: Interviewers will ask specific questions based on the technologies and projects you list. Be ready to defend every tool you claim to know.
• Prioritize hands-on practice: Do not just read documentation. Spin up a local environment or a cloud sandbox and practice writing actual Terraform code or Kubernetes manifests.
• Focus on the "Why": When explaining your past work, don't just state what you did. Explain why you chose a specific tool or approach over alternatives.
• Prepare for the environment: Whether remote or in-person, ensure your setup is ready to handle live coding tasks.

The DevOps Engineer position at EY Global Delivery Services ( EY GDS) is a high-visibility role that rewards technical precision and proactive problem-solving. By mastering the core areas of scripting, cloud infrastructure, and orchestration, you position yourself as a vital asset capable of driving the firm’s digital transformation. Focus your energy on the practical applications of your skills, as the interviewers will prioritize your ability to "do" over your ability to "describe."

You can explore additional interview insights, practice questions, and preparation resources on Dataford to further refine your strategy. With a structured approach and consistent practice, you can approach your interviews with the confidence needed to succeed.

This module provides an overview of the compensation landscape for this role. Candidates should interpret these figures as general benchmarks, noting that final offers are typically adjusted based on years of experience, specific technical certifications, and the complexity of the team you are joining.