@russellxu For an APPLICATION for a job, yes. 20 hours is far too much. After having a chance to speak with the hiring manager to make sure the job is for me - the right opportunity, reward, culture, team, etc - then sure, I'll put far more effort in.

If you were going to be my manager and I found out that you expect me to put in 20 hours of work just to even APPLY, then I think you've told me everything I need to know about what it's like to work for you.

You both seem to be forgetting that this is a two-way street.

I think you've touched on a lot of important points and there are useful takeaways here. Being a hiring manager for the last 10 years, I recognise a lot of this.

But suggesting that someone needs to spend "maybe 20 hours" on building a website for a job application is, honestly, ridiculous. There's a part of me that might even look upon such an application with suspicion.

If it was a perfect opportunity at a company that I really want to work for, and I met you, the hiring manager, in a bar and you promised me that you'd genuinely spend some time looking at it and guarantee to bring me in for an interview, then perhaps I would put the 20 hours worth of effort in, in order to have a decent opportunity.

But spending 20 hours on an application? When I can't even guarantee that someone will even look at my email, let alone the website? That's just nonsense.

I am not even looking for a job and this sounds exasperating and depressing, can't imagine if someone really needs the job and are looking. Maybe these things are only meant to be done for a specific job that you really, really want get and not for every single potential job because it is just impossible. It is called "job hunting" not "job luring".

I'd rather apply to 50 positions a day with the same resume and hope for the best than spend a couple of days conceptualizing, designing, developing a website for a specific role, only to find that applications are closed the moment the website build is complete, or even if I do send it through, not receive any reply at all.

And doing all of this stuff would not really guarantee the candidate a job anyway, but it would make sorting through the applications easier for the recruiter. So it is actually helping the recruiter more than the candidate. So it makes sense coming from you now because I assume you do more job applications reviewing than actually applying in the way you described.

I usually eat whatever Laravel releases but can’t get into this. The binding between controller namespace and frontend import doesn’t work for me. I don’t want to do a backend refactor and then have to figure out where I use that controller in the frontend.

Might not be an issue in reality but I think I’d regret using this.

Ziggy is great but it is not so great in that it exports all routes to the frontend. Would be nice if Ziggy could resolve the routes during the build process.

I know this is old, but I came here by Google search because I hit the same issue.

In my case, the problem was that the request validation of Laravel failed and - for a still unknown reason - returns 302 instead of 422 when called from Flutter.

When I tested the same request with the same (wrong) parameters and header configuration (application/json) in Postman, I received 422 as expected.

Hope this helps anybody who finds this.