The team
If you think you have something to contribute, tell us.
Simulation Baseball is small on purpose. It is also not finished, which is the honest reason this page exists.
We are not a studio with open headcount and a careers portal. We are a small group of people who have played this genre for a very long time, got tired of waiting for it to move, and started building the version we wanted. That means the useful thing you can offer is rarely a resume. It is usually an argument.
If any of the following sounds like you, write to us. Tell us what you would change and why. That is a better first message than a list of previous employers, and we read every one.
- Baseball people
- You have opinions about pitcher usage that you can defend with something other than vibes. You have run a fantasy or sim league for years and know exactly where those tools break. You do not need to write code to be useful here, and the engine is only as good as the people arguing with it.
- Engineers
- TypeScript, a simulation engine with a very large test suite, and a browser client that has to stay fast while a league of thirty teams advances a day. If the phrase "season boundary" makes you curious rather than tired, we should talk.
- Data and research
- Historical baseball data is messy in interesting ways. Turning a 1912 season line into ratings that behave, without laundering the era out of it, is genuinely hard and genuinely fun.
- Design and writing
- A front-office game lives or dies on how legible a screen of numbers is. If you have ever looked at a sim interface and known precisely why it hurt, that instinct is worth a lot.
Write to us
One address, read by an actual person. Tell us what you would work on and what you think we have wrong. If you would rather just play it first, that is the better move anyway.