Midseason Firing In Play For Doug Pederson?

It was made pretty clear coming into Week 11 that Doug Pederson‘s job security was hinging heavily on his team’s performance against the Lions. A report last week indicated that, while a loss was expected, a blowout loss would put a midseason firing on the table in Duval.

Unfortunately for Pederson, today’s loss was not only a blowout, but it was also one of the team’s most lopsided losses in franchise history. Losing 52-6, the Jaguars 46-point deficit at the end of the game was their worst since 1995, when Jacksonville lost to the Lions for the first time 44-0 in their inaugural season. The Jaguars were also outgained by the Lions today by 475 yards, the biggest yardage differential in a game since 1979.

These results don’t bode well for a head coach that is, at the very least, trying to make it to the end of the season. Six of Jacksonville’s nine losses this year have come in one-score games, something which could help Pederson’s chances of surviving until the end of the year. Today’s blowout, though, changes that perspective a bit.

Per Tom Pelissero of NFL Network, when asked after today’s loss whether this may have been his last game as head coach, Pederson told the media, “I can’t control that. Listen, I’ve been around this league a long time. If it’s going to happen, it’s going to happen, obviously. But at the same time, I have a job to do.”

Peliserro also reported that Pederson “won’t rule out making staff changes over” the team’s bye upcoming bye week. An obvious candidate to replace him on an interim basis does not necessarily exist on staff, which further strengthens his case for the rest of 2024. Removing coordinators or assistant coaches from the picture may further reduce the options to replace him in the short term.

Regardless, with his job on the line, Pederson’s team put up its worst game perhaps in franchise history. It’s starting to feel like a foregone conclusion that he will lose his job, but today’s performance may bring about that change sooner rather than later.

View Comments (12)