Job Role : DevOps Engineer – Lead
Client : Domestic (Delhi based client)
Experience required : To be eligible for this position, a minimum of 5 years of experience in Linux Administration is required.
Project duration : 1 year / contractual or project based tenure.
Client Onsite : Noida, Okhla phase 2. New Delhi.
Employment Type : Full-Time / Contractual ( I year). Notice period 45 days.
Client Onsite : Noida, Okhla phase 2. New Delhi.
Attractive Salary.
Job Overview
We are looking for a Dynamic and Talented DevOps Engineer with minimum 5 years of experience in building, managing, and automating DevOps pipelines and deployments on self-managed infrastructure.
This role demands hands-on experience with at least 2 tools from the following stack :
are mandatory for application for this position.
- JFrog Artifactory
- SonarQube
- GitHub Enterprise
- Jenkins / CloudBees Jenkins ( if known is okay but not mandatory)
- Docker
The candidate should be comfortable working in Linux environments, automating tasks with scripts, and configuring the DevOps ecosystem at an infrastructure and pipeline level.
Key Responsibilities & Expected Configuration Knowledge
SonarQube :
Configure SonarQube for Java / Maven (or .NET) projectsGenerate and analyze reports on code smells, vulnerabilities, bugsEnforce quality gates in Jenkins using sonarScanner CLI or pluginSet up project-level and global rulesetsManage access control and authenticationJFrog Artifactory :
Set up and manage local repositories for Maven, Docker, and npmConfigure virtual repositories for aggregationImplement artifact retention policiesAutomate artifact uploads from Jenkins using Artifactory plugin, REST API, or CLISet user / group / permission targets for access controlGitHub Enterprise :
Manage repositories, create branches, handle pull requestsConfigure branch protection rules and merge checksImplement webhook triggers to integrate with JenkinsResolve merge conflicts and apply GitFlow or trunk-based workflowsLinux & Scripting :
Navigate and manage Linux file systemsWrite Bash, Python, or PowerShell scripts for automationConfigure log rotation and cleanup for Jenkins, SonarQube, ArtifactorySet up reverse proxies (Nginx / Apache) if neededReview and troubleshoot logs in / var / log, / opt / jenkins, or containersTools & Technologies (Hands-on Expectation) :
enkins / CloudBees Jenkins :
Design and write Jenkinsfile for pipeline-as-code (declarative or scripted)Create multi-branch pipelinesConfigure build triggers (SCM / webhook / cron), post-build actions, and shared librariesInstall and configure Jenkins plugins (e.g., Git, SonarQube Scanner, Artifactory)Set up Jenkins agents (static or dynamic)Store build artifacts and test resultsMonitor and troubleshoot builds via console output and logsDocker :
Write and maintain Dockerfiles for application packagingUse docker-compose for local testing environmentsBuild and tag images via Jenkins pipelinePush / pull images to / from JFrog Artifactory Docker registryImplement security best practices : base image validation, multi-stage builds, image cleanup automationCI / CD : Jenkins (CloudBees), GitHub Webhooks
SCM : GitHub Enterprise
Containers : Docker, Docker Compose
Quality : SonarQube
Artifacts : JFrog Artifactory (Maven + Docker)
Scripting : Bash, Python, PowerShell
OS : Linux (Ubuntu / CentOS), Windows (for .NET if applicable)
Build Tools : Maven, Gradle, dotnet CLI
Minimum Requirements :
5+ years total experience4+ years hands-on with the following : Jenkins, Docker, SonarQube, JFrog Artifactory, GitHub EnterpriseClear understanding of DevOps workflows, not just tool usageMust be able to explain what they have configured and automated in each toolPreferred Skills (Nice to Have) :
Exposure to infrastructure-as-code tools (e.g., Ansible, Terraform)Awareness of DevSecOps practicesExperience with monitoring tools (Grafana, Prometheus, Nagios)Experience integrating .NET Core apps (IIS or Kestrel hosting)Candidate Submission Instruction :
To apply, candidates must :
Include a detailed CV that lists DevOps tools usedClearly explain what configurations / implementations were done by them during the project (not their team)An extended CVOr a separate email / document that describes tool-by-tool hands-on experienceApplications without actual hands-on configuration details will not be shortlisted.
