1

Grafana Developer Jobs in Georgia (NOW HIRING)

Site Reliability Engineer

Alpharetta, GA · On-site

$55.75 - $74/hr

SLI/SLO Definition & Grafana Implementation: Drive the definition of Service Level Indicators (SLIs ... DevOps, or production engineering role. We care far more about what you've actually shipped than ...

Senior AI Engineer

Alpharetta, GA · On-site

$119K - $157K/yr

OpenTelemetry, Grafana, Prometheus. * CI/CD (Jenkins, GitHub Actions), DevOps/GitOps. Qualifications * Bachelor's/Master's in Computer Science or equivalent. * 8+ years of software engineering ...

New

Senior AI Engineer

Alpharetta, GA · On-site

$119K - $157K/yr

OpenTelemetry, Grafana, Prometheus. * CI/CD (Jenkins, GitHub Actions), DevOps/GitOps. Qualifications * Bachelor''''s/Master''''s in Computer Science or equivalent. * 8+ years of software engineering ...

DevOps Engineer

Atlanta, GA · Hybrid

$50.75 - $69.50/hr

We are looking for a DevOps Engineer to join our amazing Cloud Engineering team. We are developing ... Experience with monitoring and observability tools such as Datadog, Prometheus, Grafana, or similar.

Senior AI Engineer

Alpharetta, GA · On-site

$119K - $157K/yr

OpenTelemetry, Grafana, Prometheus. * CI/CD (Jenkins, GitHub Actions), DevOps/GitOps. Qualifications * Bachelor'''''s/Master'''''s in Computer Science or equivalent. * 8+ years of software ...

Software Developer Augusta, Ga Work Location & Schedule This is a hybrid position based in our ... Use observability tooling (for example Grafana) to monitor production behavior and proactively ...

Software Developer Augusta, Ga Work Location & Schedule This is a hybrid position based in our ... Use observability tooling (for example Grafana) to monitor production behavior and proactively ...

Software Developer Augusta, Ga Work Location & Schedule This is a hybrid position based in our ... Use observability tooling (for example Grafana) to monitor production behavior and proactively ...

Software Developer Augusta, Ga Work Location & Schedule This is a hybrid position based in our ... Use observability tooling (for example Grafana) to monitor production behavior and proactively ...

Software Developer Augusta, Ga Work Location & Schedule This is a hybrid position based in our ... Use observability tooling (for example Grafana) to monitor production behavior and proactively ...

Senior DevOps Engineer

Atlanta, GA · Hybrid

$125K - $160K/yr

Section 1: Position Summary We are seeking a Senior DevOps Engineer with 10+ years of handson ... Metrics, logging, and tracing with Prometheus, Grafana, Splunk, New Relic, CloudWatch ...

... Grafana, Prometheus. • Support the application CI/CD pipeline for promoting software into higher environments through validation and operational gating, and lead in DevOps automation and best ...

Showing results 41-60

Grafana Developer information

See Georgia salary details

$15

$32

$44

How much do grafana developer jobs pay per hour?

As of Aug 14, 2026, the average hourly pay for grafana developer in Georgia is $32.44, according to ZipRecruiter salary data. Most workers in this role earn between $16.06 and $43.85 per hour, depending on experience, location, and employer.

Does Grafana require coding?

Grafana developers often use scripting and query languages like SQL or PromQL to create dashboards and visualize data, but basic setup and configuration can be done without coding. Advanced customization and plugin development typically require programming skills in languages such as JavaScript or Python. Familiarity with data sources and query languages enhances effectiveness in the role.

What are some common challenges faced by Grafana developers in managing large-scale dashboards?

Grafana Developers often encounter challenges related to performance optimization and data visualization when managing large-scale dashboards. As the number of panels and data sources increases, dashboards can become slower to load and harder to maintain. Developers need to implement best practices such as efficient query design, use of variables, and dashboard templating to ensure scalability and responsiveness. Collaborating closely with DevOps, backend teams, and data engineers is also essential to troubleshoot issues and implement robust monitoring solutions.

What are the key skills and qualifications needed to thrive as a Grafana developer, and why are they important?

To thrive as a Grafana Developer, you need strong skills in data visualization, time-series databases (like Prometheus or InfluxDB), and proficiency in scripting or query languages such as SQL or Grafana's own query language, often backed by a degree in computer science or related fields. Familiarity with Grafana dashboards, plugins, data source integrations, and monitoring tools, as well as experience with cloud platforms and DevOps pipelines, are highly valuable. Problem-solving, attention to detail, and effective communication are essential soft skills for collaborating with teams and addressing monitoring needs. These skills ensure the creation of insightful dashboards, efficient troubleshooting, and effective communication of system health to stakeholders.

What is the difference between Grafana Developer vs Data Analyst?

AspectGrafana DeveloperData Analyst
Required skillsGrafana setup, dashboard creation, data visualization, basic scriptingData interpretation, SQL, Excel, statistical analysis
CertificationsNone specific, familiarity with data visualization toolsCertifications like Microsoft Data Analyst, Google Data Analytics
Work environmentIT teams, DevOps, monitoring dashboardsBusiness units, reporting teams, data-driven decision making
Industry usageTech, finance, operations, monitoringMarketing, finance, healthcare, business analysis

While both roles involve working with data, a Grafana Developer specializes in creating and maintaining dashboards for monitoring and visualization, often within IT and DevOps environments. A Data Analyst focuses on interpreting data to support business decisions, using a broader set of analytical tools. Understanding these differences helps employers and job seekers target the right skills and roles.

What is a Grafana developer?

Grafana Developers are professionals who specialize in designing, developing, and maintaining dashboards and data visualizations using Grafana, an open-source analytics and monitoring platform. They work with various data sources, create custom visualizations, and help organizations gain insights from their data through interactive dashboards. Grafana Developers typically have experience with scripting, querying databases, integrating APIs, and may also develop Grafana plugins or contribute to automation and alerting solutions.

Is Grafana a good place to work?

Grafana is a company known for its open-source data visualization platform, and working there as a Grafana Developer involves collaborating on cloud-based tools, often requiring skills in JavaScript, Go, and DevOps. Employees generally report a collaborative environment with opportunities for growth in the tech industry.

What job categories do people searching Grafana Developer jobs in Georgia look for?

The top searched job categories for Grafana Developer jobs in Georgia are:

What cities in Georgia are hiring for Grafana Developer jobs?

Cities in Georgia with the most Grafana Developer job openings:

Infographic showing various Grafana Developer job openings in Georgia as of August 2026, with employment types broken down into 77% Full Time, 7% Part Time, 1% Temporary, and 15% Contract. Highlights an 80% Physical, 6% Hybrid, and 14% Remote job distribution, with an average salary of $67,475 per year, or $32.4 per hour.

Site Reliability Engineer

Incident IQ

Alpharetta, GA • On-site

$55.75 - $74/hr

Full-time

Medical, Dental, Vision, Life, Retirement, PTO

Posted 18 days ago


Job description

Company Overview:
About Us:
Atlanta-based Incident IQ is the leading workflow management platform built exclusively for K-12 districts. Trusted by over 2,000 districts, Incident IQ powers mission-critical services for more than 12 million students and educators nationwide. By connecting technology and operational workflows, Incident IQ enables schools to streamline processes, reduce administrative burdens, and focus on what matters most: supporting students.
Purpose:
Incident IQ is committed to creating a future where every K-12 district operates with seamless efficiency. When operations are unified on a single platform, districts gain the clarity and control needed to build a stronger foundation for student success. We're focused on delivering the tools, support, and partnerships that help make that vision a reality.
Mission:
Incident IQ is on a mission to eliminate the friction of disconnected systems and clunky workflows that slow schools down. We're reimagining the critical work that happens behind the scenes, bringing visibility, efficiency, and impact to the processes that keep classrooms running. By streamlining the complex, automating the routine, and surfacing the insights that matter most, we can create the conditions for educators to teach, students to thrive, and districts to shape the future of education.
Site Reliability Engineer (SRE) Overview:
We are looking for a Site Reliability Engineer (SRE) to join our Engineering team. This is a build-it-from-zero role at startup speed. You're our first dedicated Site Reliability Engineer, and you'll be defining what "reliable" means for our production systems, not maintaining someone else's playbook. You'll work with leading-edge observability and reliability tooling, and the calls you make will directly shape how confidently the whole engineering org ships.
Expect real engineering deep dives, not top-down mandates. We love digging into a hard problem together, and we want you to bring a strong point of view, back it up with data and sound reasoning, and enjoy the back-and-forth as we work toward the best answer. Good persuasion skills matter here as much as technical depth, since good ideas still have to win the room. We move at startup speed: we'd rather figure something out in a few hours than plan it for weeks. We're a collaborative, respectful team: we debate ideas hard, never people.
We care much more about a proven track record running big, ambiguous projects efficiently than about years of tenure or a wall of certifications. You should be genuinely comfortable working independently: we won't hand-hold you or chase you for status updates. We expect you to take total ownership of outcomes and drive them without being asked twice, and without running your own separate agenda. This work is relentless, juggling several things at once under real time pressure is normal here, and the right candidate is passionate about SRE and thrives on that intensity, not just tolerates it.
Site Reliability Engineer (SRE) Responsibilities:
  • This role is hands-on from day one. Your initial focus will be:
    • SLI/SLO Definition & Grafana Implementation: Drive the definition of Service Level Indicators (SLIs) and Service Level Objectives (SLOs) for our core services, translating them into insightful Grafana dashboards and actionable, burn-rate-based alerting, so pages are precise and noise stays low.
    • Incident Management: Stand up our incident management practice (tooling such as PagerDuty, on-call training, incident command), then own and continuously improve it, stepping in personally only for the most severe incidents.
    • Observability Stack Ownership: Own the observability stack end to end: metrics, logs, traces, Real User Monitoring (RUM), and synthetic checks across the user journey, alerting whenever a signal deviates from baseline.
    • Team Enablement: Partner with engineering teams to refine SLIs, SLOs, and error budgets as services evolve, and coach teams on SRE and observability best practices.
    • Toil Reduction: Identify and automate away manual, repetitive operational work through infrastructure as code and tooling.
    • Chaos & Performance Engineering: Design and run load/performance tests and chaos engineering game days to proactively surface weaknesses before they cause incidents.
  • For example: in your first few days, you might stand up an SLO and a burn-rate alert in Grafana for our highest-traffic service. Within a couple of weeks, PagerDuty on-call is configured and the rotation is trained on incident command. That's the pace we operate at here: hours and days, not weeks.

Site Reliability Engineer (SRE) Requirements:
  • The tools below are what we run today. What matters more is the systems literacy and genuine curiosity about reliability that let you reason from first principles when something breaks in a way none of these tools have seen before:
    • Education & Systems Foundations: Bachelor's degree in Computer Science, Computer Engineering, or equivalent formal training, with real depth in operating systems, databases, and networking. This fundamental understanding is required. How you acquired it (degree or a rigorous equivalent) is not, since it's what lets you diagnose a novel failure, not just operate a dashboard.
    • AI-Accelerated Execution (core requirement): You actively use AI tools daily to multiply your own output, not just experiment with them on the side. We expect you to use AI to write and debug code faster, stand up dashboards and alerts faster, and generally ship at a pace that wouldn't be possible without it. This is not a bonus skill here; it's how we expect this role to operate.
    • Track Record Over Tenure: A demonstrated history of independently driving big, ambiguous reliability or infrastructure projects to completion, typically reflecting 5+ years in an SRE, DevOps, or production engineering role. We care far more about what you've actually shipped than the number itself.
    • SLI/SLO Methodology: Proven, hands-on track record implementing the SLI/SLO/error-budget model in a prior role, the discipline formalized in Google's SRE Workbook.
    • Observability Tooling: Strong experience with Grafana and PromQL (Prometheus Query Language), Grafana Alloy for Loki logs, and a metrics backend such as Prometheus or Datadog. Experience instrumenting with OpenTelemetry and a tracing/Application Performance Monitoring (APM) backend (open-source preferred: SigNoz, Uptrace, Tempo; commercial: Datadog, New Relic), plus Real User Monitoring (RUM) and synthetic monitoring (e.g., Grafana Faro, Grafana Synthetic Monitoring / k6).
    • Incident Management: Proven track record designing on-call rotations and incident command practices elsewhere, with tooling such as PagerDuty or equivalent.
    • Performance & Chaos Engineering: Hands-on with a load/performance framework (Locust, k6, or JMeter) and chaos engineering exercises to validate reliability under real conditions.
    • Automation, Infrastructure & Cloud: Proficient in Python, Go, or Bash; hands-on with Infrastructure as Code (Terraform, Ansible, or equivalent), Kubernetes, and at least one major cloud platform (Amazon Web Services (AWS), Google Cloud Platform (GCP), or Azure).
    • Communication: Experienced, versatile communicator: able to go deep with developers on root cause, tradeoffs, and implementation detail; comfortable pushing back with a real technical path when a team says something "can't" be done; precise about the difference between a mitigation and an actual fix when reporting status; and able to translate reliability status, risk, and priorities clearly for business and engineering stakeholders.
    • Independence & Pace: You don't need hand-holding or check-ins to make progress. Comfortable resolving ambiguous problems in hours, not weeks, taking full ownership of outcomes, and juggling multiple threads under real time pressure without dropping the ball.

What Success Looks Like:
By the end of your first quarter, core services have defined SLIs and SLOs, live in Grafana dashboards, and are backed by burn-rate-based alerting. A documented incident management process is operating end-to-end, run day to day by trained on-call engineers rather than by you personally, from detection through blameless postmortem. Over time, success looks like measurably reduced alert noise, faster Mean Time to Recovery (MTTR), and an engineering organization that trusts its reliability signals enough to make release and investment decisions based on them.
Bonus Points:
  • Experience standing up an SRE practice from zero to one ("founding SRE").
  • Experience with GitOps and just-in-time production access models.
  • Familiarity with eBPF-based auto-instrumentation (eBPF stands for extended Berkeley Packet Filter), such as Grafana Beyla or OpenTelemetry eBPF Instrumentation, for legacy or hard-to-modify codebases. It's a newer approach, nice to have rather than expected.
  • .NET experience is a plus, given our engineering stack.
  • Certifications aren't required and aren't a strong signal for us; what you've built matters more than what's on your cert wall. If you happen to have one, Certified Kubernetes Administrator (CKA) or Google Cloud Professional DevOps Engineer are the most relevant.

What makes Incident IQ different:
  • We facilitate whole-person growth where employees can develop personally as well as professionally.
  • We offer an energetic and collaborative environment; everyone's opinion matters!
  • We produce software that empowers K-12 schools to run efficiently, allowing for a better classroom experience for students to THRIVE!
  • We provide excellent work/life balance. Two amazing offices - a Downtown Atlanta office location and one at Halcyon in Alpharetta!

Incident IQ offers a competitive salary based on experience with a benefits package for full-time employees that includes medical, dental, vision, life insurance, 401k match, and paid-time off (PTO).
Incident IQ is an Equal Opportunity Employer