Scribd
Upload
31 views

AWS DevOps interview

This document is a preparation guide for candidates interviewing for an AWS DevOps engineer position at Capgemini Engineering. It outlines the structure of the technical interview, which includes an introduction, practical tasks, and evaluations of computer science and technology skills, lasting approximately 90-120 minutes. Key topics for discussion include AWS services, infrastructure as code, containerization, CI/CD concepts, and monitoring/logging practices.

Uploaded by

georgesuper2
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
31 views

AWS DevOps interview

This document is a preparation guide for candidates interviewing for an AWS DevOps engineer position at Capgemini Engineering. It outlines the structure of the technical interview, which includes an introduction, practical tasks, and evaluations of computer science and technology skills, lasting approximately 90-120 minutes. Key topics for discussion include AWS services, infrastructure as code, containerization, CI/CD concepts, and monitoring/logging practices.

Uploaded by

georgesuper2
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 5

HOW TO PREPARE

FOR A TECHNICAL
INTERVIEW AT
CAPGEMINI
ENGINEERING EE

1
https://capgemini-engineering.com.ua/
DevOps development
AWS DevOps

Dear Candidate,

The key to a successful interview is advanced preparation. It helps to gain self-assurance


and feel confident during the interview. Therefore, we have created this guide to help you
prepare for an AWS DevOps engineer interview.

The technical interview is an online/offline meeting with engineers with related


specialization i.e., interviewers. The goal of this part is to evaluate your technical skills.
The interview has a recommended duration equal to 90-120 minutes (about 1.5-2 hours,
but it can vary on a case-by-case basis) and consists of the following blocks:

▪ Introduction (5-15 minutes).


▪ Practical task (30 minutes).
▪ Computer science & technology evaluation – oral question interview form (60-
75 minutes).

Please note, that some interview questions are more computer science-oriented than
others, but they are very important and exemplary for technical evaluation because we
need to check your engineering mindset.
The interviewer can independently initiate the transition to the next block of questions in
order to pass all stages of the technical interview on time.
Feedback on questions and practical cases will be provided to you as feedback on the
interview.

You can expect the following aspects to be discussed:

AWS:
Your general understanding of networking and AWS networking services, load
balancing, network security and AWS compute services will be evaluated. In
addition, you will be asked about AWS cloud storage options and capabilities, AWS
identity and access management, encryptions, and secret management.
Specifically, the following topics will be covered:

▪ VPCs, Subnets, Elastic IP Address, gateways, route


tables, security groups, NACL, Route53, Load Balancers
Networking ▪ Load Balancers limitations, VPC peering, endpoints,
transit gateway, AppMesh, API Gateway
▪ CloudFront, Shield, WAF, Network Firewall, multi-

2
https://capgemini-engineering.com.ua/
account networking
▪ EC2: provisioning, AMI, types and cases
▪ EC2: metadata, instance profile, launch
Compute template/config, Auto Scaling groups
▪ Containers: ECS, EKS, Fargate
▪ Serverless: Lambda
▪ S3, EBS, RDS
Storage and ▪ EFS, FSx, instant storage, S3, EBS, RDS, DynamoDB,
Database ElastiCache
▪ Storage gateways, Snowball, RDS, Redshift
▪ IAM, KMS, CloudTrail, AWS certificate manager, AWS
secrets manager, Parameter store, Trusted Advisor
Security
▪ AWS organization, AWS SSO, AWS Cognito, account
limits

Infrastructure as code:

Your understanding of the value of lac, knowledge of how to properly organize it


in combination with GitOps, and your experience with at least one IaC tool (e.g.,
Terraform) will be checked. You should understand CM purpose and your
experience with at least one CM tool will be verified.
Specifically, the following topics will be covered:

▪ IaC pros/cons, approaches


▪ GitOps, experience with IaC tools: Terraform, Cloud
Infrastructure as specific (AWS CloudFormation, GCP Deployment
a code (IaC) Manager, Azure Stack)
▪ external management of resources in restricted
environments
▪ CM purpose and pros/cons, CM approaches
Configuration ▪ experience with CM tool at least: Ansible, Salt, Chef,
Management (CM) etc.
▪ dynamic infrastructure configuration

Containerization and orchestration:


Your containerization knowledge and experience will be checked. You will be asked
about container orchestration concepts and your experience with tooling will be
evaluated.
Specifically, the following topics will be covered:

▪ containerization purposes, pros, and cons, container


image
Containerization
▪ container image building best practices, containerized
app configuration

3
https://capgemini-engineering.com.ua/
▪ container internals, capabilities, runtimes
▪ container orchestration purpose, benefits, Docker
Compose
▪ Kubernetes: pod, workload resources, service/ingress,
assigning pods to nodes, storage, Helm, deployment
Container
strategies
orchestration
▪ Kubernetes: node isolation/restriction, auto scaling,
infrastructure on demand, networking, RBAC,
networking policies and service mesh, requirements to
applications running on K8s

CI/CD/CT:
Be ready to show your understanding of CI/CD concepts and the role of CT role in
CI/CD process. Be ready to demonstrate your scripting skills (experience with one
of Bash, PowerShell, Python, etc) and tooling (Linux/Windows).
Specifically, the following topics will be covered:

▪ general idea, benefits, CI systems, Artifacts, artifact


registry, VCS
Continuous ▪ pipelines, runners/executors, pipeline triggers,
Integration (CI) dependency management
▪ branching strategies, versioning, language-specific
build tasks
Continuous ▪ concepts, deployment targets
Delivery / ▪ environment types, CD tools and systems
Deployment (CD) ▪ deployment strategies
▪ purpose of CT, test types, functional testing, non-
Continuous
functional testing
Testing (CT)
▪ infrastructure testing
▪ pipes, standard data streams, grep/sed/awk
Scripting
▪ language specific knowledge, exit codes

Monitoring & logging:


Your understanding of metrics, how to collect, store and use them for monitoring
will be checked. You can be asked about logging and log processing as well as your
experience with tooling. Make sure that you are aware of distributed tracing
process.
Specifically, the following topics will be covered:

▪ metric, APM, alerting


Metrics & ▪ Tooling: Grafana/Datadog/Prometheus/Any Cloud
Monitoring Native systems
▪ SLI, SLO, SLA, OpenTelemetry

4
https://capgemini-engineering.com.ua/
▪ purpose of logging and log processing and application
Logging & Logs instrumentation
processing ▪ Tooling: ELK, Datadog, cloud specific
Distributed ▪ purpose of distributed tracing
tracing ▪ Tools: Sentry, OpenTelemetry, Newrelic, cloud specific

We hope you will find this guide useful!

Thanks for your interest in joining Capgemini Engineering Eastern Europe! We’re looking
forward to speaking with you.

5
https://capgemini-engineering.com.ua/

You might also like