Is this type of take-home assignment becoming the norm?

I recently got contacted by a recruiter for a Founding Engineer role at an AI-for-real-estate company. They already have 4 engineers and 2 co-founders. Even before I got the chance to get an intro cha

I recently got contacted by a recruiter for a Founding Engineer role at an AI-for-real-estate company. They already have 4 engineers and 2 co-founders. Even before I got the chance to get an intro chat with anyone on the team, they sent me this take-home assignment: >Information about a real estate property is often scattered, inconsistent, or incomplete, making it hard for buyers to see the comprehensive picture before purchasing a home. We want a feature that turns this landscape into a clear, reliable brief so people can make confident property decisions. Your task is to design and implement this feature end-to-end. >What to Deliver: - A GitHub repo link with your code and frequent, clear commits. - A short design note (markdown in the repo in README.md) explaining your approach, trade-offs, and what you’d do with more time. >You are welcome to use any tools you’d normally rely on IDEs like Cursor or Windsurf, AI-assisted coding, web search, API docs, or hosted AI services. We encourage you to use whatever stack or workflow helps you demonstrate your design and implementation skills best. >We’re less concerned about which exact APIs or frameworks you choose and more interested in how you structure the problem, make design decisions, and communicate trade-offs. What really struck me is that this assignment was supposed to be done in only 2 hours (checked by the GitHub commit timestamps). The combination of the short amount of time, the open-ended aspect of the problem definition, and the lack of possibility to ask questions to the interviewer caught me off-guard to be honest. I ended up writing a structured document with my analysis of the problem and each pros and cons for different parts of it, but I left it at that. Since they asked for a public GitHub link (which I didn't provide because my current employer doesn't need to know I'm interviewing), I was later able to find two other candidate's public GitHub repos for the same interview question. They both did a serious attempt at building an end-to-end web app, but both of them used simplified mock data instead of real API connections, and one of them didn't really address the "scattered, inconsistent, or incomplete" part of the problem. But the fact that they both delivered a decent app in 2 hours makes me wonder how much I should practice my "vibe-coding" skills if this type of interview question becomes the norm? I'd love to hear what you think!