Experience

Proprietary work, told in prose.

Before founding Prava, I built internal tools and revenue systems in sports betting and ticketing. I came to engineering from the trading desk. Every tool below exists because my team and I needed it. Some of this work is proprietary; where a sanitized public repo exists, it's linked.

Caesars (William Hill): Sports Trading

I worked as a sports trader and taught myself to code by building the tools the desk was missing.

Live Odds Display

A real-time market view for the trading desk. An ingestion service I built separately pulls competitor odds via APIs into Google BigQuery; the display streams that data to traders over Socket.io, updating every five seconds with movement coloring: green when a line moves toward the bettor, red when it moves away. Traders used it to see exactly where our lines sat against the market on moneyline, spread, and total.

github.com/sbrcly/Odds-Display-Public · github.com/sbrcly/Odds-Tracker-Public

Live market view: green toward the bettor, red against. Click to play.

Trading Schedule

A scheduling system that pulls every game we offered across sports from BetRadar and BetGenius feeds and assigns traders to them based on their schedules and league coverage. Traders filter by date, keyword, or league; games without an assigned trader are flagged until someone owns them.

github.com/sbrcly/Trading-Schedule-Public

The trading schedule home screen: a table of upcoming games across sports with assigned traders. — Every game we offered, with an owner.

In-Play Odds Tracker

A Python tool charting in-play implied probability across the course of a game: our line against DraftKings, FanDuel, Pinnacle, and Unibet, update by update.

Chart of in-play implied probability for a Brewers at Cubs game, comparing Caesars' line against four competitors over two hours of updates. — Implied probability, Brewers @ Cubs: our line vs. the market.

Arbitrage Calculator

Compared every market we offered against roughly fifty competitor sportsbooks, live. Server side pulls the books' odds via APIs and emits over Socket.io on a one-minute cycle; the client flags any price of ours that opens an arbitrage a bettor could lock in, so traders could correct the line before it was exploited.

github.com/sbrcly/Arbitrage-Public

The arbitrage calculator's live table, with flagged arbitrage opportunities against competitor sportsbooks. — Live arb detection across ~50 books.

Etainement: Ticketing

Revenue systems for a ticket brokerage: a pricing portal and the browser tooling that connected it to the marketplaces. Both proprietary. Happy to walk through either in an interview.

Pricing Portal

The core system I worked on: a portal for analyzing our ticket inventory against the live market, and setting and adjusting prices across it.

Ticket Broker Extension

A Chrome extension that sits inside major ticketing sites, including Ticketmaster, and communicates with our pricing portal. One example of what it did: buyers set purchasing rules in the portal, and the extension fetched those rules and altered Ticketmaster's venue maps in-page, so the employees buying inventory knew exactly which seats to buy without having to think about it. Cross-origin messaging, DOM automation against sites hostile to automation, and state kept in sync between systems never designed to talk to each other.