I’m a software engineer at The Weather Company, where the day-to-day is mostly Python backend test automation on the SUN QA team. Outside the day job, I work across the stack — Next.js and TypeScript on the front end and API layer, DevOps and CI work to keep the pipes moving, Linux administration to keep the servers honest, and — when the mood strikes — lower-level programming in NASM assembly.
Background & education
Before The Weather Company I was Director of Software Engineering at Fidelity Investments. I studied Applied Mathematics at North Carolina State University (2000–2004), where I spent more time than was strictly reasonable on analysis, algebra, and PDEs. I’m a member of ACM, SIAM, IEEE, and Mensa.
Outside the day job, my open-source work splits across two umbrellas — github.com/jedi-knights for the larger infrastructure work and github.com/ocrosby for personal projects, tools, and lab code.
Also a scattering of language labs across Go, Python, Rust, Lua, C, C++, TypeScript, R, and NASM, plus notes on physics, math, and astronomy calculations — because the best way to learn a language is to build something small in it.Open-source portfolio (7 areas)
market-bridge, an MCP server bridging Tradovate, Bookmap, and Thinkorswim to Claude for real-time /ES futures data; and strike-pilot, a Python SPX-bias / credit-spread signal engine.identity-platform-go) built as clean microservices, plus a configurable reverse-proxy gateway (api-gateway) with rate limiting, circuit breaking, and MCP routing.yoda.nvim plus a family of modular plugins (yoda-core.nvim, yoda-window.nvim, yoda-logging.nvim, yoda-diagnostics.nvim, yoda-terminal.nvim, pytest.nvim, yaml.nvim, go.nvim, python.nvim, and pytest-atlas.nvim for pytest-bdd navigation).go-semantic-release (which powers this site’s release workflow), nasm-lint (Rust-based NASM static analyzer with CLI, LSP, and GitHub Action), kyber (Go quality metrics), py-cyclo (Python cyclomatic-complexity checker), neospec (Neovim test/coverage runner in Go), and ctestprobe — a unit testing framework for C, distributed via a Homebrew tap.holocron, a single-binary Kafka-style event streaming broker in Go, with a Python SDK.claude-config (my Claude Code setup, GNU Stow–managed), my Neovim config, my macOS dotfiles, and a learn-neovim walkthrough.
The through-line is: build the boring plumbing well, in the language that fits, and open-source it.
For the editor, shell, languages, and release stack I actually reach for day to day, see /uses/. For what I’m actively focused on right now (updated every 4–6 weeks), see /now/. To get new posts as they land — RSS or email — see /subscribe/.
Experience
- The Weather Company — Mar 2025–present. Senior Software Engineer on the SUN QA team; day-to-day is Python backend-test automation, but the role essentially spans team leadership, overall QA evolution, and a lot of software architecture — without the formal titles for any of it.
- Fidelity Investments — 2015–2024. SE in Test → Principal Engineer → Architect over nine years across trading and internal-tooling orgs.
- Sageworks — 2014–2015. Senior Software Engineer on the analytics platform.
- Paragon Application Systems — 2010–2014. Senior Software Engineer on payments-testing simulators.
- IBM / Lenovo — 2000–2010. Software Engineer → Staff → Senior → Architect across the ThinkPad manufacturing test and firmware stack.
Away from a keyboard, I cook — from scratch, mostly, because measuring things is fun. I watch a lot of film and TV, keep a curated /music/ playlist running most of the day, and follow soccer more closely than is probably healthy — especially the NWSL, and specifically Gotham FC.
Contact
- LinkedIn — linkedin.com/in/omarcrosby
- X — x.com/crosbyomar
- Instagram — instagram.com/omar.crosby
- Facebook — facebook.com/omar.crosby
- Email — omar.crosby@gmail.com
- GitHub (personal) — github.com/ocrosby
- GitHub (projects) — github.com/jedi-knights