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) projects
- Generate and analyze reports on code smells, vulnerabilities, bugs
- Enforce quality gates in Jenkins using sonarScanner CLI or plugin
- Set up project-level and global rulesets
- Manage access control and authentication
JFrog Artifactory:
- Set up and manage local repositories for Maven, Docker, and npm
- Configure virtual repositories for aggregation
- Implement artifact retention policies
- Automate artifact uploads from Jenkins using Artifactory plugin, REST API, or CLI
- Set user/group/permission targets for access control
GitHub Enterprise:
- Manage repositories, create branches, handle pull requests
- Configure branch protection rules and merge checks
- Implement webhook triggers to integrate with Jenkins
- Resolve merge conflicts and apply GitFlow or trunk-based workflows
Linux & Scripting:
- Navigate and manage Linux file systems
- Write Bash, Python, or PowerShell scripts for automation
- Configure log rotation and cleanup for Jenkins, SonarQube, Artifactory
- Set up reverse proxies (Nginx/Apache) if needed
- Review and troubleshoot logs in /var/log, /opt/jenkins, or containers
Tools & Technologies (Hands-on Expectation):
enkins / CloudBees Jenkins:
- Design and write Jenkinsfile for pipeline-as-code (declarative or scripted)
- Create multi-branch pipelines
- Configure build triggers (SCM/webhook/cron), post-build actions, and shared libraries
- Install and configure Jenkins plugins (e.G., Git, SonarQube Scanner, Artifactory)
- Set up Jenkins agents (static or dynamic)
- Store build artifacts and test results
- Monitor and troubleshoot builds via console output and logs
Docker:
- Write and maintain Dockerfiles for application packaging
- Use docker-compose for local testing environments
- Build and tag images via Jenkins pipeline
- Push/pull images to/from JFrog Artifactory Docker registry
- Implement security best practices: base image validation, multi-stage builds, image cleanup automation
CI/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 experience
- 4+ years hands-on with the following: Jenkins, Docker, SonarQube, JFrog Artifactory, GitHub Enterprise
- Clear understanding of DevOps workflows, not just tool usage
- Must be able to explain what they have configured and automated in each tool
Preferred Skills (Nice to Have):
- Exposure to infrastructure-as-code tools (e.G., Ansible, Terraform)
- Awareness of DevSecOps practices
- Experience 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 used
- Clearly explain what configurations/implementations were done by them during the project (not their team)
- An extended CV
- Or a separate email/document that describes tool-by-tool hands-on experience
Applications without actual hands-on configuration details will not be shortlisted.