Mid + Cloud Engineer (AWS)

As a Mid + Cloud Engineer (AWS) at Capco Poland, you will be responsible for managing cloud applications using various AWS services such as EC2, Lambda, and ECS. Your role involves automating cloud resources with Terraform, developing serverless applications, and monitoring app performance to ensure high availability. You will also collaborate with teams using Git and set up CI/CD pipelines to manage automated deployment processes.

To qualify for the Mid + Cloud Engineer (AWS) position at Capco Poland, candidates should have a minimum of 3-5 years of relevant experience with AWS services, proficiency in Terraform, and skills in JavaScript and TypeScript. Familiarity with container technologies like Docker and experience with CI/CD pipelines are also essential. A Bachelor’s degree in Computer Science or a related field, as well as good communication skills in English, are required.

Success as a Mid + Cloud Engineer (AWS) at Capco Poland requires strong technical skills in AWS services such as EC2, Lambda, and ECS. You should also be proficient in using Terraform for infrastructure automation and have programming skills in JavaScript and TypeScript. Additionally, skills in CI/CD tools and monitoring cloud performance are valuable, along with excellent organizational and communication abilities.

Yes! The Mid + Cloud Engineer (AWS) position at Capco Poland is completely remote, allowing you to work flexibly from anywhere in Poland. This provides you with the opportunity to collaborate with a global team, including members based in Canada, making for an engaging and diverse work environment.

As a Mid + Cloud Engineer (AWS) at Capco Poland, you will work on various projects involving the design, deployment, and maintenance of cloud applications and services. You will focus on automating infrastructure, developing serverless solutions, and ensuring best practices in security and performance monitoring, significantly contributing to our innovative solutions in finance and energy sectors.

When designing cloud solutions using AWS, I start by understanding the requirements and objectives of the project. I assess the needs for scalability, availability, and security before selecting the appropriate AWS services to fit those needs. Then, I focus on creating an architecture that minimizes costs while maximizing performance and reliability.

My experience with Terraform includes writing infrastructure as code to automate the deployment of cloud resources on AWS. I use Terraform to create and manage EC2 instances, VPCs, and security groups, ensuring consistent and repeatable deployments while also utilizing version control for managing configurations.

AWS ECS (Elastic Container Service) is a solution for running and managing containerized applications, while AWS Lambda is a serverless computing service that allows you to run code without provisioning servers. ECS is ideal for long-running services or microservices, while Lambda is best suited for event-driven architectures where applications respond to specific events or triggers.

To ensure the security of cloud applications, I implement best practices such as using IAM roles and policies to control access, enabling encryption for data at rest and in transit, and regularly updating security patches for services. I also conduct regular audits and monitoring to identify potential vulnerabilities.

For CI/CD, I leverage tools like Jenkins and AWS CodePipeline to automate our deployment processes. I ensure automated testing is integrated into the pipeline to catch issues early and employ rollbacks in case of deployment failures, thus enabling rapid and reliable delivery of updates to cloud applications.

To manage performance issues in cloud applications, I utilize monitoring tools like AWS CloudWatch to track performance metrics. If I notice any degradation, I analyze the logs and resource utilization, optimize code, adjust resource allocation, and sometimes scale the infrastructure dynamically to maintain performance levels.

I have hands-on experience with container technologies such as Docker for packaging applications into containers and AWS ECS for orchestrating those containers. This experience includes building Docker images, deploying services, and optimizing container performance for scalability and resource utilization.

One challenging cloud project involved migrating a monolithic application to a microservices architecture on AWS. It required careful planning to ensure minimal downtime, transforming the codebase, and rearchitecting for scalability. I collaborated with cross-functional teams and utilized AWS services like ECS and RDS, which resulted in improved application performance and fault tolerance.

I stay updated with the latest AWS features and services by regularly visiting the AWS documentation, attending webinars, and participating in online tech communities. I also follow industry blogs and forums that discuss cloud architecture and best practices to continuously evolve my knowledge and skills.

I primarily use Git for version control, as it allows easy collaboration and branching strategies for managing code changes effectively. I’m familiar with GitHub and GitLab for repositories, and I employ practices like pull requests and code reviews to maintain code quality and team collaboration.