Resume

Senior Software Developer · Houston, TX (Kingwood)

altsman.dev · linkedin.com/in/stevenaltsman · github.com/tinhalo

Summary

Senior software developer with 8+ years at JPMorgan Chase & Co. building enterprise applications, automation, and full-stack .NET solutions. Built IAHUB, a firmwide catalog of automation assets that scaled to 800,000+ entries and cut duplicate development across engineering organizations. Background spans automation engineering, enterprise integration, and over a decade of hands-on development across financial services and industrial sectors.

Skills

Languages & Frameworks — C#, .NET, .NET Framework, TypeScript, Python, PHP, PowerShell, Bash, Entity Framework, React, Angular, Next.js

Contact

Open to new roles · Houston, TX (Kingwood) · open to hybrid, remote, and on-site

Email and phone

My email address and phone number are behind a quick bot check — not to make you jump through hoops, but because unprotected contact details on a resume site get harvested within days.

If the check doesn’t load, LinkedIn below always works.

Where else to find me

• LinkedIn: linkedin.com/in/stevenaltsman — best for role enquiries and recruiter contact
• GitHub: @tinhalo — the repositories behind the projects on this site are private, but I’m glad to grant access on request; just ask

What I’m looking for

Senior or staff-level software engineering, with a preference for full-stack work that runs all the way to deployment. Strongest in C#/.NET, TypeScript/Node, and Python, with Kubernetes and CI/CD ownership. Happy to talk about developer tooling, platform work, or anything involving the Model Context Protocol.

About

Software developer · Houston, Texas

I build enterprise applications, automation, and full-stack systems — most recently spending 8+ years at JPMorgan Chase & Co. working on metrics tooling and firmwide data cataloging.

My background started in .NET and grew outward: these days I work across TypeScript and Node, Python, React, Kubernetes, and CI/CD pipelines, and I spend a lot of time on developer tooling built around the Model Context Protocol. I care about clean architecture, well-documented code, and leaning on good existing libraries rather than reinventing them.

Projects

Most of my side work lives at the intersection of music production and developer tooling — building Model Context Protocol servers that let an LLM do useful work against real music libraries and DAWs.

drummer-library

A TypeScript MCP server that indexes roughly 35,900 Groove Monkee drum MIDI files and makes them searchable by musical intent rather than filename.

Grooves are classified into a Turso/libSQL database with the MIDI stored inline, and embedded into ChromaDB for semantic search — so a query like “driving half-time groove around 95 BPM” returns real candidates instead of a directory listing. It exposes tools for searching, filtering, and inspecting grooves, plus a set of composition-focused prompts that encode reasoning workflows: semantic search first, then structured filtering when confidence is low.

Post 3

Occaecat aliqua consequat laborum ut ex aute aliqua culpa quis irure esse magna dolore quis. Proident fugiat labore eu laboris officia Lorem enim. Ipsum occaecat cillum ut tempor id sint aliqua incididunt nisi incididunt reprehenderit. Voluptate ad minim sint est aute aliquip esse occaecat tempor officia qui sunt. Aute ex ipsum id ut in est velit est laborum incididunt. Aliqua qui id do esse sunt eiusmod id deserunt eu nostrud aute sit ipsum. Deserunt esse cillum Lorem non magna adipisicing mollit amet consequat.