Not a job description. A compounding list of muscles I've built while actually putting software in front of real users — six projects to production so far, and counting.
From requirements with non-technical stakeholders, through architecture, implementation, QA, deployment, and the boring ongoing maintenance. After six of these, I stopped being surprised by what a project can throw at you.
Running daily stand-ups, unblocking teammates, shielding the team from scope creep, translating PM-speak into tasks. Team-lead mechanics without the politics.
At my day job I've put platforms in front of thousands of people inside a single company — the kind of scale where "just redeploy" or "ask the user to refresh" stops being an option. My personal projects get shipped; my work projects get shipped and lived with.
Systems that introspect a MongoDB schema and answer in plain English. A debugger that opens its own GitHub PRs. A Claude-powered Figma plugin. The boring kind of AI — the kind that saves humans time.
—
Six in-house projects end-to-end. A CEE platform used across borders. A few awards. A lot of stand-ups. The short version of the story.