Skip to main content

JFrog

Professional Services DevOps Engineer

Atlanta$135k–$145kfull-timemidAdded 3 days ago

About this role

JFrog seeks an experienced DevOps engineer to join their Professional Services team, delivering CI/CD pipeline design and DevOps platform implementation for enterprise customers. You'll architect solutions using JFrog products alongside Docker, Kubernetes, and cloud technologies while collaborating cross-functionally to ensure customer success.

What you'll do

  • Design and build CI/CD pipelines with Docker, Kubernetes, and IaC for JFrog customers
  • Configure binary repositories, distribution systems, and continuous build tooling (Jenkins, Maven, NPM, PyPI)
  • Partner with Sales, Support, and Development teams to guide customers through their DevOps transformation
  • Train customers and open-source community on JFrog platform best practices
  • Provide feedback to product teams on feature requirements based on customer needs
  • Maintain knowledge of emerging DevOps and CI/CD technology trends

What they're looking for

  • CI/CD tools (Jenkins, GitLab CI, GitHub Actions)
  • Docker and container orchestration (Kubernetes)
  • Infrastructure as Code (Terraform, CloudFormation, Ansible, Chef, Puppet)
  • Linux system administration
  • Cloud platforms (AWS, Azure, GCP)
  • Binary repository management (Artifactory)
  • Customer-facing communication and technical training
  • Git and version control workflows

Benefits

  • Base salary $135,000–$145,000
  • Discretionary bonuses or commission eligibility
  • Equity package (restricted stock units)
  • Employee Stock Purchase Plan
  • Comprehensive medical, dental, vision, and retirement benefits
  • Hybrid work arrangement (3 days office, 2 days remote)
Apply on the employer's site

Opens the official application on the employer’s site. No login required.

JFrog

Website
jfrog.com
View all jobs at JFrog

Likely interview questions

  • Walk us through a complex CI/CD pipeline you've designed—what challenges did you encounter and how did you solve them?
  • How would you approach migrating a customer's legacy build system to a modern Docker and Kubernetes-based pipeline?