Kevin Coleman
Principal Engineer at Spaceback
Ann Arbor, Michigan, United States
Summary
👤
Senior🎓
Top SchoolKevin Coleman is a Principal Engineer based in Ann Arbor with a decade of experience building scalable, data-driven systems across healthcare, legal, and political domains. He combines deep Ruby on Rails and JavaScript expertise with pragmatic DevOps and architecture skills to deliver high-throughput ingestion pipelines, automated marketing launches, and GDPR-aware sharding solutions. As a technical lead and founding backend engineer, he has launched mobile-backed APIs, microservices for webhook traffic, and CI/Kubernetes-driven deployments that measurably reduced latency and increased test coverage. Kevin also contributes to the octopus ActiveRecord sharding library, improving its stability and multi-shard migration behavior—evidence of his focus on reliability at the database layer. His background in campaign data operations and lifeguarding hints at a calm, process-oriented approach to high-pressure problems and cross-team collaboration.
10 years of coding experience
9 years of employment as a software developer
Mater Dei High SchoolBachelor of Arts - BA Political Science, Bachelor of Arts - BA Political Science at Occidental College
Latin
Github Skills (8)
activerecord10
rails10
sharding10
ruby-on-rails10
migration10
ruby10
postgresql9
testing8
Programming languages (7)
Github contributions (5)
thiagopradi/octopus
Oct 2018 - Oct 2018
Database Sharding for ActiveRecord
Role in this project:
Back-end Developer & Database Engineer
Back-end Developer & Database EngineerContributions:9 commits, 2 PRs, 7 comments in 3 days
Contributions summary:Kevin primarily focused on fixing bugs and improving the stability of the `octopus` library. Their contributions involved addressing errors related to ActiveRecord, Arel, and database connections, ensuring correct behavior with different Rails versions. The user implemented changes to migrations, including support for running them on specific shards and groups, and ensured proper schema creation and table initialization across multiple database shards. These changes were focused on improving the performance and overall reliability of the database sharding implementation.
ruby-on-railsdatabase-shardingrailsmongoidsharding
3dna/servicesdashboard
Jun 2016 - Apr 2017
Contributions:10 PRs, 89 pushes, 12 branches in 10 months
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.