I'm Josh. I build web apps, integrations, and data tools in Python and Django, mostly for the healthcare and insurance world.
For the last couple of years I've been the developer at a healthcare claims administrator, where my work runs from Django apps and SQL Server to X12 EDI files, Power BI, and the VMware boxes everything sits on. Outside of work I tinker with language models and run a small Kubernetes cluster at home.
I'm open to remote full-time roles and contract projects.
- Currently
- Software Developer at The Kempton Group Administrators
- Based in
- Bryan, TX, working remotely
- Education
- B.S. MIS, Oklahoma State
- jmhorn1115@gmail.com
Selected work
- Day jobAn internal platform in one Django monorepoA CRM, a job runner, a ticketing system, and an assistant, built and maintained in a single large, layered Django codebase.Django · Python · SQL · Monorepo
- Day jobTwo-way EDI for a claims systemA Python integration that builds outbound X12 files from the claims system and loads what vendors send back into it.Python · SQL · X12 834 / 837 / 835 · Managed file transfer
- Day jobClient & broker apps, and claim notificationsInternal Django apps for client and broker communication, including a notification system that replaced a manual outreach process.Django · Python · SQL
- Day jobClaims reporting, from Power BI to scheduled PythonDashboards that cut claims reporting turnaround by 30%, followed by automated daily, weekly, and monthly reports.Power BI · Python · pandas · SQL Server
How I work
- 1
I run what I build
The EDI integration I built runs every day, and when a payer rejects a file, I'm the one reading the acknowledgment. Owning software in production changes how you write it: clear logging, obvious failure modes, and code that's easy to debug.
- 2
Plain tools, used well
Django, a solid relational database, and a few scheduled jobs solve most business problems. I reach for something heavier when the problem calls for it, not before.
- 3
The front end is part of the job
Internal tools get used all day, so fast pages, clear forms, keyboard support, and layouts that work on a phone matter. This site is static HTML with very little JavaScript, and it prints cleanly.
- 4
Write it down
A short README, a diagram of where the data goes, a note on why a decision was made. It is the cheapest way to make a system easy for the next person to pick up.
What I do
Toolkit
- Languages
- Python, SQL, JavaScript, C#, HTML/CSS
- Backend
- Django, Django REST Framework, Wagtail CMS, FastAPI, SQLAlchemy
- AI / LLM
- LLM applications, Prompt engineering, RAG pipelines, MCP servers, Tool / function calling, Agentic workflows, OpenAI & Anthropic APIs, Ollama, PyTorch, Claude Code
- Frontend
- Astro, HTML5, CSS3, JavaScript, HTMX, Tailwind CSS, Vite, Responsive design
- Data
- PostgreSQL, SQL Server, pandas, Power BI, ETL, Reporting automation
- Healthcare EDI
- ANSI X12 834, ANSI X12 837, ANSI X12 835, Payer acknowledgments, CMS Section 111, Claims system integrations
- Infrastructure & IT
- VMware ESXi / vSphere, Proxmox, Docker, Kubernetes (Talos), Flux CD / GitOps, Traefik, cert-manager, Azure, GCP Cloud Run, Linux, ScreenConnect, PDQ Deploy / Inventory, Managed file transfer
Say hello
If you have something you'd like built or fixed, the easiest way to reach me is email: jmhorn1115@gmail.com.