Los Angeles Dodgers ยท Baseball Operations Product Development
I want to help the Dodgers build tools that baseball people trust.
I built my career around systems that had to work under pressure, then moved intentionally toward product design because I kept seeing the same failure: powerful tools losing their value at the interface. The Dodgers role is the rare opening where that background is not a detour. It is the point.
- Sports product
- Current sports-product work gives this application a real anchor rather than a generic design pitch.
- Design craft
- My strongest product-design proof is where I have had to understand technical users, map workflows, prototype decisions, and help implementation teams move.
Why I applied
This is the role where the unusual parts of my background become useful.
I am pursuing this role because it sits in the exact gap that has shaped my career: strong systems can still fail their users when the interface treats data flow, operational risk, and implementation reality as somebody else's problem.
The Dodgers are asking for product design close to Baseball Operations, where the users are experts and the stakes are real. That is where my non-traditional background becomes useful: I can talk with analysts, scouts, engineers, and leaders without losing the decision the tool is supposed to improve.
Fumaro Sports is the current expression of that work. It is primarily fan-facing today, but the discipline behind it is directly relevant here: clear information architecture, understandable model output, context that explains why a signal matters, and prototypes that survive contact with real constraints.
What to notice first
The short version for a recruiter screen.
My background is non-traditional for a product designer, but it is not random. I spent 22 years making complex systems work for people under pressure, and I now apply that discipline to product design for expert users.
- This is product design for expert baseball users, not decorative UI work.
- I can talk with analysts, scouts, player-development staff, engineers, and leaders without losing the actual decision the tool is supposed to improve.
- Fumaro Sports gives the application a current sports-product anchor, backed by years of delivery in environments where trust, adoption, and technical correctness mattered.
Scoria Software SolutionsFounder and Principal Software Architect | March 2025 - Present
Current proof that I am already working through the hard part: how sports software can show context, confidence, and next-step value without becoming another black box.
Resume evidence
- Building Fumaro Sports as a sports-first predictive intelligence product with MLB-first data surfaces, Azure Databricks-backed analytics, and a public multi-sport web runtime.
- Designing research, prototype, feedback, telemetry, staged beta, and human review loops so sports recommendations can improve without hiding uncertainty from users.
- Using Figma alongside schema-driven UI, TypeScript implementation, generated documents, and design-system decisions to move ideas into working product surfaces.
Principal Architect | January 2019 - Present
Proof that I can interview real users, map messy workflows, and turn those conversations into tools and roadmaps that change how work gets done.
Resume evidence
- Led discovery, stakeholder interviews, workflow mapping, and implementation planning across 26 major priorities, translating ambiguous needs into roadmaps, dashboards, procurement choices, and training paths.
- Built a microfilm digitization tool that converted more than a century of public records into OCR/ICR-optimized PDF/A assets with metadata in a single 21-hour run, shortening records-request turnaround from weeks or months to days or hours.
Principal / Senior Cybersecurity Architect and Microsoft Global Tech Team Senior Customer Engineer | 2020 - 2024
Proof that I can make dense technical decisions usable for leaders, engineers, operators, and high-pressure teams.
Resume evidence
- Turned SIEM, SOAR, SASE, GRC, cloud, and architecture decisions into proof-of-concept reviews, reusable pattern libraries, change workflows, and executive-ready tradeoff discussions.
- Supported 37 Microsoft dedicated accounts, including high-visibility media operations around the 2021 Olympic Games, while translating competing technical options into operationally safe decisions.
Why this is worth an interview.
Fumaro Sports is the closest proof. The enterprise work matters because it shows that I can move a complicated product from user need to usable system without losing trust, context, or technical realism.
Current application focusLos Angeles Dodgers - Product Designer, Baseball Operations
The role asks for someone who can understand baseball evaluators, shape product ideas with them, and make software easier to trust and use. That is the conversation I am asking for.
Dedicated public page for the LAD Product Designer application. Dodgers-specific resume downloads remain private unless explicitly requested.
Featured proof pointFumaro Sports Product System
Fumaro Sports is where I am actively working through the product problem: how to show context, uncertainty, and next-step value in sports decision support.
Supporting strengthEngineering-Aware Product Design
The architecture background matters because Baseball Operations product work cannot stop at attractive mockups. The design has to respect data, security, APIs, engineering capacity, and operational reality.
Contextual fitSports, Live-Event, and Los Angeles Context
Production training, Olympic-broadcaster support, Los Angeles public-sector work, and regulated operations add useful context for a high-visibility sports organization.
What I would bring to Baseball Operations product work.
Hiring signalResearch with expert users
I am at my best when the user already knows the domain deeply and the design has to make their judgment easier, faster, and better supported.
Evidence
- Building Fumaro Sports as a live sports product with MLB-first data surfaces, a public multi-sport web runtime, and Azure Databricks-backed analytics.
- Modeled Second Order context such as venues, weather, umpire crews, rivalry conditions, schedule density, home-road splits, and travel effects so users can understand what changed around a matchup.
- Led stakeholder interviews, workflow mapping, and implementation planning at Bedrock across field, administrative, compliance, executive, and public-facing users.
Prototype to buildable handoff
The point is not just polished screens. The point is a prototype clear enough that users can react honestly and engineers can see how to build it.
Evidence
- Use Figma in current Scoria and Fumaro work for product exploration, collaboration, high-fidelity prototyping, and handoff.
- Developed JSON-schema front-end patterns that reduced each interface codebase 25-30% through shared components across web, native, desktop, API, CLI, and MCP surfaces.
- Produced working prototypes, application flows, generated documents, and delivery automation that tied user needs to engineering constraints and operating risk.
Trustworthy analytics and AI output
If a tool recommends, ranks, or warns, the user should be able to see why. That is a design problem as much as a data problem.
Evidence
- Designing Fumaro around research input, prototype/build loops, feedback submission, telemetry-aware runtime logging, staged review, and human-in-the-loop release controls.
- Designed deterministic AI and development guardrails so generated or model-assisted behavior remains auditable, repeatable, and reviewable.
- Built model- and platform-agnostic orchestration across enterprise, consumer, Azure AI Foundry, Ollama, and local-model contexts while preserving approval paths.
Cross-functional delivery
I have repeatedly had to turn messy stakeholder needs into decisions, roadmaps, prototypes, and working systems. That matters when product, baseball, data, and engineering all have to trust the same tool.
Evidence
- Led RFP, demonstration, proof-of-concept, and evaluation processes for SIEM, SOAR, SASE, and GRC platforms, balancing user workflows, functional requirements, security outcomes, and cost.
- Drove ServiceNow GRC and change-management integration, increasing legitimate change tickets from a handful per month to dozens per week while reducing change delivery cycles from weeks to days or hours.
- Created Wells Fargo architecture pattern libraries and standardized review paths that turned technical ambiguity into repeatable choices for thousands of downstream application teams.
Engineering fluency
I can design with realistic knowledge of APIs, data contracts, security boundaries, and delivery tradeoffs, so the work is less likely to die between prototype and implementation.
Evidence
- Works fluently across TypeScript, JavaScript, Astro, React patterns, REST and GraphQL API concerns, JSON Schema, document generation, CI/CD, GitHub, Azure DevOps, telemetry, and cost-aware delivery.
- Performed an in-depth Azure and Google Cloud Platform third-party-risk and security comparison that clarified how functional, security, and economic constraints should govern multi-cloud product and platform decisions.
- Carries enough security, identity, access lifecycle, RBAC, SIEM/SOAR/SASE, WAF, DDoS, anti-bot, and secure-SDLC depth to keep Baseball Operations tools credible with engineering and platform teams.
Sports, live-event, and Los Angeles context
The sports fit is honest: current sports-product work, live-event discipline, high-visibility support experience, and a long-running attachment to Los Angeles and the Dodgers.
Evidence
- Entertainment production background gives real venue, live-event, time-bound, public-facing discipline without overstating prior MLB stadium ownership.
- Fumaro Sports under Scoria is actively becoming a live sports analytics proof of concept at poc.fumaro.pro with Azure Databricks as the analytics backend, a public multi-sport web runtime, MLB-first data surfaces, feedback patterns, telemetry-aware runtime logging, and human-in-the-loop release controls.
- Supported a broadcaster involved in the 2021 Olympic Games as a Microsoft senior architecture design and operational escalation resource for high-visibility, time-bound media technology operations.
- Understands Los Angeles as a professional market through local work history and public-sector experience, while keeping baseball-domain claims grounded in Fumaro Sports and current learning rather than overstating front-office tenure.
Communication range and adjacent craft
These details are secondary, but useful: they point to a designer who takes craft, communication, and how people work seriously.
Evidence
- French and Italian are proficient but rusty; Spanish is intermediate with active daily learning; Japanese is novice with active daily learning.
- Creative-production background includes University of Michigan Design & Production study plus archival lighting design, sound design, and stage-management work that is useful context for collaboration, rhythm, and high-visibility delivery.
- Adjacent hands-on domains include electrical and non-IT electrical systems, strong culinary craft, canine training and wellness context through California Cattle Dogs LLC, and sports analysis through Fumaro Sports.
How I work
How he would work with analysts, scouts, and engineers.
The useful pattern is practical: learn the decision first, show context clearly, prototype the risky part early, and keep improving the tool after real users touch it.
Working patternUnderstand the decision first
Start with the evaluator's real decision: what must be understood, compared, challenged, or explained before someone can act with confidence.
A good Baseball Operations tool should feel like it respects how expert users already think, not like it is forcing them through a generic dashboard.
Working patternMake the signal explain itself
Show the context behind a recommendation: confidence, provenance, edge cases, model limits, and the reason a signal deserves attention.
That is the practical value of Fumaro's Second Order context work: users should not have to accept a black box when they are making a baseball decision.
Working patternDesign what engineering can actually build
Prototype the riskiest parts early: the screen the user has to trust, the data the system must expose, and the handoff engineering needs in order to build it cleanly.
The architecture background is useful only when it makes the design clearer, more buildable, and less likely to collapse between mockup and implementation.
Working patternLet the product keep learning
Build in feedback loops, staged review, telemetry, and change notes so the tool can improve after real users start depending on it.
Baseball software has to learn from a season of use. A portfolio screenshot is not enough.
LADThe honest boundary.
I have not worked inside the Dodgers or an MLB front office. The claim here is more specific and more useful: I am already building sports-product judgment through Fumaro Sports, and I have a long record of making complicated tools usable for expert users, executives, engineers, and high-pressure operating teams.