In my experience: the FE engineering fields (web FE, Android, iOS) are probably (very slightly) less in demand than most others. I think that's primarily because: the technology has calcified (in a good way), and there's tons of bootcamps that churn out pretty high quality associate-level engineers which specialize in the FE world.
These bootcamps will also advertise as having covered backend stuff, but its very rarely in any level of depth beyond "spun up an express NodeJS app as a razor-thin layer in front of Firebase" or something; thirty minutes of interviewing will expose this gap, and they get hired on as a FE.
BE/DevOps is in higher demand, thus harder to find. DevOps is a weird one, because its a field that's extremely striated between platforms. Whereas a Java BE engineer could ramp up on NodeJS or whatever very quickly, an Azure specialist will take longer to match their skillset to AWS, not to mention the large body of individuals coming in with traditional linux server maintenance experience that will have a hard time matching their skillset to cloud-native serverless-like roles. It shouldn't stop a hire, but it does make finding well-matched qualified candidates more difficult.
Actually, I'll give props to a lot of the modern Azure skills DevOps peeps can develop; they're very big on their state-of-art being open source CNCF stuff; ex, Kubernetes, DAPR, KEDA, etc. So, a skillset there can transfer to a ton of places (including a GCP-esque shop, or even an AWS shop on less managed tooling). Glad to see some modernization/standardization in this space, but AWS is very antiquated and stuck in their ways.
Less from a hiring manager angle and more from an engineer angle: bonafide actual full stack devs are insanely valuable. Every once in a while you get a candidate that can apply to any role, but will apply to a specialized role; then they meet the engineering manager and the manager realizes, they're a candidate among a pool of candidates who are specialized enough for the role, but they also bring that full stack experience. Very few teams/roles are actually "100% backend" or "100% whatever"; the team may settle for someone who meets the job description, but will prefer breadth over depth, in nearly all cases.
Rarest quality: seniority. Not skill based. Just time, and more-so a demonstrable breadth of experience on a handful of projects, tech stacks, etc. Can't fake it. Can't stress how many roles we've posted at a Senior level, then settled for someone more mid-level because there's no-one. We're remote; competitive salary; small team; cool tech; cool product; maybe one in fifty candidates feels demonstrably senior.