There's typical ones where an engineer will stack their resume with buzzwords that they don't understand at a basic level. An example of this is putting Kubernetes on ones resume but not being able to explain the different workloads. People don't often call this fraud, but I do when it crosses some magical threshold. The reason I call it fraud is that fraud, to me, generally implies intent to deceive. About a year ago I discovered on Reddit there were people coaching others through lying on their resumes and in interviews with the reasoning that "everyone does it" and "you'll learn on the job".
The second kind I've encountered is more analogous to what you experienced, though we never hired any of these folks. Retrospectively I think one of the things that helped us avoid hiring these folks is that we don't refer to an engineers provenance. Early on I took the stance that just because you say you're from Google, or any other large engineering firm, doesn't mean you're the right fit for the team. We had candidates invest in a 2-3 hour take home exercise that was pretty easy, it mostly tested your API design skills but because it involved code we got some good peeks into what that would look like in a contrived scenario. Second, we ask that candidates bring an example of projects they've worked on, starting with ones they led. This one is a little harder to fake the funk on, especially if the candidate is Senior+.