School software development project in a nutshell:

You will need to gather the requirements from us by ways of an interview, built the documentation for it, we'll sign it and that's what you have to build.
...
We were supposed to get that signature 3 weeks ago, but they decided to not sign yet because they want to make late changes to the project whenever they want, yet we have to finish the build of this in 7 weeks... Seriously? That's what we have to work with.

Any working devs that recognize this situation at work and not at school?

Prepping you for the real world buddy :)

Yep, just a normal project tbh. At least send an email stating that their deadline date will pass due to their buffering about. :\

My design team rushes through mocks repeatedly, and I consistently only have partial mocks to work with. Requirements documentation sometimes consists of only a blurb of a marketing use case. When I do have actual requirements, they are never feature complete, ignore edgecases entirely, and conflict with the mocks (of course).

Honestly I miss the requirements gathering of my senior comp sci project. When you have only 2-3 teachers evaluating requirements, then it is easy to agree on stuff. Having multiple C-level people argue around you and give conflicting requests is confusing and stressful.