Skip to main content

JFrog

Developer Support Engineer (Atlanta)

  • Confirmed live in the last 24 hours
  • $90k–$95k
  • Mid level
  • On-site · Atlanta, Georgia
  • 2+ yrs exp
  • Added 1 month ago

About this role

JFrog seeks a Developer Support Engineer in Atlanta to serve as a technical partner for customers using their DevOps platform. You'll troubleshoot complex CI/CD scenarios, develop automation scripts, and collaborate across R&D and sales teams to resolve issues and improve customer success.

What you'll do

  • Troubleshoot and resolve complex CI/CD customer scenarios with innovative solutions
  • Write debugging and automation scripts in Bash, Python, and Groovy
  • Set up JFrog applications and third-party products across multiple environments
  • Analyze logs, thread dumps, HTTP traffic, and JVM/OS parameters to diagnose issues
  • Reproduce customer scenarios and document bugs or feature requests
  • Maintain and expand knowledge base of known issues and solutions

What they're looking for

  • Linux administration
  • Software debugging and troubleshooting
  • Bash, Python, and Groovy scripting
  • Java or other compiled languages
  • CI/CD pipeline knowledge
  • Log analysis and performance diagnostics
  • Database and LDAP administration
  • Apache/Tomcat and reverse proxy (nginx/httpd) configuration

Benefits

  • Hybrid work: 3 days onsite, 2 days remote
  • Equity package with restricted stock units (RSU)
  • Employee Stock Purchase Plan eligibility
  • Comprehensive health, dental, and vision coverage
  • Retirement and wellness programs
  • Career development and learning opportunities
Apply on the employer's site

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

JFrog

Industry
Technology & Software
Website
jfrog.com
View all jobs at JFrog

Likely interview questions

  • Walk us through your experience troubleshooting a complex CI/CD pipeline issue—what was your approach and how did you resolve it?
  • Tell us about your most challenging customer support case. How did you handle escalation and collaboration with technical teams?