4_screening round.md

1. Can you tell something about yourself and your background?

I have [X years] of experience in [your field – e.g., DevOps, software development, cloud infrastructure, etc.]. I started my career as a [your first role] and gradually moved into more specialized roles where I handled [key responsibilities]. In my previous role at [company name], I worked extensively on [mention key technologies or projects], which helped me build strong expertise in [highlight key skills]. I'm passionate about [mention something related to the job role] and always look for opportunities to improve efficiency and solve real-world problems through technology.

2. What do you know about our company?

From my research, I understand that your company is a leader in [industry/domain]. You are known for [mention something notable – innovation, customer-centric approach, specific product or service]. I’ve seen that your recent focus is on [mention a current initiative or project if known], which really aligns with my interests. I admire the way your organization promotes [mention values, such as innovation, learning, work culture], and I’m excited about the possibility of being a part of such a team.

• Before every interview , you must do basic research about the company and be ready with few positive points about the company .

• Like Company Domain / Awards / Achievements / Values / work Culture ...etc etc .

3. How does your previous role align with this role?

In my previous role, I was responsible for [mention tasks or responsibilities that are relevant to the new role]. This involved working with [technologies or teams] to deliver [outcomes]. The current role you're offering focuses on [key responsibilities], which directly overlap with what I've already been doing. I also have experience in [mention any transferable skills], which I believe will help me contribute effectively from day one.

4. Can you explain something about your previous work?

Sure. In my last role at [company name], I worked on [specific project or product]. My responsibilities included [briefly list tasks like building pipelines, deploying applications, monitoring systems, etc.]. One of the key achievements was [mention a problem you solved or a measurable outcome]. This experience helped me improve my skills in [mention technologies or processes] and work effectively as part of a collaborative team.

5. What exactly does this role mean to you?

This role is a great opportunity for me to apply the skills I’ve gained and grow further in [mention your career goal]. I see it as a chance to contribute to meaningful projects, learn from talented colleagues, and take on new challenges. It aligns well with both my short-term and long-term goals, especially in terms of [career growth, technical exposure, leadership opportunities, etc.].

Screening call : Competency based

1. What skills do you have in terms of your experience?

I have hands-on experience in cloud infrastructure, primarily on AWS. I’ve worked on setting up and managing VPCs, EC2 instances, Auto Scaling, IAM roles, S3, RDS, and other core services. I’m also comfortable with automation using Terraform and CI/CD pipelines using Jenkins and Git. Additionally, I’ve used Docker and Kubernetes for container orchestration, and I’m familiar with monitoring tools like CloudWatch and Prometheus. I also follow best practices for security, availability, and cost optimization.

2. How will you tackle a situation when you made a mistake at work?

If I make a mistake, my first step is to take ownership and communicate it to the team or lead without delay. Then, I analyze what went wrong, fix the issue immediately if possible, and document the root cause to prevent it from happening again. For example, if I push a faulty script that causes deployment failure, I’d roll back, correct it, and improve the validation process to catch such issues earlier.

3. What will you do if you do not know about a tool and how to use it?

If I come across a tool I haven't used before, I start by understanding its official documentation and basic use cases. I also look at tutorials, community discussions, and examples. I believe in learning by doing, so I try it out in a test environment to get comfortable. I'm a quick learner and have picked up tools like Terraform and Prometheus the same way in the past.

4. Are you comfortable working on-call? Will that be a problem?

Yes, I’m comfortable working on-call. I understand that production issues or system outages may not always occur during work hours, and I’m okay with supporting critical situations when needed. I believe being on-call is part of owning the system reliability and customer experience.

5. What are your strengths and weaknesses?

Strengths:

• Strong problem-solving skills and ability to work under pressure.
• Quick learner when it comes to new tools or technologies.
• Good at automation and improving efficiency in repeated tasks.
• Clear communication and coordination with team members.

Weaknesses:

• Earlier in my career, I used to try solving everything on my own before asking for help. Now, I’ve learned to balance independence with collaboration by reaching out when needed.
• I sometimes tend to over-document processes, but I’ve realized that keeping it concise helps others better.
• Sometimes i over stretch