some cleanup and todos
This commit is contained in:
Nikolai Rodionov
@ -1,13 +0,0 @@
|
||||
Hi! I'm a young DevOps engineer with 3++ years of hands-on experience in IT. I had experience in several IT areas, and I understand how things may work for different teams, which is important for implementing the DevOps philosophy in the company.
|
||||
After working in a QA engineer position, I understand how to test any solution and describe test cases.
|
||||
Also, I'm not afraid of experiments when it comes to solving unusual problems and using new technologies. I know how things work on bare-metal and in the cloud, so I may help with migrating to the cloud and vice versa.
|
||||
Also, I'm thinking about consequences, and I'm ready to take responsibility for every decision I've made.
|
||||
I've got a will to learn, so I won't be stuck with old-fashioned technologies claiming they are the best fit if there are better alternatives. And I'm never saying that it's impossible to solve any problem unless it is.
|
||||
|
||||
When should you pay attention to my CV?
|
||||
- You working with Kubernetes
|
||||
- You need to improve/refactor/create/support CI/CD pipelines
|
||||
- You need help with docker
|
||||
- You're migrating to the cloud
|
||||
- You need to support legacy application
|
||||
- You need help with supporting micro-services application
|
||||
@ -1,105 +0,0 @@
|
||||
# Nikolay Rodionov
|
||||
```
|
||||
St. Petersburg, Russia
|
||||
|
||||
- phone: +79996690458
|
||||
- email: nicrodionov@gmail.com
|
||||
```
|
||||
---
|
||||
## About me
|
||||
|
||||
|
||||
I'm an engineer with 3++ years of hands-on experience in different IT areas: from writing e2e auto-tests in JS to setting up a Kubernetes cluster from scratch on bare metal.
|
||||
Just over a year ago, I've completely understood that being a system engineer is what I truly like to do.
|
||||
|
||||
A short list of things I love doing
|
||||
- Setting up, managing, and supporting K8s clusters
|
||||
- Writing scripts to automate manual actions (Go, Perl, Bash, or Ansible)
|
||||
- Linux administrating
|
||||
- Working with containers
|
||||
- Setting up CI/CD (Gitlab-CI, GitHub Actions)
|
||||
- Resolving incidents and troubleshooting problems
|
||||
- "Everything as code (from QA to Infrastructure)"
|
||||
|
||||
## Expirience
|
||||
### Itigris: _devops engineer/qa automation_
|
||||
> 07.2019 - until present
|
||||
I have started as a QA automation and then have moved to the system engineering
|
||||
1. As a QA Automation
|
||||
- Creating a codebase for E2e tests (**Java**, **NodeJS**) from scratch.
|
||||
- Creating and supporting e2e and integration tests **Gitlab C**I pipeline with dynamically starting **Selenoid** server
|
||||
- Automating basic actions with **bash**
|
||||
- Working a lot with **Docker**, **docker-compose**, and **Dockerfiles**
|
||||
- And a bit of SQL quering (**Postgres**)
|
||||
2. As a System Engineer
|
||||
- Writing scripts (**Go** and **Bash**)
|
||||
- Supporting and setting up several **k8s** clusters (**AWS EKS**)
|
||||
- Supporting services running in **docker** on **ec2** instances
|
||||
- Supporting **ec2** instances too
|
||||
- Troubleshooting incidents (**k8s**, **nginx**, **aws**)
|
||||
- Disaster recovery (**k8s**, **docker**)
|
||||
- Maintaing the process of "microservicing" the old monolith
|
||||
- Deploying services written in Java, JS and Python
|
||||
- And a bit of SQL administrating (**Postgres**)
|
||||
- Setting up an infrastructure with **Terraform**
|
||||
### Etersoft: _engineer_
|
||||
> 03.2017 - 06.2019 officially (and until present as a side project)
|
||||
I became as a "handyman" and was learning how to do anything in this company.
|
||||
- Lots of **Linux**, containers (**docker**, cri-o), and virtualization (VirtualBox, Proxmox)
|
||||
- A bit of networking (**IPtables** and UFW)
|
||||
- A bit of **Kubernetes** (setting up and supporting little bare-metal clusters from scratch)
|
||||
- Setting up virtual machines with **Vagrant** (VirtualBox and a bit **Docker**) and **Ansible**
|
||||
- Setting up **Nginx** and **Envoy**
|
||||
- **Bash** and **Perl** scripts for automating basic actions
|
||||
- Create a codebase for E2e tests (**NodeJs** and the plain **Selenium**) from scratch.
|
||||
- Create and support e2e tests **Gitlab CI** pipeline with a small static selenium server
|
||||
- A bit of frontend development (**ReactJS**) so I have a basic understanding of HTML and CSS too
|
||||
- A bit of SQL (**MySQL**)
|
||||
|
||||
## Skills
|
||||
- Kubernetes
|
||||
- Kubeadm
|
||||
- EKS
|
||||
- Docker, Containerd, Cri-O
|
||||
- Kubectl, Helm, Kustomize
|
||||
- Ingress Nginx, Istio
|
||||
- Rook-Ceph
|
||||
- Keel, Kube-Monkey
|
||||
- Zalando Postgres
|
||||
- AWS
|
||||
- EC2
|
||||
- RDS
|
||||
- S3
|
||||
- Route53
|
||||
- EKS
|
||||
- Elasticache (redis)
|
||||
- Coding
|
||||
- QA automation (JS, Java)
|
||||
- Backend development with Go (GRPC and Rest API)
|
||||
- Scripting (Go, Perl, Bash)
|
||||
- Frontend development (ReactJS and Elm)
|
||||
- Just coding (Haskell, Go, Perl, NodeJS)
|
||||
- Others
|
||||
- Linux, MacOS
|
||||
- Docker
|
||||
- Ansible, Terraform, Vagrant
|
||||
- VirtualBox, Proxmox
|
||||
- Nginx, Envoy
|
||||
- Prometheus, grafana
|
||||
- ELK
|
||||
- Postgres, MySQL
|
||||
|
||||
## Cover Letter
|
||||
Hi! I'm a young DevOps engineer with 3++ years of hands-on experience in different IT areas. I had experience in several IT areas, and I understand how things may work for different teams, which is important for implementing the DevOps philosophy in the company.
|
||||
After working in a QA engineer position, I understand how to test any solution and describe test cases.
|
||||
Also, I'm not afraid of experiments when it comes to solving unusual problems and using new technologies. I know how things work on bare-metal and in the cloud, so I may help with migrating to the cloud and vice versa.
|
||||
Also, I'm thinking about consequences, and I'm ready to take responsibility for every decision I've made.
|
||||
I've got a will to learn, so I won't be stuck with old-fashioned technologies claiming they are the best fit if there are better alternatives. And I'm never saying that it's impossible to solve any problem unless it is.
|
||||
|
||||
When should you pay attention to my CV?
|
||||
- You working with Kubernetes
|
||||
- You need to improve/refactor/create/support CI/CD pipelines
|
||||
- You need help with docker
|
||||
- You're migrating to the cloud
|
||||
- You need to support legacy application
|
||||
- You need help with supporting micro-services application
|
||||
@ -1,90 +0,0 @@
|
||||
# Nikolay Rodionov
|
||||
```
|
||||
St. Petersburg, Russia
|
||||
|
||||
- phone: +79996690458
|
||||
- email: nicrodionov@gmail.com
|
||||
```
|
||||
---
|
||||
## About me
|
||||
|
||||
|
||||
I'm an engineer with 3++ years of hands-on experience in different IT areas: from writing e2e auto-tests in JS to setting up a Kubernetes cluster from scratch on bare metal.
|
||||
Just over a year ago, I've completely understood that being a system engineer is what I truly like to do.
|
||||
|
||||
A short list of things I love doing
|
||||
- Setting up, managing, and supporting K8s clusters
|
||||
- Writing scripts to automate manual actions (Go, Perl, Bash, or Ansible)
|
||||
- Linux administrating
|
||||
- Working with containers
|
||||
- Setting up CI/CD (Gitlab-CI, GitHub Actions)
|
||||
- Resolving incidents and troubleshooting problems
|
||||
- "Everything as code (from QA to Infrastructure)"
|
||||
|
||||
## Expirience
|
||||
### Itigris: _devops engineer/qa automation_
|
||||
> 07.2019 - until present
|
||||
I have started as a QA automation and then have moved to the system engineering
|
||||
1. As a QA Automation
|
||||
- Creating a codebase for E2e tests (**Java**, **NodeJS**) from scratch.
|
||||
- Creating and supporting e2e and integration tests **Gitlab C**I pipeline with dynamically starting **Selenoid** server
|
||||
- Automating basic actions with **bash**
|
||||
- Working a lot with **Docker**, **docker-compose**, and **Dockerfiles**
|
||||
- And a bit of SQL quering (**Postgres**)
|
||||
2. As a System Engineer
|
||||
- Writing scripts (**Go** and **Bash**)
|
||||
- Supporting and setting up several **k8s** clusters (**AWS EKS**)
|
||||
- Supporting services running in **docker** on **ec2** instances
|
||||
- Supporting **ec2** instances too
|
||||
- Troubleshooting incidents (**k8s**, **nginx**, **aws**)
|
||||
- Disaster recovery (**k8s**, **docker**)
|
||||
- Maintaing the process of "microservicing" the old monolith
|
||||
- Deploying services written in Java, JS and Python
|
||||
- And a bit of SQL administrating (**Postgres**)
|
||||
- Setting up an infrastructure with **Terraform**
|
||||
### Etersoft: _engineer_
|
||||
> 03.2017 - 06.2019 officially (and until present as a side project)
|
||||
I became as a "handyman" and was learning how to do anything in this company.
|
||||
- Lots of **Linux**, containers (**docker**, cri-o), and virtualization (VirtualBox, Proxmox)
|
||||
- A bit of networking (**IPtables** and UFW)
|
||||
- A bit of **Kubernetes** (setting up and supporting little bare-metal clusters from scratch)
|
||||
- Setting up virtual machines with **Vagrant** (VirtualBox and a bit **Docker**) and **Ansible**
|
||||
- Setting up **Nginx** and **Envoy**
|
||||
- **Bash** and **Perl** scripts for automating basic actions
|
||||
- Create a codebase for E2e tests (**NodeJs** and the plain **Selenium**) from scratch.
|
||||
- Create and support e2e tests **Gitlab CI** pipeline with a small static selenium server
|
||||
- A bit of frontend development (**ReactJS**) so I have a basic understanding of HTML and CSS too
|
||||
- A bit of SQL (**MySQL**)
|
||||
|
||||
## Skills
|
||||
- Kubernetes
|
||||
- Kubeadm
|
||||
- EKS
|
||||
- Docker, Containerd, Cri-O
|
||||
- Kubectl, Helm, Kustomize
|
||||
- Ingress Nginx, Istio
|
||||
- Rook-Ceph
|
||||
- Keel, Kube-Monkey
|
||||
- Zalando Postgres
|
||||
- AWS
|
||||
- EC2
|
||||
- RDS
|
||||
- S3
|
||||
- Route53
|
||||
- EKS
|
||||
- Elasticache (redis)
|
||||
- Coding
|
||||
- QA automation (JS, Java)
|
||||
- Backend development with Go (GRPC and Rest API)
|
||||
- Scripting (Go, Perl, Bash)
|
||||
- Frontend development (ReactJS and Elm)
|
||||
- Just coding (Haskell, Go, Perl, NodeJS)
|
||||
- Others
|
||||
- Linux, MacOS
|
||||
- Docker
|
||||
- Ansible, Terraform, Vagrant
|
||||
- VirtualBox, Proxmox
|
||||
- Nginx, Envoy
|
||||
- Prometheus, grafana
|
||||
- ELK
|
||||
- Postgres, MySQL
|
||||
@ -1,27 +0,0 @@
|
||||
## Cover letter
|
||||
When I find out that Native Instruments is looking for a DevOps Engineer, I've decided that I can't just get past it.
|
||||
|
||||
### About me
|
||||
Hi!
|
||||
|
||||
I'm a DevOps engineer with almost five years of experience in different IT areas (QA, Development, System Engineering). Currently, I'm working at Itigris in the role of DevOps/System Engineer.
|
||||
Some of my current responsibilities:
|
||||
- Support Kubernetes clusters. (all our applications and self-hosted services are running in Kubernetes)
|
||||
- Provide "Platform as a service" for developers and QA. For example, create and support reliable and fast CI/CD pipelines, support and administrate self-hosted services, etc.
|
||||
- Help other teams with an understanding of Docker and containerization.
|
||||
- Troubleshooting and administrating
|
||||
|
||||
### Why am I writing you?
|
||||
|
||||
Not so long ago, I've started to understand that it's important for me to feel that I'm working on something important and valuable. And all the projects at my current job don't make me feel like that. And I've started to think which job may make me give this filing.
|
||||
Because of being a musician, I've decided that I should continue my DevOps way in the musical area. Native Instruments is a great audio software developing company, and it seems impossible to me not to send my CV.
|
||||
|
||||
### Why, I think, you should pay attention to my CV?
|
||||
- I'm a young engineer with a will to learn.
|
||||
- I'm not afraid of non-standard solutions, and I'm not tied to old-familiar technologies.
|
||||
- I always take responsibility for what I'm doing.
|
||||
- I'm sure that things must be automated when it's possible.
|
||||
|
||||
Thank you
|
||||
|
||||
Nikolay Rodionov
|
||||
@ -1,27 +0,0 @@
|
||||
## Cover letter
|
||||
When I find out that SoundCloud is looking for a Production Engineer, I've decided that I can't just get past it.
|
||||
|
||||
### About me
|
||||
Hi!
|
||||
|
||||
I'm a DevOps engineer with almost five years of experience in different IT areas (QA, Development, System Engineering). Currently, I'm working at Itigris in the role of DevOps/System Engineer.
|
||||
Some of my current responsibilities:
|
||||
- Support Kubernetes clusters. (all our applications and self-hosted services are running in Kubernetes)
|
||||
- Provide "Platform as a service" for developers and QA. For example, create and support reliable and fast CI/CD pipelines, support and administrate self-hosted services, etc.
|
||||
- Help other teams with an understanding of Docker and containerization.
|
||||
- Troubleshooting and administrating
|
||||
|
||||
### Why am I writing you?
|
||||
After reading the job description, I've had a little doubt because I'm not sure that I can make a perfect fit right now. But it seems impossible to me not to try because I think SoundCloud is a great platform, and I will be happy to become a part of the team. I'm just tired of working on projects that don't make me feel satisfied, no matter how interesting tasks are. That's why I've decided to try.
|
||||
|
||||
SoundCloud is a platform that I'm using every day (as a listener and as a musician), and I believe that it's a kind of project that will make me feel that I'm working on something valuable. That's why I hope you will come back with feedback even if I'm not good enough to join the team right now. To help me understand which technologies I should learn deeper.
|
||||
|
||||
### Why, I think, you should pay attention to my CV?
|
||||
- I'm a young engineer with a will to learn.
|
||||
- I'm not afraid of non-standard solutions, and I'm not tied to old-familiar technologies.
|
||||
- I always take responsibility for what I'm doing.
|
||||
- I'm sure that things must be automated when it's possible.
|
||||
|
||||
Thank you
|
||||
|
||||
Nikolay Rodionov
|
||||
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
|
Before Width: | Height: | Size: 145 KiB |
Reference in New Issue
Block a user