Architecture - You will be responsible for high-level system design and architecture for the product, driving architectural
change/evolution whenever and wherever needed.
Hands-on coding – This is a hands-on role. You will be expected to deliver web APIs, features & functionalities by writing
clean code every day.
Troubleshooting and monitoring – You will be expected to resolve bugs and troubleshoot the system as and when
required. You will also be expected to set up monitoring using tools like Prometheus and Grafana
Expectations:
Experience – You must have at least 5 years of experience.
.NET stack + web API expertise – You must have worked extensively with the .NET stack, having worked with C#, .NET
Core (6.0 and above), Entity Framework, SQL Server, and one cloud ecosystem (preferably AWS). You must also be proficient in writing well-designed & efficient web APIs.
Good to know - Experience with AWS RDS, S3, and Lambda will be great to have. Experience in setting up monitoring
using tools like Prometheus and Grafana will be great to have.
Engineering practices – You must be a follower, and custodian, of the best engineering practices. You must know how to
design secure, performant, usable, maintainable and efficient RESTful APIs. You must have implemented TDD and SOLID principles in your daily code.
Excellent communication skills – You need to articulate your points clearly and assertively so that you can get the team
and all the stakeholders on the same page w.r.t the requirements, the roadmap, and the progress. You need to be a great listener and represent not just your team, but Caizin in front of the stakeholders.
Experience with Agile projects – You must have worked extensively with distributed, cross-functional agile teams. You
must be familiar with agile rituals and be a custodian of the same.
This page is for Indian job seekers preparing for cloud engineer, DevOps, backend and solutions architect roles that list AWS as a skill, whether you are a fresher with a first certification or an experienced engineer moving into a senior role. It covers 60 questions in three levels: core services and concepts, then design and configuration choices for one to three years of experience, and finally scenario, security, cost and troubleshooting questions asked in senior rounds. Read each answer, explain it aloud in your own words, and try the CLI commands in a practice account with a billing alert set.
Questions you may be asked
What is the difference between an AWS Region and an Availability Zone?
Explain the AWS shared responsibility model.
What is Amazon EC2, and how do you read an instance type name like m7g.large?
What is Amazon S3, and what are its main storage classes?