skip to content
JS John Sosoka
John Sosoka

Hi, I'm John

A Boise based software engineer.

I'm a father, husband, and software engineer living in Boise, Idaho. I'm a backend developer and usually work with Java and Python day to day. Over the course of my career I've worked in a variety of roles in software development, including software tester, release engineer, software engineer, principal software engineer, and tech lead.

What I'm Working On

Agents, orchestration, and tool use

Lately I've been working a lot with Large Language Models, particularly agent design and orchestration. A while back I wired up a language model to a collection of tools that allowed it to browse the internet and build themed Spotify playlists. Once I witnessed the model's capacity for planning and tool usage, I was hooked. I've been working on LM/agent related projects ever since.

I've been on GitHub for a while under a pseudonym, but I keep a more polished profile at github.com/johnsosoka. That's where the code examples accompanying blog posts live. Things I've built and care to keep a record of end up on the projects page.

Beyond the Code

Trails, pinball, and projects around the house

When I'm not coding, you can find me hiking the trails around Boise with my dogs, hanging out with my family, or working on projects around the house.

I also really enjoy pinball and have been playing quite a bit at the Pinball Museum in Garden City. I haven't competed recently, but I do have an IFPA profile :).

A few other corners of the site keep track of what holds my attention outside of work — all of it collected under Beyond.

This Website

A base of operations

This website is intended to serve as a base of operations for me. I enjoy running it as somebody might enjoy keeping a garden — I like contributing to it and watching it grow, but I don't have any ambitious plans for it.

As I'm not a professional writer and this is a very low traffic site, I might edit or update posts after they are published. A public record of all changes is available in the GitHub repository.

Get in Touch

Friendly requests, comments, and corrections are always welcome. Be sure to leave a valid e-mail address so that I can follow up with you.