Junior DevOps Engineer

Affidea

About The Position

The Junior DevOps Engineer builds foundational DevOps skills by supporting CI/CD pipeline maintenance, monitoring and alerting, basic infrastructure tasks, and access and security administration under close supervision. The role is expected to grow steadily in independence and technical scope as the employee develops competence and confidence across the team’s toolchain and internal platforms. The engineer assists with maintaining existing CI/CD pipelines, monitoring pipeline runs, triaging straightforward build and deployment issues, and following documented runbooks and change procedures. They help configure monitoring dashboards and alert rules, review alerts, document recurring patterns, and contribute observations to runbook improvements. The role also supports routine infrastructure and environment tasks using infrastructure-as-code templates and established change processes, and documents work performed. The engineer assists with routine access management and basic security hygiene, and helps administer internal platforms such as Bitrix24 for well-defined requests. Ambiguous, higher-risk, anomalous, or security-related issues must be escalated to senior engineers. The employee actively completes onboarding and learning materials, pairs with senior DevOps engineers, tracks learning goals with a mentor or the DevOps Lead, and takes on progressively larger tasks. They are expected to follow documented change-management, security, and operational procedures; use agreed tools and ticketing systems accurately; apply feedback; and raise process gaps or unclear documentation with the team.

Requirements

Bachelor's degree or diploma in Computer Science, Information Technology, Software Engineering, or a related field, or a completed relevant bootcamp or certification path with a demonstrable practical portfolio.
0–2 years of experience in a DevOps, systems administration, or software development support capacity.
Basic understanding of version control, such as Git, and branching workflows.
Exposure to Linux or Windows server environments and basic scripting, such as Bash, PowerShell, or Python.
Some exposure to CI/CD concepts and tools, such as Jenkins, GitHub Actions, or Azure DevOps Pipelines.
Basic understanding of networking fundamentals, including DNS, TCP/IP, and HTTP/HTTPS.

Responsibilities

Assist with maintenance and minor configuration changes to existing CI/CD pipelines under guidance from senior engineers.
Monitor pipeline runs, flag failures, and help triage straightforward build and deployment issues.
Follow documented runbooks and change procedures when adjusting pipelines, and escalate ambiguous or higher-risk changes before proceeding.
Help configure and maintain basic monitoring dashboards and alert rules under supervision.
Perform first-line alert review and promptly escalate genuine incidents to senior engineers.
Document recurring alert patterns and contribute observations to runbook improvements.
Assist with routine infrastructure tasks, including environment provisioning support and configuration updates, under close supervision.
Use infrastructure-as-code templates and established change processes instead of making ad-hoc infrastructure changes.
Document steps taken and outcomes to support knowledge transfer.
Assist with routine access management, including user provisioning and de-provisioning, following approved processes.
Support basic security hygiene tasks such as patch tracking and access reviews under supervision.
Help administer internal platforms, including Bitrix24 and similar collaboration or CRM tools, for routine, well-defined requests.
Immediately escalate anomalous access requests or potential security concerns.
Complete onboarding materials, toolchain documentation, and internal platform guides; pair with senior engineers and track learning goals and progress with a mentor or the DevOps Lead.
Follow documented change-management, security, and operational procedures; use agreed tools and ticketing systems consistently and accurately; apply feedback; and raise process gaps or unclear documentation with the team.