
...

By Ernesto Cova
0
Share
Newsweek is a Trust Project member
See more of our trusted coverage when you search.Prefer Newsweek on Googleto see more of our trusted coverage when you search.
Even though the New York Jets still have a big need for a quarterback, it looks like they will roll with Geno Smith for a year and go after their guy in 2027.
Barring a major surprise, QB Fernando Mendoza will be gone at No. 1, leaving the New York Jets with a chance to bolster their defense.
For most of the pre-draft process, Aaron Glenn's team was projected to land Ohio State star LB Arvell Reese. That's why it was a major shocker to see ESPN NFL Draft expert Mel Kiper predict they will go with David Bailey instead:
Read More on NFL
"...The Jets really need an instant impact edge rusher. They were 31st in sacks last season (26) and traded Jermaine Johnson, further thinning out the unit. They have to find foundational players off the edge. And Bailey is explosive and productive, posting 14.5 sacks (tied for first in the FBS), 71 pressures (second) and a 20.2% pressure rate (first) last season," Kiper wrote.

...
While Bailey is clearly an elite prospect as a pass rusher, Reese's impressive performance at the NFL Scouting Combine seemed to cement him as the clear-cut No. 2 pick, especially given his versatility and ability to line up at multiple positions.
That said, they can't go wrong with Bailey, either. The Texas Tech star is a privileged athlete who can turn the corner in the blink of an eye with his quick twitch and agility. He has a great nose for getting to the quarterback, and he has a solid repertoire of pass-rushing moves.
On the downside, there are some concerns about his ability to withstand the physicality of the pros, given that he's listed at 6-foot-4 and just 251 pounds, which is slightly small for an edge rusher.
The Jets could probably just trade down and still get him if they're hell-bent on landing him, and Reese falling past No. 2 would most definitely make other teams reconsider their draft plans.
View 0 Comments
Submit Correction
View Editorial & AI Guidelines