Jeff Levin
Staff Software Engineer at Grafana Labs
Anchorage, Alaska, United States
Summary
🤩
Rockstar🎓
Top SchoolJeff Levin is a Staff Software Engineer with 13 years of experience building backend systems, currently shaping Grafana's next-generation app platform and testing infrastructure. He combines hands-on API and backend development—contributing to high-profile open-source projects like Grafana and Puma—with product leadership from founding a SaaS legal automation company. Based in Anchorage, Alaska, he balances cloud-native architectures (AWS, Terraform, Lambda, Postgres, DynamoDB) with pragmatic engineering for startups and nonprofits. Jeff has a track record of shipping robust, tested APIs and scaling teams from MVP to delivery, often acting as a stand-in CTO. He also co-founded the Alaska Developers Alliance, demonstrating a commitment to community-building and developer education across the state. Practical, curious, and entrepreneurial, he brings both technical depth and organizational muscle to ambiguous, systems-level challenges.
13 years of coding experience
6 years of employment as a software developer
High School Diploma, High School Diploma at Highland Tech HighBBA Management Information Systems General, BBA Management Information Systems General at University of Alaska Anchorage
Stackoverflow
2,250reputation
312kreached
21answers
9questions
Github Skills (20)
apidoc10
multithreading10
testing10
ruby10
go10
api10
server10
develop9
backend9
rack9
postgresql8
nvm6
serverless6
nodejs6
google-oauth6
Programming languages (12)
Github contributions (5)
grafana/grafana
Jan 2022 - Dec 2022
The open and composable observability and data visualization platform. Visualize metrics, logs, and traces from multiple sources like Prometheus, Loki, Elasticsearch, InfluxDB, Postgres and many more.
Role in this project:
Backend Developer
Backend DeveloperContributions:377 reviews, 49 commits, 90 PRs in 10 months
Contributions summary:Jeff primarily contributed to the Datasource API, addressing issues related to read-only datasources and standardizing API responses. They implemented checks to prevent modification of read-only datasources and ensured 404 errors were returned when datasources were not found during updates. The user's work involved modifying files within the `pkg/api` directory, specifically focusing on the `datasources_test.go` and `datasources.go` files. This indicates a focus on backend API development and testing.
visualizeobservabilitybusiness-intelligencegrafanaprometheus
puma/puma
Mar 2020 - Apr 2020
A Ruby/Rack web server built for parallelism
Role in this project:Back-end Developer
Back-end DeveloperContributions:17 commits, 1 PR, 13 comments in 1 month
Contributions summary:Jeff primarily contributed to the configuration and testing aspects of the Puma web server. They focused on setting up environment variables for thread management (RAILS_MIN_THREADS, RAILS_MAX_THREADS) and ensuring the correct behavior of worker processes, including preloading the application. Additionally, the user modified and updated test files, ensuring the proper functioning of Puma's configuration options. These changes involved adjustments to thread settings, worker counts, and environment variable loading.
multithreadingweb-serverrackrubyparallelism
Find and Hire Top DevelopersWe’ve analyzed the programming source code of over 60 million software developers on GitHub and scored them by 50,000 skills. Sign-up on Prog,AI to search for software developers.