Archive for Teams

Chapman Chooses Another Year in Pinstripes

Aroldis Chapman, most recently seen allowing a home run to José Altuve that sent the Astros to the World Series, has reportedly signed a contract extension with the Yankees that will keep him in New York through the 2022 season. The deal, as reported, adds one year and $18 million onto the two years and $30 million that were left on Chapman’s previous contract, and answers the question — open since that Altuve home run — of whether Chapman would exercise the opt out in his contract and become a free agent this offseason.

Last week, Jon Heyman reported that Chapman, 32, planned to exercise his opt-out in the event he was unable to reach a deal with the Yankees for an additional year. That move would almost certainly have resulted in the Yankees extending Chapman a qualifying offer (this year set at $17.8 million), Chapman declining to sign at that price, and Chapman and his agent subsequently seeking a deal that involved the signing team giving up a draft pick.

Having no doubt watched the Craig Kimbrel experience play out last offseason, and presumably wanting no part of it, it makes sense that Chapman would pursue an extension in New York rather than test free agency with a QO hanging around his neck. This is now the second time the left-hander has chosen to return to New York (the first time, when he signed his current contract, came in 2016) and this extension guarantees him three more years in the city he calls home — not to mention a worry-free winter.

The Yankees benefit too. Retaining Chapman means that their excellent 2019 relief corps can return mostly intact, and in particular that Zack Britton, Adam Ottavino, Tommy Kahnle, and Chad Green can return to the roles they played last season, and are presumably comfortable with (that’s especially true for Britton, who for obvious reasons threw in many of the same sorts of situations as Chapman). That’s not to discount Chapman’s contributions on their own terms, as they were excellent last year (a 2.28 FIP and a 36.2% strikeout rate over 57 innings pitched) despite modest declines in fastball velocity that began in the middle of 2018 and persisted in 2019:

It’s hard to know what to make of Chapman’s velocity decline or what it augurs for his future effectiveness. As far as I can tell, the conventional wisdom on relievers is that they’re good until they’re not, except for elite relievers, who are good for longer until they’re not. Chapman definitely falls into the latter category, and as Ben Clemen’s wrote earlier this year, he’s already demonstrated success in moving somewhat away from his fastball in favor of sliders inside the strike zone. Since Ben wrote that piece, Chapman has gravitated even more towards his slider, throwing it 31.1% of the time in 2019 against 19.7% two years ago and 19.3% on his career.

Perhaps most promisingly, Chapman has demonstrated a willingness to use that slider in most instances with the count even or behind, saving his fastball only for the first strike of the sequence (in the chart below, courtesy of Baseball Savant, his fastball is in red, his slider in yellow, and his little-used sinker in orange). That sinker only appears with two strikes and fewer than two balls, when Chapman uses it to try to generate swings and misses.

All in all, although I wouldn’t personally want to be on the hook today for paying a generic 35-year-old reliever $18 million in 2022, I think this is the right move for the Yankees, whose owners are significantly richer than I. Chapman has convincingly demonstrated that he is anything but a generic reliever, and finalizing their bullpen this early in the offseason gives New York the cost certainty they need to pursue other, Gerrit Cole-shaped projects. What’s more — and this is where it gets icky — the Yankees have clearly already decided that they’re comfortable with Chapman’s history and past suspension under the league’s domestic violence policy (Hal Steinbrenner, their owner, was quoted in 2017, not long after Chapman signed his first deal with New York, as saying of the incident, “Sooner or later, we forget, right?“).

Any other team that signed Chapman — save perhaps the Cubs — would no doubt have deservedly tarnished their reputation for doing so. For the Yankees, that decision was made three years ago, though that stretch hasn’t dimmed our memories quite like Steinbrenner thought, or perhaps hoped, it would.

With Chapman’s new contract will likely come ripple effects downstream in the relief market. Will Harris, Will Smith, Daniel Hudson, and Dellin Betances (not to mention Drew Pomeranz, Chris Martin, and Jake Diekman) are all available this offseason, and probably happy to see Chapman return to a team already rife with relief arms. There aren’t quite as many sure bets on the market this offseason as there were, perhaps, a year ago, when Kimbrel, Britton, Cody Allen, Jeurys Familia, Kelvin Herrera, Andrew Miller, Joakim Soria, David Robertson, and Ottavino were all available. But there are still enough that the teams most in the market will find plenty to consider this winter.


Job Posting: Cleveland Indians Area Scout

Position: Area Scout

Primary Purpose
Provide high-quality information on amateur players to prepare the organization for acquisition opportunities

Essential Responsibilities and Duties

  • Relationships: Create and maintain strong relationships with players and their families, along with coaches and programs, to understand the player’s background and character.
  • Evaluations: Provide player evaluations and rankings by using organization’s scouting principles
  • Scheduling: Through preparation and prioritization, maximize opportunities for information collection
  • Data Collection: Lead a thorough data collection effort on the player pool

How will they get it done?

  • Info: Capture and document info quickly on players
  • Communication: Consistently communicate with internal stakeholders to lead and execute the scouting process
  • Teamwork: Commit to doing what’s best for the organization and acquiring the best players for the org

Leadership, Management, Development Responsibilities

  • Management: Manage and lead a scouting process within the area on amateur players within a network around them
  • Leadership: The organization will provide tools, resources and exposure for growth as an emerging leader
  • Development Responsibilities: The organization offers resources dedicated to personal development through leaders, research and processes.

Goals/Objectives for the Position

  • Player Pool: Cultivate a robust and well-rounded understanding of the player pool by using all available information and dynamically updating evaluations
  • Org Philosophies: Learn and understand organizational philosophies to accurately assess what’s happening and why/how
  • Feedback: Seek out feedback and use available resources to fuel development and increase understanding of players

Background
A demonstrated track record of curiosity and continuous improvement in the game, regardless of experience

Skills

  • Baseball Acumen: An understanding of the evaluation process. A technical proficiency in player assessment
  • Emotional Intelligence: Ability to manage emotions and time
  • Communication: Clearly and concisely explain thoughts verbally and in writing
  • Work Ethic: A relentless drive to collect more and better information
  • Passion: Demonstrate a clear passion for the game, teammates, the organization and learning
  • Resourcefulness: Utilize organizational resources to develop and understand organizational philosophies
  • Self-awareness: Understand your skill set, understand your biases, recognize your areas of development
  • Strategic Thinking: Employ a problem-solving mindset and strategic thinking

To Apply:
To apply, please complete the application, which can be found here.

The content in this posting was created and provided solely by the Cleveland Indians.


Job Posting: Texas Rangers Baseball Analytics Apprentice

Job Title: Apprentice, Baseball Analytics

Location: Arlington, TX

Basic Duties and Responsibilities:

  • Query and report on data
  • Build and maintain analytical tools, metrics, & models
  • Create compelling data visualizations and stories
  • Research game changing ideas and concepts
  • Present information to organizational stakeholders and executives

Qualifications:

  • Bachelor’s Degree in mathematics, engineering, computer science, data science, or related field
  • Strong written & verbal communication as well as visualization skills
  • Strong knowledge of baseball and associated data & technologies
  • Proficiency in SQL, R, Python, Tableau, SSRS, Microsoft BI, STAN, and/or other analytical platforms and languages
  • Familiarity with concepts such as predictive learning, cloud computing, machine learning, artificial intelligence, & Bayesian analysis
  • A creative mindset, open-mindedness, and desire to work in a learning culture

To Apply:
If interested, please complete the application, which can be found here.

The content in this posting was created and provided solely by the Texas Rangers.


Sunday Notes: Cutter Heavy, Josh Osich Doesn’t Bury His Head in the Sand

Josh Osich doesn’t bury his head in the sand when a change is in order. Compared to most hurlers, the 31-year-old southpaw has been chameleon-like in terms of his pitch usage. He’s switched teams, as well. Originally in the Giants organization, Osich spent 2019 with the White Sox, and just this past week he was claimed off waivers by the Red Sox.

Intrigued by what I saw in his pitch-type column, I asked the former Oregon State Beaver for the reasons behind all the ebbs and flows of his offerings.

“If the scouting report is the same every year, they know what you’re going to be throwing,” Osich said this summer. “It’s always nice to change things up, so that they don’t know what’s coming. In 2016, I was sinker-heavy. The year before that, I was fastball-changeup-cutter; it was more of a mix. In 2018, there were probably a few more changeups. This year I’ve been cutter-heavy.”

Very cutter-heavy. Roughly two out of every three pitches Osich threw in 2019 were classified as cutters. Might that not be contradictory to his “they don’t know what’s coming” comment? Read the rest of this entry »


Why Gerrit Cole Never Came Into Game 7 of the World Series

Yesterday, I wrote about the decisions A.J. Hinch and the Astros made in Game 7 of the World Series. Zack Greinke started the inning, gave up a one-out homer to Anthony Rendon that cut the Astros’ lead to 2-1, and then walked Juan Soto. At that point, Hinch opted to take Greinke out and bring in Will Harris; Howie Kendrick proceeded to hit a two-run homer to give the Nationals a lead they would never relinquish. In my piece, I argued that Hinch should have left Greinke in to finish the seventh, but before I got there, I discussed whether Greinke should have started the inning to begin with, and the team’s bizarre handling of Gerrit Cole as a potential reliever:

That leaves Gerrit Cole. It’s not clear why Cole was only going to be available for the ninth inning if Houston got the lead. He was warming earlier in the game. He was pitching on two days rest, so it’s possible he was only going to be available for an inning, and it seems reasonable to want to put him in at the start of an inning so he can be better prepared for it, but having him only available in the ninth to close out a World Series win is an odd choice and makes one wonder if the decision wasn’t entirely baseball-related. In any event, if Cole could have only gone one inning and needed to start it, then sticking with Greinke to start the seventh was completely reasonable.

We now have some answers, though they cause more questions.

Read the rest of this entry »


The 2019 Astros Join a List of Great Failures

The list of baseball’s winningest teams is one that any franchise would want to be on, but if we take that list and remove the World Series champions, it becomes something of a bummer. Everyone remembers the 2001 Mariners more for what they didn’t do than what they did. It’s not clear how history will remember the 2019 Astros. It seems likely this club will simply get tossed in with the 2017 team that did win it all, taking some of the sting away from not being able to claim a second championship this season. Though perhaps difficult for Houston and its fans right now, we should remember just how great this team was. There’s a reason the Astros’ World Series odds were so high for so long, and it’s because they put together a roster that, over the course of the regular season and much of the postseason, was a lot better than everyone else.

The table below feels almost obligatory, but here’s a list of the teams to win least 105 games, with how their seasons finished:

Teams with the Most Wins in a Season
Season Team W Result
2001 Mariners 116 Lost ALCS
1906 Cubs 115 Lost World Series
1998 Yankees 114 Won World Series
1954 Indians 111 Lost World Series
1927 Yankees 110 Won World Series
1909 Pirates 110 Won World Series
1969 Orioles 109 Lost World Series
1961 Yankees 109 Won World Series
1970 Orioles 108 Won World Series
1975 Reds 108 Won World Series
1986 Mets 108 Won World Series
2018 Red Sox 108 Won World Series
2019 Astros 107 Lost World Series
1932 Yankees 107 Won World Series
1931 Athletics 107 Lost World Series
1907 Cubs 107 Won World Series
1939 Yankees 106 Won World Series
1998 Braves 106 Lost NLCS
1904 Giants 106 No World Series
2019 Dodgers 106 Lost NLDS
1942 Cardinals 106 Won World Series
1905 Giants 105 Won World Series
1944 Cardinals 105 Won World Series
1943 Cardinals 105 Lost World Series
1953 Dodgers 105 Lost World Series
1912 Red Sox 105 Won World Series
2004 Cardinals 105 Lost World Series

Read the rest of this entry »


Toward a Unified Theory of Baby Shark

Gerardo Parra reached base only one time in the World Series, a walk against Josh James in Game 4. It wasn’t a key moment in the series — the Nationals were down 4-0, and while Parra scored, the Nats lost 8-1. When he reached first base, he was downright businesslike:

But businesslike isn’t normally a good description of Parra’s time on the Nationals. He’s widely regarded as a great clubhouse guy, ambushing Stephen Strasburg with hugs and keeping things light over the long grind of a season. He also, you may have heard, uses “Baby Shark” as his walkup music, a song that Nationals fans and players alike have rallied around.

If you’re curious, here’s a handy guide of the hand signals the Nationals make after hits:

Read the rest of this entry »


Chaim Bloom Aims for Collaboration and Sustainable Competitiveness in Boston

In an interview that ran here last week, Red Sox Senior Vice President/Assistant General Manager Zack Scott suggested that Dave Dombrowski’s successor will be heavily invested in analytics. That turned out to be an understatement. On Monday, Chaim Bloom — an integral cog in Tampa Bay’s cutting-edge front office since 2005 — was formally introduced as Boston’s Chief Baseball Officer.

If you paid heed to the press conference, you’re aware that “collaborative” was the buzzword of the day. Bloom, principal owner John Henry, chairman Tom Werner, and president/CEO Sam Kennedy used the term (and variants thereof) as frequently and purposefully as “Trick or Treat” is heard on Halloween.

Dombrowski didn’t depart Fenway Park in a gorilla costume, as Theo Epstein famously did in 2005, but the reason he’s being replaced isn’t cloaked in mystery. However much the ownership group cares to dance around it, Dombrowski didn’t fully embrace the collaborative process that was deemed necessary to move the team forward, certainly not to the extent they expect Bloom to do so.

Couching his comments with, “I wouldn’t contrast the two,” Henry said from the dais that ownership was “extremely desirous of bringing in someone who would augment and add, as opposed to bringing in someone who might have been an autocrat.” Read the rest of this entry »


Job Posting: Cincinnati Reds Baseball Analytics Roles

Please note, this posting contains multiple positions, all of which report to the Manager of Baseball Analytics.

Job Title: DevOps Engineer

Job Purpose:
Work with Baseball Analytics group to manage departmental infrastructure, build out analytic workflows, and support optimal development processes within the group. The Reds envision the person in this position to play a major role in the creating and maintaining stable production environments, allowing stakeholders to easily access information.

Essential Duties and Responsibilities:

  • Implement and maintain software build and release processes including continuous integration of software modules.
  • Develop and maintain production data analysis jobs in tandem with data scientists and baseball analysts.
  • Select, deploy, and maintain software services to best support external consumers of analytical information, as well as the efficient development of new analytics.
  • Develop, document and communicate processes to team members.
  • Assist with the development and maintenance of automated tests and monitoring services to ensure continued reliability of our analytical products.
  • Collaborate with Baseball Systems and IT departments to integrate processes and ensure organizational alignment.

Knowledge, Skills, and Abilities:

Because the Reds expect any candidate for this position to possess the capacity to discover and learn new technologies quickly, their emphasis for evaluating candidates will be on their demonstrated experience and talent in developing reliable technical solutions rather than their knowledge of any specific programming languages or tools. However, the Reds anticipate that familiarity with the following items could be beneficial in this role:

  • Python, or similar programming languages, including for web development (Flask) and/or data analysis (Pandas)
  • Linux/Unix
  • Docker and related technologies for virtualization
  • R (the statistical computing environment)
  • Relational databases (SQL)
  • Spark and Hadoop, and/or other technologies for processing high volume data sets (HPC, stream processing, NoSQL, etc.)
  • Azure DevOps or similar tools (Jenkins, TeamCity, etc.) for automation and continuous integration
  • Azure cloud computing services or similar environments (AWS)
  • Kubernetes
  • Web services, microservices, REST APIs, serverless, and related software architecture concepts

Work Environment:

  • Remote working accommodations are available.
  • Work is normally performed in a typical interior/office work environment.
  • Hours may periodically include nights, weekends and holidays.

Expectations:

  • Adhere to Cincinnati Reds Organization Policies and Procedures.
  • Act as a role model within and outside the Cincinnati Reds Organization.
  • Performs duties as workload necessitates.
  • Demonstrate flexible and efficient time management and ability to prioritize workload.
  • Meet Department productivity standards.

To Apply:
To apply, please complete the application, which can be found here.

Job Title: Baseball Research Analyst

Job Purpose:
Work with the Baseball Analytics, Baseball Operations, Scouting and Player Development staffs to develop and support analysis and research requests. The Reds envision the person in this position to play a major role in the creation of new baseball analytics/development concepts, supporting player evaluation, development and acquisitions and on-field strategies.

Essential Duties and Responsibilities:

  • Design, develop, test, implement and maintain method and models, utilizing appropriate tools and techniques.
  • Assist staff with ad-hoc research projects and data requests.
  • Create tools to improve the flow of information and insights.
  • Work with the Reds’ Baseball Analytics and Systems staff to integrate new statistical analyses, models and data visualizations into existing and new applications.
  • Collaborate with Major League Operations, Player Development, Sports Science and Scouting departments to plan, manage and integrate analyses.

Knowledge, Skills, and Abilities:

  • Bachelor’s degree or equivalent experience in a quantitative field, such as Statistics, Data Science, Mathematics, Engineering.
  • Understanding of statistical analysis and predictive and prescriptive modeling.
  • Experience with statistical software (e.g. R, Python) and database querying (SQL).
  • Strong ability to communicate effectively with all aspects of Baseball Operations, Scouting and Player Development.
  • Knowledge of current baseball research, traditional baseball statistics and strategy.
  • Understanding of the workings of baseball front office.

Work Environment:

  • Work is normally performed in a typical interior/office work environment.
  • Hours may periodically include nights, weekends and holidays.

Expectations:

  • Adhere to Cincinnati Reds Organization Policies and Procedures.
  • Act as a role model within and outside the Cincinnati Reds Organization.
  • Performs duties as workload necessitates.
  • Demonstrate flexible and efficient time management and ability to prioritize workload.
  • Meet Department productivity standards.

To Apply:
To apply, please complete the application, which can be found here.

Job Title: Data Scientist

Job Purpose:
Work with the Manager of Baseball Analytics to implement the department’s research and development efforts within new and existing applications. The Reds envision the person in this position to play a major role in the creation of new baseball analytics concepts with the ultimate goal of enhancing player evaluation and on-field performance.

Essential Duties and Responsibilities:

  • Design, develop, test, implement and maintain predictive models and metrics utilizing appropriate tools and techniques.
  • Work with the Reds’ Baseball Analytics and Systems staff to integrate new statistical analyses, models and data visualizations into existing and new applications.
  • Perform ad hoc analyses and effectively prepare and present findings.
  • Keep up to date on new predictive modeling techniques and evaluate their potential for application to baseball data sets.
  • Collaborate with Major League Operations, Player Development and Sports Science departments to design and implement statistical analyses.

Knowledge, Skills, and Abilities:

  • 3+ years of experience in computational field, such as Statistics, Biostatistics, Data Science, Mathematics, Engineering, Quantitative Social Sciences or Analytics.
  • Strong knowledge of statistical analysis and predictive modeling.
  • Demonstrated experience with statistical software (e.g. R, Python) and database querying (SQL).
  • Ability to communicate effectively with all aspects of Baseball Operations, Scouting and Player Development staffs.
  • Experience with Bayesian statistics. (Preferable, but not required)
  • Understanding of typical baseball data structures.
  • Knowledge of current baseball research, sabermetric concepts, traditional baseball statistics and strategy.

Work Environment:

  • Remote working accommodations are available.
  • Work is normally performed in a typical interior/office work environment.
  • Hours may periodically include nights, weekends and holidays.

Expectations:

  • Adhere to Cincinnati Reds Organization Policies and Procedures.
  • Act as a role model within and outside the Cincinnati Reds Organization.
  • Performs duties as workload necessitates.
  • Demonstrate flexible and efficient time management and ability to prioritize workload.
  • Meet Department productivity standards.

To Apply:
To apply, please complete the application, which can be found here.

The content in this posting was created and provided solely by the Cincinnati Reds.


A Defining Moment Slips Away From Zack Greinke

It is not an indictment of a pitcher to allow a home run to Anthony Rendon. He hit 34 of those this season, and 104 over the past four seasons combined. It is also no grand failure to walk Juan Soto. The precocious 21-year-old was issued 108 free passes this season, the third-most in the National League. He also hits for quite a bit of power, so sometimes, a pitcher is content watching Soto trot down to first if it doesn’t mean he just yanked a pitch into the seats. When Rendon homered and Soto walked in back-to-back plate appearances in the seventh inning of Game 7 of the World Series on Wednesday, it wasn’t, as Craig Edwards wrote earlier today, a sure sign that Houston starter Zack Greinke had run out of gas. But it was spooky enough to make Astros manager A.J. Hinch reach for his bullpen, bringing in Will Harris to face Howie Kendrick with a 2-1 lead.

By now, you know what happened next. Kendrick poked his bat head through the bottom of the zone and got enough of a Harris fastball to drill the foul pole in right field for a two-run homer. The shot gave the Nationals their first lead of the game, and they never looked back, adding three more runs the rest of the way while their bullpen stymied Houston’s destructive lineup en route to a 6-2 final and their first World Series championship in franchise history. Harris is a very good pitcher, and he made a good pitch — a cutter that was on track to perfectly dot the low and outside corner of the strike zone. But Kendrick came up with the only possible swing that could have done damage against it, and in doing so, delivered a fatal blow to the Astros’ historically great season. It also nullified a performance by Greinke that could have served as the defining moment of his career.

Greinke allowed two runs in six and two-thirds innings on Wednesday, despite allowing just four baserunners. For comparison’s sake, his counterpart, Max Scherzer, allowed the same number of runs in five innings while allowing 11 to take base. Before the two-out homer and walk in the sixth, Greinke had been spectacular. He faced the minimum 12 batters over the first four innings of the game, allowing just one hit — a single by Soto — that was wiped out on a double play. He issued his first walk with one out in the fifth inning against Kendrick, but bounced back from that with two quick outs to end the threat, before throwing another 1-2-3 frame in the next inning. After six scoreless, Greinke had thrown just 66 pitches. While Scherzer labored on the other side, having to gut through each inning after falling behind hitters repeatedly and setting up potentially disastrous situations with men on base, Greinke seemed to be on cruise control. Read the rest of this entry »