How did you transition from junior level to middle level?

The transition from Junior to Middle in DevOps involved several key stages:

1. Deepening technical expertise:

   • Thorough study of operating system fundamentals (Linux): file system, processes, network, permissions.
   • Understanding network operations (TCP/IP, DNS, routing).
   • Mastering automation tools: scripting (Bash, Python), configuration management systems (Ansible, Chef, Puppet).
   • Proficiency in containerization (Docker) and orchestration (Kubernetes).
   • Experience with CI/CD pipelines (Jenkins, GitLab CI, GitHub Actions).
   • Skills in working with cloud platforms (AWS, Azure, GCP).

2. Development of practical skills:

   • Active participation in real projects, not just isolated tasks.
   • Troubleshooting more complex issues in production.
   • Designing and implementing small infrastructural solutions.
   • Participating in Code Review, both as reviewer and reviewee.
   • Writing automated tests for infrastructural components.

3. Broadening horizons:

   • Understanding the business context of tasks, not just technical implementation.
   • Learning project management methodologies (Agile, Scrum).
   • Communicating with other teams (development, testing, business analysts).
   • Self-learning new technologies and best practices.

4. Mentoring (informal and formal):

   • Training junior colleagues, explaining principles of work.
   • Participating in knowledge exchange within the team.

5. Taking on greater responsibility:

   • Performing tasks with minimal supervision from senior colleagues.
   • Actively proposing solutions and improvements.
   • Being ready to take responsibility for one's work.

This process involved continuous learning and applying acquired knowledge in practice, with tasks gradually becoming more complex and expanding the scope of responsibility.