Ask HN: What does Agile mean in practice at your job? (non-Agile developer here)

I come from a mostly systems/simulators engineering background where things were done either using waterfall or ad-hoc practices. I've quit my job and moved for multiple reasons. What I see is that now virtually all job ads, at least web business related, require Agile. Despite of nobody really using these at my previous company, I'm aware of TDD, CI, CD, and git workflow. 1) I use git workflow (_master_ is deployable, _develop_ branch for CI, _feat/name_ and _fix/name_ for implementations). 2) And I've done a bit of TDD so I think I have an idea of development workflow: think about the system before typing, design a test, implement until test passes. 3) Back where I was there were no "iterations". Instead there were milestones and these were somewhere between 3-6 months. Requirements had some flexibility, but most it were set to stone. 4) Neither concepts of sprint. Wait. Actually there was a lot "sprinting" (weekends and all nighters) typically in the last weeks before the milestone deadline. Is Agile immune to this with the "don't change date only change requirements" approach? 5) There was no daily scrum - whatever that means. I talked daily with the team when it was more convenient. And with the PM once a week or so. Daily as the milestone approached. 6) Pair programming whatever that is, was someone (most of the times me) sitting next to another developer when he was stuck and solve things. The thing is I'll likely have to "fake it until you make it" in my CV about using Agile :( So am I missing any revelation here? Do I need to pick up a (snake oil?) book to fit in a new company?