About

Scott Barclay

Full-Stack Engineer

From sports trader on a Las Vegas trading floor to full-stack engineer shipping an AI-powered prayer and scripture app.

BUYER’S SCREEN · TICKETMASTER EVENT PAGE Hartwell Tour · Northside Arena · Sat 7:00 PM · synthetic venue, synthetic rule STAGE 101 102 103 104 105 106 107 201 202 203 204 205 206 207 208 209 Rule 01 · Section 105 · Rows B to D 15 seats shaded · max 4 Message · Lower bowl only. Stop at $240. 15 seats painted · section 105 · rule 01 THE STOP OVERLAY STOP When the rule set says stop, this replaces the paint. Full screen, until a manager lifts it. STOP The rule set says stop. Buying is halted for this event. Hartwell Tour · Sat 7:00 PM · lifted by a manager, not by the buyer BUYER’S SCREEN · TICKETMASTER EVENT PAGE Hartwell Tour · Northside Arena · Sat 7:00 PM · synthetic venue, synthetic rule STAGE 101 102 103 104 105 106 107 201 202 203 204 205 206 207 208 209 Rule 01 · Section 105 · Rows B to D 15 seats shaded · max 4 Message · Lower bowl only. Stop at $240. 15 seats painted · section 105 · rule 01 THE STOP OVERLAY STOP When the rule set says stop, this replaces the paint. Full screen, until a manager lifts it.

Featured · engineering

Buyer extension

Inside Ticketmaster during an on-sale, painting a manager's buy rules onto the map a buyer is already looking at.

Read the case study

The trading floor needed tools it did not have, so I built them. The first was a Python script that gave every matchup its proper ID and mapped it to a trader. That script became a department: I helped hire a data analyst, and the two of us built tools for the floor, reporting to a senior vice president. I have been writing software since.

Most recently I designed, built, and shipped Prava, an AI-powered iOS prayer and scripture app, as its only engineer. Before that I spent nearly four years at Etainement, a small team of ticket brokers that did some of the highest volume in the country, integrating with Ticketmaster and other ticketing services through custom Chrome extensions that talked to our pricing portal. There was no blueprint and no documentation for any of it, and I learned more there than I think I could have in any other industry.

The trading desk tools are still here too: a live odds console, an arbitrage detector that caught the gaps sharp bettors were picking off, and a trading schedule. Each was built alone, and together they saved traders hours a week.

I have learned what I wanted to learn from shipping an app solo. I want to be on a team again.

Outside work I read, keep learning, run marathons, play tennis, and spend the rest of my time with my family. Where my focus is now:

Reading
Crime and Punishment, Fyodor DostoevskyThe Spirit of the Liturgy, Joseph RatzingerWriting to Learn, William ZinsserDesigning Data-Intensive Applications, Martin Kleppmann (reread)
Studying
AI engineering
Running
Maui Oceanfront Marathon, 17 January 2027

Work

Faith Platforms Inc.

Sole engineer · 2025 to now

Prava

iOS · 5.0 · 58 ratings on the App Store
Prava's home screen for the 17th Sunday in Ordinary Time: a verse card from Romans 8, this week's readings with completed checkmarks, and the Prayers and Creeds row.
The Pray movement of Lectio Divina: Romans 8:28-30 with a phrase highlighted, a text field labeled In your own words, and a Help me pray this button.
The daily journal asking How was yesterday, with Light, Normal, and Heavy load options and yes or no questions including Pray, Read your Bible, and Confess something to God.
A Circle group screen: nine members reading Romans, this week's verse, and a feed of marks such as a member praying the Examen.

An iOS prayer and scripture app built around the Church's week rather than a streak. Every AI feature in it reads a versioned prompt with a tested fallback behind it. Designed, built, and shipped solo.

  • TypeScript
  • Next.js
  • Capacitor
  • Postgres
  • Anthropic API

Read the case study  ·  App Store

Etainement

Full-stack engineer · 2022 to 2026

Buyer extension

Chrome extension · proprietary
BUYER’S SCREEN · TICKETMASTER EVENT PAGE Hartwell Tour · Northside Arena · Sat 7:00 PM · synthetic venue, synthetic rule STAGE 101 102 103 104 105 106 107 201 202 203 204 205 206 207 208 209 Rule 01 · Section 105 · Rows B to D 15 seats shaded · max 4 Message · Lower bowl only. Stop at $240. 15 seats painted · section 105 · rule 01 THE STOP OVERLAY STOP When the rule set says stop, this replaces the paint. Full screen, until a manager lifts it. STOP The rule set says stop. Buying is halted for this event. Hartwell Tour · Sat 7:00 PM · lifted by a manager, not by the buyer BUYER’S SCREEN · TICKETMASTER EVENT PAGE Hartwell Tour · Northside Arena · Sat 7:00 PM · synthetic venue, synthetic rule STAGE 101 102 103 104 105 106 107 201 202 203 204 205 206 207 208 209 Rule 01 · Section 105 · Rows B to D 15 seats shaded · max 4 Message · Lower bowl only. Stop at $240. 15 seats painted · section 105 · rule 01 THE STOP OVERLAY STOP When the rule set says stop, this replaces the paint. Full screen, until a manager lifts it.

A Chrome extension that ran inside Ticketmaster for over a hundred buyers at a small team of ticket brokers that did some of the highest volume in the country. It painted the manager's buy rules onto Ticketmaster's seat map, recorded each purchase as it happened, and brought the verification code to the screen that asked for it. I built every part of it.

  • Chrome MV3
  • JavaScript
  • React
  • Node and Express
  • Python
  • Postgres
  • Firestore
  • BigQuery

Read the case study

  • Pricing portal

    Where analysts priced inventory against the live market and on-sale managers drew the buy rules the extension painted. A team system; the parts I built are named on its page.

    • React
    • Redux
    • Node
    • BigQuery
    • Redis

    Read the case study

  • On-sale monitor

    The extension's telemetry as live tables: who is in which Ticketmaster queue, what they have carted, what failed, and what was bought. Built alone.

    • React
    • Firestore
    • Firebase

    Read the case study

Caesars Sportsbook

Software developer, promoted from trader · 2018 to 2022

Live odds console

sportsbook trading desk · 33 s recording

Competitor prices pulled into BigQuery and streamed to the trading desk over Socket.io every five seconds. Green when a line moves toward the bettor, red when it moves away. This is the console running live on the desk.

  • Node
  • Socket.io
  • BigQuery
  • MySQL

Write-up: Odds-Display-Public

  • The arbitrage detector's live table: rows of flagged opportunities, each with the game, the market, the book's price, the competitor's price, and the percentage a bettor could lock in.

    Arbitrage detector

    Every market the book offered, compared against about fifty competitors. Any price a bettor could lock in from both sides is flagged so a trader can move the line first.

    • Node
    • Socket.io
    • MySQL
    • GCP

    Write-up: Arbitrage-Public

  • Trading schedule: games across sports with assigned traders

    Trading schedule

    Pulls every game from the data feeds and assigns traders by shift and league coverage. A game nobody owns stays flagged until someone takes it.

    • Node
    • Express
    • MySQL
    • feed APIs

    Write-up: Trading-Schedule-Public

Contact

scottbarclay02@gmail.com

Replies within a day. Happy to walk through any project here in as much depth as you like, including the ones whose code I cannot show.