Sports
MLB Director of Baseball Systems Job Description
The MLB Director of Baseball Systems leads the engineering and data infrastructure that powers a club's baseball operations — building the proprietary databases, internal applications, and data pipelines that analysts, scouts, coaches, and the front office use to make decisions. The role sits at the intersection of software engineering and baseball operations, requiring both technical depth (Python, SQL, cloud infrastructure) and genuine baseball domain knowledge to build tools that practitioners actually use.
Last updated
Role at a glance
- Typical education
- Bachelor's or Master's degree in computer science, software engineering, or data science
- Typical experience
- 6-10 years in software or data engineering, with 3-5 years in a baseball or sports analytics context
- Key certifications
- AWS or GCP cloud certification; no baseball-specific certifications required
- Top employer types
- All 30 MLB clubs; sports data vendors (Sportradar, TrackMan, Baseball Cloud); sports analytics consulting firms
- Growth outlook
- Growing; Hawk-Eye expansion to affiliated parks and AI tool adoption are driving scope expansion for all 30 MLB baseball systems departments
- AI impact (through 2030)
- Transformative — AI coding assistants accelerate engineering velocity; LLM-powered natural language query tools are beginning to appear in baseball operations workflows; directors are increasingly evaluating AI tooling as core infrastructure.
Duties and responsibilities
- Architect and maintain the club's internal baseball data platform, ingesting Statcast, Hawk-Eye, Trackman, and third-party vendor datasets into a unified data warehouse
- Lead a team of software engineers and data engineers building proprietary applications for scouting, roster management, and player development
- Manage API integrations with MLB Advanced Media (Baseball Savant), Sportradar, FanGraphs, and other commercial baseball data providers
- Oversee the club's player-development tracking platform — the system coaches use to log development notes, set player targets, and track mechanic benchmarks
- Build and maintain the internal trade-value and roster-projection models used by the GM and AGM in transaction decisions
- Manage cloud infrastructure (AWS or GCP) for the club's baseball systems, ensuring data security, uptime, and performance at scale
- Implement machine-learning model deployment pipelines for the R&D team's predictive models, including pitch design and injury-risk tools
- Coordinate with the Commissioner's Office technical staff on Statcast data feeds, API access agreements, and Hawk-Eye system integrations at affiliated minor-league parks
- Establish and enforce data governance standards across the baseball department to ensure consistent metric definitions across systems
- Recruit, hire, and develop software and data engineers with both technical skills and genuine baseball domain interest
Overview
Every modern MLB front office runs on proprietary software — internal applications that scouts use to file reports, databases where development coaches log player progress, decision-support tools that present the GM with a real-time CBT calculation, and pitch-design applications that deliver Rapsodo spin data to coaches' iPads in the bullpen. The Director of Baseball Systems builds, maintains, and evolves all of that infrastructure.
The role emerged as a distinct function as clubs invested heavily in their technology platforms through the 2010s. Early front offices that competed analytically — the Oakland A's, Tampa Bay Rays, Houston Astros, Cleveland — built proprietary data systems as competitive advantages. By the late 2010s, every club recognized the need for dedicated engineering leadership to manage what had become complex software organizations.
The data infrastructure function is the role's technical foundation. MLB's Statcast system generates enormous volumes of ball-tracking and player-tracking data — every pitch, every batted ball, every sprint across the outfield — and distributes it through the Baseball Savant API. The Director of Baseball Systems builds the pipelines that ingest this data into the club's data warehouse, the transformations that convert raw tracking coordinates into usable metrics, and the query layers that analysts and coaches use to retrieve insights. They do the same for third-party vendors: Trackman, Rapsodo, FanGraphs licensed data, Sportradar game feeds.
Application development is the other major pillar. A typical club's baseball systems team maintains a suite of internal applications: a scouting report platform (where area scouts file reports from the road that flow into the draft board), a player development tracking system (where minor-league coaches log workout notes and set development benchmarks), a roster management tool (the operational database the baseball operations team uses for 40-man tracking), and a video tagging and annotation system integrated with Synergy or BATS. Each of these applications requires ongoing development, maintenance, and iteration as user needs evolve.
Stay close to the baseball product: the best Directors of Baseball Systems embed themselves in baseball department conversations — attending scout meetings, sitting in on R&D model presentations, talking to coaches about what information they actually want at their fingertips. A system built without genuine understanding of how scouts grade prospects or how pitching coaches use pitch-shape data produces tools that go unused regardless of their technical quality.
Qualifications
Directors of Baseball Systems typically have strong computer science or data engineering backgrounds combined with deep personal engagement with baseball analytics. The role requires technical leadership capability alongside enough baseball fluency to understand the domain problems being solved.
Educational background:
- Bachelor's degree in computer science, software engineering, or a related quantitative field
- Master's in computer science or data science increasingly common; some directors hold advanced degrees in statistics or applied mathematics
- Formal degree in sport management with a strong technical track is less common but exists among candidates who transitioned from the analytics side
Technical skills required:
- Software engineering: Python (primary language in baseball analytics), SQL, REST API development, and web application frameworks
- Data engineering: ETL pipeline design, data warehouse management (Snowflake, BigQuery, or Redshift), streaming data ingestion, and dbt or similar transformation tooling
- Cloud infrastructure: AWS or GCP infrastructure management, Kubernetes or Docker for containerized application deployment, CI/CD pipeline management
- Machine learning infrastructure: MLflow or similar for model versioning and deployment, familiarity with model monitoring in production environments
- Database design: ability to design schemas that balance analytical query performance with transactional application needs
Baseball domain knowledge:
- Statcast metric literacy: understanding of Hawk-Eye tracking data structure, Baseball Savant API, and the derived metrics (sprint speed, outs-above-average, run value) built on raw tracking data
- Minor-league system structure: how player development tracking needs differ across rookie, Low-A, High-A, Double-A, and Triple-A contexts
- CBA awareness: how contract and transaction data must be structured to support the baseball operations team's compliance and decision needs
Leadership:
- 3–7 years managing engineering teams; comfort with hiring, performance management, and technical roadmap prioritization
- Ability to translate baseball operations requirements into engineering specifications without baseball practitioners needing to know the technical details
Career outlook
The MLB Director of Baseball Systems role has grown from a novelty to a standard front-office position in roughly 15 years. All 30 clubs now maintain some version of this function, though the team size and technical sophistication vary significantly across the market.
Salary range: $200K–$320K at small-market clubs with lean engineering teams; $320K–$500K at large-market organizations with substantial software development infrastructure. Some clubs located in tech-hub cities (Dodgers in Los Angeles, Giants in San Francisco, Red Sox in Boston, Yankees in New York) face direct competition from tech company compensation packages and adjust accordingly.
The technical sophistication of these functions has grown sharply. Clubs that started with one or two developers maintaining an internal scouting database now run engineering teams of 8–20 people building production applications used by scouts, coaches, and front-office staff simultaneously. The Director of Baseball Systems at these organizations is an engineering executive, not just a technically skilled analyst.
The Hawk-Eye installation expansion into affiliated minor-league parks has created a new wave of infrastructure requirements. As Statcast-quality ball tracking becomes available at Double-A and Triple-A, systems directors must extend their data pipelines and application layers to incorporate that data for the player development staff. This expansion of scope is creating demand for larger baseball systems teams.
Career paths from the Director level include VP of Baseball Technology or Chief Technology Officer (CTO) roles at well-resourced clubs, lateral transitions to larger tech companies in sports data or sports SaaS roles (Sportradar, Baseball Cloud, TrackMan USA), or transitions into analytics leadership where technical depth becomes the foundation for a baseball research role. Some Directors of Baseball Systems transition into R&D or analytics leadership as their baseball understanding deepens over years in the role.
Sample cover letter
Dear [GM / VP of Baseball Operations],
I am applying for the Director of Baseball Systems position with [Club]. As Senior Baseball Systems Engineer at [Organization] for the past four years, I have built and maintained the data infrastructure supporting a 15-analyst baseball operations department — including our Statcast pipeline, Trackman integration, internal scouting platform, and the 40-man roster management application used daily by our baseball operations team.
My core technical stack is Python and SQL on a Snowflake data warehouse hosted on AWS, with Airflow orchestrating our nightly data pipelines from Baseball Savant, Sportradar, and our affiliated minor-league Trackman installations. I built our current player development tracking application from a Flask/PostgreSQL foundation with a React front end — the system our minor-league coaches use to log development notes from all four affiliate levels and that our coordinators access to monitor progress against player benchmarks.
I am also the technical lead on our pitch-design model deployment pipeline, taking R&D-built models from Jupyter notebooks into production environments that bullpen coaches access via iPad. I understand how to translate what the R&D team builds into what coaches and scouts actually use in daily operations.
I am drawn to [Club] because of your commitment to technology investment at all affiliate levels and the opportunity to scale systems to match your organizational depth. I would welcome the opportunity to discuss your current infrastructure challenges and how my background fits.
Thank you for your time.
Sincerely, [Your Name]
Frequently asked questions
- What does an MLB Director of Baseball Systems do?
- The MLB Director of Baseball Systems leads the engineering and data infrastructure that powers a club's baseball operations — building the proprietary databases, internal applications, and data pipelines that analysts, scouts, coaches, and the front office use to make decisions. The role sits at the intersection of software engineering and baseball operations, requiring both technical depth (Python, SQL, cloud infrastructure) and genuine baseball domain knowledge to build tools that practitioners actually use.
- What are the main duties of an MLB Director of Baseball Systems?
- Core duties include: architect and maintain the club's internal baseball data platform, ingesting Statcast, Hawk-Eye, Trackman, and third-party vendor datasets into a unified data warehouse; lead a team of software engineers and data engineers building proprietary applications for scouting, roster management, and player development; and manage API integrations with MLB Advanced Media (Baseball Savant), Sportradar, FanGraphs, and other commercial baseball data providers.
- What technology stack do MLB baseball systems departments typically use?
- Python is the dominant language for baseball analytics applications; SQL (PostgreSQL or Snowflake) powers data warehousing. Cloud infrastructure runs primarily on AWS or GCP depending on the club's preference and existing corporate relationships. R remains common in legacy R&D code but is largely being supplanted by Python for new development. Some clubs use dbt for data transformation pipelines, Airflow for workflow orchestration, and MLflow or similar for machine learning model management.
- How does the Director of Baseball Systems interface with the R&D and analytics teams?
- The Director of Baseball Systems provides infrastructure that R&D and analytics teams rely on to do their work. When an R&D analyst builds a new pitch-design model, the Baseball Systems team handles productionizing it — turning a research notebook into a deployed application that coaches can access from the dugout on an iPad. The relationship requires systems directors who understand the analytical work well enough to build appropriate tooling without requiring analysts to be their own engineers.
- What is Statcast and how does it affect the baseball systems function?
- Statcast is MLB's tracking system, built on Hawk-Eye cameras and Doppler radar, that captures ball and player movement data on every play. It generates position coordinates, velocity, spin rate, and dozens of derived metrics. MLB distributes Statcast data through the Baseball Savant API. The Director of Baseball Systems is responsible for ingesting this data reliably, storing it efficiently, and making it queryable through the club's internal systems. Statcast data volumes are large — every pitch, every batted ball, every player position update from every game.
- How is AI changing the baseball systems director role?
- Large language models are beginning to appear in baseball operations contexts — AI tools that can query a natural-language question against the club's internal database, or summarize a prospect's development report across multiple scouting notes. GitHub Copilot and similar AI coding assistants have accelerated the engineering team's velocity in building and maintaining proprietary baseball tools. The Director of Baseball Systems increasingly evaluates and deploys these AI tools as infrastructure rather than just managing traditional data pipelines.
- What career paths lead to Director of Baseball Systems?
- Most directors arrive through one of two backgrounds: a software engineering career outside baseball followed by a transition into a baseball operations engineering role (often starting as a baseball systems engineer or analyst), or an analytics path within baseball that evolved into building the tools underlying the analytical work. The MIT Sloan Sports Analytics Conference, SABR Analytics Conference, and public baseball analytics communities (Baseball Prospectus, FanGraphs, The Athletic's analytics coverage) are networking and visibility channels for candidates transitioning into the profession.
Related job descriptions
See all Sports jobs →- MLB Baseball Systems Developer$110K–$200K
An MLB Baseball Systems Developer builds and maintains the software infrastructure that powers a club's baseball operations department — data pipelines that ingest Statcast and Hawk-Eye feeds, internal analytics platforms used by analysts and coaches, scouting report systems, player development dashboards, and the databases that store the organization's proprietary player information. The role sits at the intersection of software engineering and baseball analytics.
- MLB Director of Baseball Operations$200K–$600K
The MLB Director of Baseball Operations serves as the operational backbone of a club's baseball department, translating the GM's strategic decisions into daily execution across transactions, roster management, travel coordination, spring training logistics, and CBA compliance. The role is distinct from a baseball-analytics director — it is operational, not primarily analytical — and demands mastery of the Commissioner's Office transaction portal, waiver-wire mechanics, and the administrative requirements of running a 40-man roster organization through a 162-game season.
- MLB Baseball Operations Analyst$80K–$160K
An MLB Baseball Operations Analyst uses statistical modeling, Statcast data, and machine learning techniques to generate player valuations, trade evaluations, and strategic recommendations for the front office. They sit within the research and development function of a baseball operations department, producing both ongoing analytical infrastructure — player projection models, WAR estimates, contract valuations — and ad-hoc analyses that respond to real-time roster construction questions.
- MLB Baseball Operations Coordinator$55K–$90K
An MLB Baseball Operations Coordinator handles the administrative infrastructure that keeps a 40-man roster, transaction wire, and player contract database running accurately and in compliance with CBA requirements. They process IL placements, 40-man roster moves, option and DFA paperwork, and coordinate with MLB's transaction system to ensure that every roster change is documented correctly — supporting the GMs, AGMs, and analysts who make the strategic decisions.
- MLB President of Baseball Operations$3000K–$10000K
The President of Baseball Operations is the most senior baseball decision-maker within an MLB organization, sitting above the general manager and overseeing all facets of roster construction, player development, scouting, analytics, and competitive strategy. The role emerged as a distinct executive layer in the mid-2010s, pioneered by appointments like Andrew Friedman in Los Angeles, Alex Anthopoulos in Atlanta, and David Stearns in New York, as organizations recognized that the scale of modern baseball operations — spanning MLB, four MiLB affiliates, the international signing infrastructure, the draft, and the analytics department — exceeded what a single GM title could effectively manage. In 2025, approximately 20-25 of the 30 MLB clubs have an explicit POBO or equivalent above the GM.
- MLB Vice President of Baseball Operations$300K–$1000K
An MLB Vice President of Baseball Operations sits in the upper tier of a club's baseball operations hierarchy — typically reporting directly to the General Manager or President of Baseball Operations — and oversees specific operational domains such as player development, analytics, amateur scouting, pro scouting, or administration. The role bridges the gap between executive strategy and departmental execution, ensuring that the GM's roster-building vision is implemented coherently across multiple teams, data systems, and organizational layers from the international signing pipeline through the 26-man roster.