About the job
Full details, eligibility and the selection process are available on the company's careers page.
Cognizant
Java Developer(AWS)
Posted 1 week ago
- Experience
- 0-3 years
- Location
- Chennai
- Job type
- Full-time
- Work mode
- Hybrid
Interview prep · DevOps / Cloud Engineer
How to prepare for this interview
DevOps and cloud interviews are hands-on. Expect questions on Linux, networking, CI/CD pipelines, containers and at least one cloud provider, plus scenario questions about outages. Interviewers value people who automate and who stay calm when things break.
Typical selection process
-
1
Screening or online test
Linux commands, networking basics and scripting MCQs.
-
2
Technical round 1
Linux, Git, CI/CD, Docker and a scripting task in Bash or Python.
-
3
Technical round 2
Kubernetes, cloud services (AWS, Azure or GCP), Terraform and incident scenarios.
-
4
Managerial / HR
On-call experience, team practices and offer discussion.
Rounds vary between companies. Cognizant may combine or skip some of them.
Skills to brush up on
- Linux administration
- Bash or Python scripting
- Git and branching strategies
- CI/CD (Jenkins, GitHub Actions, GitLab CI)
- Docker
- Kubernetes
- AWS, Azure or GCP
- Terraform or another IaC tool
- Monitoring (Prometheus, Grafana, CloudWatch)
Likely interview questions
Open a question to see what the interviewer is looking for.
01 What is the difference between a container and a virtual machine?
How to answer:
VMs virtualise hardware and run a full guest OS; containers share the host kernel and isolate processes, so they start faster and use less memory.
02 How do you reduce the size of a Docker image?
How to answer:
Use a slim or distroless base image, multi-stage builds, a .dockerignore file, and combine layers while cleaning package caches.
03 Explain Pods, Deployments and Services in Kubernetes.
How to answer:
A Pod runs one or more containers. A Deployment manages replicas and rolling updates. A Service gives the Pods a stable network endpoint.
04 Walk me through a CI/CD pipeline you have built.
How to answer:
Trigger, build, test, scan, build the image, push to a registry, deploy to staging, approval, deploy to production, and how you roll back.
05 What is Infrastructure as Code, and why does Terraform keep a state file?
How to answer:
IaC means infrastructure is defined in versioned code. The state maps your code to real resources; store it remotely with locking for team use.
06 Blue-green or canary deployment: what is the difference?
How to answer:
Blue-green switches all traffic between two full environments. Canary sends a small percentage of traffic to the new version first and increases it gradually.
07 Which Linux commands do you use to check CPU, memory, disk and open ports?
How to answer:
top or htop, free -h, df -h and du -sh, and ss -tulpn or netstat. Mention journalctl and tail -f for logs.
08 How do you manage secrets in pipelines and clusters?
How to answer:
Never commit them. Use the CI secret store, a cloud secrets manager or Vault, and Kubernetes secrets with encryption at rest and RBAC.
01 The website is down at 2 AM. What are your first five steps?
How to answer:
Confirm the impact, check monitoring and recent deployments, look at logs and resource usage, roll back if a deploy caused it, then communicate and write a post-mortem.
02 A Pod is stuck in CrashLoopBackOff. How do you debug it?
How to answer:
Run
kubectl describe pod and kubectl logs --previous, then check the image, environment variables, config maps, probes and resource limits.
03 Disk usage on a production server hit 95%. What do you do?
How to answer:
Find the large directories with
du, clear or rotate logs safely, check for deleted files still held open, then add alerts and log rotation so it does not recur.
01 Tell me about yourself.
How to answer:
Keep it under two minutes: who you are, what you have built or studied that fits this role, and why you applied here. Skip personal details unless asked.
02 Why do you want to join our company?
How to answer:
Mention something specific: a product they ship, the tech they use, or the kind of customers they serve. Generic praise ("good brand, good growth") sounds rehearsed.
03 What are your strengths and weaknesses?
How to answer:
Back each strength with a short example. For the weakness, pick a real one that does not block the role and say what you are doing about it.
04 Are you comfortable with the location, shift timings and work mode?
How to answer:
Answer honestly. If you have a constraint, say it now rather than after the offer, and mention any flexibility you do have.
05 Do you have any questions for us?
How to answer:
Always ask one or two: what the first 90 days look like, how the team is structured, or how performance is reviewed. Avoid asking only about leave and salary.
06 Walk me through your final year project.
How to answer:
Explain the problem, your exact contribution, the tech you chose and why, and one thing that went wrong and how you fixed it. Interviewers dig into this, so know every line you claim.
07 You have no work experience. Why should we hire you?
How to answer:
Point to proof of effort: projects, internships, certifications, open source or competitive coding. Show that you learn fast and can take feedback.
08 Are you willing to sign a service agreement or relocate?
How to answer:
Many campus and fresher roles include a bond or training period. Read the terms before the interview so you can answer clearly.
09 Where do you see yourself in three to five years?
How to answer:
Show ambition within the field: owning features, mentoring juniors, going deeper in a technology. Avoid saying you plan to leave for higher studies soon.
Resume tips for this role
- Show automation impact: deployment time cut from hours to minutes, or uptime improved.
- List cloud services you have actually used (EC2, S3, RDS, EKS), not just the provider name.
- Cloud certifications such as AWS Solutions Architect Associate or CKA carry real weight here.
- Link a GitHub repo with Terraform or a CI pipeline you wrote.
Free resources to study
This guide is written by the JOB_SPOT_360 team from common interview patterns for this kind of role. It is not provided by Cognizant, and the actual questions may differ.
Frequently asked questions
Can freshers apply for the Java Developer(AWS) role at Cognizant?
Yes. The role accepts candidates with 0-3 years of experience, so freshers can apply.
What is the salary for this job?
Cognizant has not disclosed the salary. You can ask about it during the HR round.
Where is the job located? Is it remote?
This is a hybrid role based in Chennai, mixing office and work-from-home days.
What skills are required for this job?
The listing mentions Java, Python and AWS. Expect interview questions on each of them.
What is the last date to apply?
No deadline is listed. Openings like this can close once enough applications come in, so apply early.
How do I apply?
Select "Apply on company site" on this page. It opens Cognizant's official careers page, where you submit your application. JOB_SPOT_360 does not collect applications and never charges a fee.