What's your concern there? (Honest question!) I feel terrible about asking for home assignments but I feel like it's good for people like myself who are terrible about coding live. (I usually have a choice of live or homework.) I put a "limit" as a guideline about what kind of quality to expect, usually with language about things not to worry about. I don't expect/want folks to burn a bunch of time on things.
But a hard limit (you will get the assignment at X o'clock and you will have to turn it in within 3 hours) is just bonkers. It's totally unnecessary and artificial time pressure. Maybe I'm having a bad day and I make a silly mistake that takes time to fix - or the assignment is complicated and it takes me half an hour to even understand it and decide on an approach. Or I could implement the assignment in a maintainable way, but the time pressure requires me to do it in the most hacky way possible. Basically, I don't do my best work under time pressure, so I have no idea why you would impose it on me. In my professional experience, there's very rarely ever been any time pressure like that, so it's not like it measures something important.
That said, as I wrote elsewhere, if you can't pull a reasonable version of a work product out of a folder, I may be asking you to create one. I'm not necessarily talking code but I absolutely am looking for some proof that you can do the work if it's not already in the wild.
If not, why?
How would you feel if they insisted on you doing home assignments?
Maybe that's fine for you, but maybe not.
Both interviews (live and homework) have downsides, referrals don't work for all and hiring blindly isn't an option. I need some kind of signal, some way to choose one of hundreds. I have successfully used contract to hire before, and while that does lower the anxiety on the interview track, many can't consider that option. And that (again) unfairly advantages some.
I.. don't really know. Just over here trying my best. The market is broken in many ways.
Can you think? Are you curious? Those are hard to distill in an interview and harder still in formulaic interviews.
There is nothing wrong with wearing a suit, and it may be common in some workplaces/cultures, but in others it can be corollary to a work culture you are not compatible with.
When I last interviewed 15 years or so ago, I wore a jacket and tie (though not a suit) when I interviewed in person. I certainly didn't think it was necessary but I'd have been shocked if anyone had considered it to be a ding.
Came here to say this, specifically.
> - "Can you send us your high school diploma?"
Related: asks questions about that McDonald's job you had in high school, even though you have a master's degree and years of experience in the actual posted job requirements.
> - There are three architects on a single project.
Related: there are more than three layers of management between you and the Big Boss. Two is better. One is best. Too many layers means that it's probably going to take months to get approval for anything, meanwhile management is giving you the stink-eye for "not producing".
- The interviewer is wearing a suit.
- The interviewer asks "you've worked with [person who now works at our company] before, what do you think about them?". Bonus points if they insist after I give a diplomatic answer.
- "Why are you using microservices?" "Because everyone is doing it"
- Not following up. For weeks.
- "Can you send us your high school diploma?"
- Take home assignment with a time limit.
- No feedback on take home assignment except "we didn't like your approach".
- Developers use separate laptops for coding and for internet access.
- There are three architects on a single project.