Position: Senior DevOps Engineer
Category: DevOps
English level: upper
Years of experience: 7

Had no complaints on my soft or tech skills previously.
Always trying to suggest or recomend something new, if I think it will be usefull.
Sticking to best practices and IaC patters, at least trying, if possible :)
Looking for something new, preferably a product or a startup, US or EU based.

Currently working in a product company, where my main responsibilities are:
- Develop and maintain AWS infrastructure, mostly EKS, RDS, EC2
- Configure, update and troubleshoot CI\CD pipelines
- Configure and update logging and monitoring tools, such as ELK stack, Prom stack and CW
- Developing and maintaining deployment templates, mostly with Helm
- Supporting developers with any infrastructure or deploy related issues

Client:   AdTech company
Description:    Was hired to help with infra and cicd for a data pipelines project
Main techologies:   AWS, Gitlab, Athena, Kinenis, Kafka, ClickHouse, S3
Position:	Senior DevOps Engineer
Activities:	 Migrate microservices into k8s, deploy all of the needed data pipline tools, provide monitoring and alerting solutions and disaster recovery.

A bit of past experience and projects:
Client:	American telecom reseller
Description:	The main goal was to move client from hardcoded and manually created infrastructure to automated tools according with best practices and IaC patterns
Environments:	AWS, Github, Circleci
Position:	Senior DevOps Engineer, Release Engineer, SRE
Activities:		
	Implementing CI\CD process using Circleci, moving to Terraform, get rid of tons of bash scripts and hacks in favor of modern ways to build and deploy;
	Maintaining related AWS resources.;
	Migrating to ECS service instead of manual docker deploys on EC2 instances;
	Documenting and writing some policies and standards around monitoring, backups, releases, etc;
	Supporting legacy networks, ipsec tunnels\routes, and slowly moving them into SaaS from manually configured servers.
	Updating and cleaning the code repositories from unnecessary devops stuff and moving to centralized release control, writing Dockerfiles with best practices, etc;
	Costs optimization;

CI\CD for Spring-Boot applications, Kubernetes + AWS
Client:	American chain of luxury department stores 
Description:	The main goal was to gather different ops teams and streams into single Devops command with single standards for pipelines, templates, code-styles, global repo management instead of per-repo scripts and so on. 
Environments:	AWS mainly, Google Cloud, GKE
No Microsoft products or Azure
No on-call, sre, 24x7 support
Not interested to lead the team