Cody Holland - Software Engineer
I am a software engineer with production experience in Python, Scala, Java, SQL, and API-heavy backend work. The thread running through most of my work is pretty simple: connect systems, remove manual pain, and make sure the result holds up when people actually need it.
That has looked like ticket fulfillment integrations, onboarding workflows, production pull requests, database changes tied to feature delivery, and multi-platform automation infrastructure. Most of it is proprietary, so I try to show the thinking, ownership, and tradeoffs as clearly as I can here.
Backend ownership, API integration, and a bias for shipping early and often. I build for production, not just to pass tests.
At Clipper I built and scaled the social media scheduling automation that handled 1,000+ posts per week across 100+ accounts spread over multiple platforms.
Understand the system, break the problem down, make the changes, and try to leave the next person with less chaos than I inherited.
Technical Highlights
I am comfortable at the boundary where your system has to talk to somebody else's, especially when that means handling imperfect data, operational edge cases, and partner-specific workflows.
I enjoy writing the glue that makes a product move: orchestration logic, support tooling, jobs, onboarding flows, and the pieces that reduce manual intervention over time.
I like reading through unfamiliar code, finding where behavior is breaking down in unexpected ways, and showing it who's boss.
I have worked in PostgreSQL as part of real feature delivery, including schema and data changes that had to line up cleanly with application behavior and operations.
I am used to making pull requests, reviewing code, supporting onboarding work, and seeing changes through as part of an actual team.
Messy integration problems, onboarding-heavy workflows, support tooling, production fixes, and the technical details required to get there.
Selected Work
I am not trying to present a bunch of polished side projects here. The more important story is that I have worked on real systems with real operators, live dependencies, and consequences when things break.
Founded and led development of a system that coordinated multi-platform posting workflows across Reddit, Instagram, YouTube, Facebook, Twitter/X, and Twitch.
The interesting part was not just posting content. It was building the scheduling, monitoring, and operational reliability needed for something that automated 1,000+ posts per week across 100+ accounts.
Worked on backend systems that integrated with ticketing partners like StubHub, Ticketmaster, and SeatGeek while also supporting internal onboarding and fulfillment processes.
This is where a lot of my professional backend instincts were sharpened: Python and Scala services, PostgreSQL changes, pull requests into production, and coordination with both engineers and sales team to make sure tickets were posted, de-listed, and fulfilled at the appropriate times.
Worked in a roughly 4,000-line Java project used to teach data structures and algorithms, adding features and fixing bugs inside an existing system.
That work mattered to me because it was a straightforward example of joining a mature codebase, understanding it quickly, and contributing real value without needing a greenfield environment.
Recommendations
"Cody would be a valuable addition to any development team, improving both the knowledge and the collaborative work environment."
"He surpassed my expectations both with his excellent work ethic as well as his programming skill. I would easily put him at the top 10% of computer science students."
Beyond the bullet points
I care a lot about software that is useful, understandable, and dependable. I also care about being the kind of teammate who can step into an existing system, learn it quickly, and make life easier for the people around me.
If you are hiring for backend-heavy engineering work, integrations, automation, or systems that need both technical depth and practical ownership, I would love to talk.
