The Unrealistic Expectation of 'Making Projects' in Job Applications

The Unrealistic Expectation of ‘Making Projects’ in Job Applications

Have you ever felt like job applications are asking for the impossible? I’m talking about those ‘make a project’ requirements that seem to be the norm these days. It’s like, ‘Hey, can you create an entire application with a frontend, backend API, and database, all by yourself? Oh, and deploy it too, so we can see it in action.’

I mean, isn’t that what a whole development team is for? It’s not like I’m asking for a simple task, like building a to-do list or something. No, we’re talking about a full-fledged application that requires expertise in multiple areas.

And then, to make matters worse, they expect you to do it multiple times. Like, ‘Hey, that was great, now can you do it again, and again, and again?’ It’s exhausting just thinking about it.

I’m not saying it’s impossible, but it does seem like a ridiculous barrier to entry. I mean, what’s the point of having a development team if one person can do it all? It’s not like we’re talking about a startup with limited resources here.

Maybe I’m just being cynical, but it feels like these ‘make a project’ requirements are just a way to weed out applicants who aren’t willing to jump through hoops. Because, let’s be real, it’s not about showcasing your skills or creativity; it’s about proving your dedication to the company.

So, what do you think? Are ‘make a project’ requirements necessary, or are they just a way to make job applications more tedious?

Leave a Comment

Your email address will not be published. Required fields are marked *