Steven Littiebrant
Funemployed
Milwaukee, Wisconsin, United States
Summary
🤩
Rockstar🎓
Top SchoolSteven Littiebrant is a pragmatic senior software engineer with 15 years building and scaling consumer and infra systems, most recently as a Staff Engineer at Uber where he drove critical driver-signup flows and served as a de facto Go client tech lead for Cadence. He blends backend, DevOps and hands-on debugging — from migrating services and fixing deep race conditions to improving test suites and build tooling — and has contributed meaningful fixes to the popular Cadence orchestration projects. Comfortable working across teams, he’s mentored hundreds of engineers, provided extensive user support, and repeatedly solved thorny, long-lived production problems that others missed. Earlier in his career he helped grow Muzy to tens of millions of users and shipped highly optimized mobile and backend systems. Based in Milwaukee and currently taking a purposeful break while advising a small business, he’s intentionally discoverable and responsive if you poke him. A detail many miss: he’s routinely dug into language/runtime bugs and even patched Go to keep large systems reliable.
15 years of coding experience
15 years of employment as a software developer
University of Wisconsin-Green Bay
Github Skills (20)
testing10
makefile10
go10
functionfs10
orchestration10
concurrency10
exponential-backoff9
distributed-systems9
workflow-engine9
devops9
orchestrate9
error-handling9
engine9
orchestrator-workflow9
automations8
Programming languages (17)
Github contributions (5)
cadence-workflow/cadence-go-client
Apr 2018 - Dec 2022
Framework for authoring workflows and activities running on top of the Cadence orchestration engine.
Role in this project:
Back-end Developer
Back-end DeveloperContributions:3 releases, 262 reviews, 66 commits in 4 years 8 months
Contributions summary:Steven contributed to the Cadence Go client, focusing on code improvements and bug fixes. Their work involved refactoring, dependency updates (like unpinning and bumping `zap`), and optimizing existing tests by removing unnecessary components and addressing race conditions. The user also enhanced the testing framework by adding mock-delay-returning function and improving its goroutine leak detection. Furthermore, they fixed several race conditions and handled potential errors.
golangworkflow-functionscadenceorchestrationauthoring-workflows
cadence-workflow/cadence
Jan 2021 - Nov 2022
Cadence is a distributed, scalable, durable, and highly available orchestration engine to execute asynchronous long-running business logic in a scalable and resilient way.
Role in this project:Back-end Developer & DevOps Engineer
Back-end Developer & DevOps EngineerContributions:1 release, 1080 reviews, 55 commits in 1 year 9 months
Contributions summary:Steven focused on improving the build process and code quality of the Cadence workflow engine. Their contributions included cleaning up and refactoring the Makefile, improving code generation, and removing unused dependencies. They also worked on optimizing the test suite and adding checks for potential bugs, such as those related to string-to-integer conversions. Additionally, they improved the test environment and introduced global ratelimiters.
cadenceresilientorchestration-engineservice-buslogic
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.