2 ms·
> A) Make it simple. Have them write "login". Don't be specific, tell them the exercise meant to be vague. Given a task without well-defined requirements would
by busterarm 11y ago
> A) Make it simple. Have them write "login". Don't be specific, tell them the exercise meant to be vague.
Given a task without well-defined requirements would be a big red flag for me about the organizational structure of the company. I might even look for the door out of habit. I would definitely try to hammer out requirements verbally before writing any code and if there were resistance I would just thank you and leave. I'm interviewing you too, after all.
How you write 'login' depends entirely upon the context of what for. There's nothing 'simple' about it. Maybe it's an intranet site and you can authenticate via LDAP. Maybe you need to authenticate some legacy devices that only support specific character sets and field lengths. I guarantee that's not the answer you're expecting though. Your question doesn't give as much credit to breadth of experience as much as it does to "do you know how to roll your own secure auth?"/CRUD-fu. I'd rather hire somebody that knows (or thinks about) what pitfalls to look out for than how to implement something they can reference online.
That said, it's pretty much par for what I've encountered so far in this industry, but I'm interviewing looking for something _better_ not the same.
> Lastly: Talk to your HR department about terminating bad employees after 90 days.
Please don't wait 90 days to fire me if I'm a bad employee. You're basically guaranteeing that I don't get to work at other places I was far along the interview/offer process at when I was applying the last time. You're guaranteeing that I start my application pipeline from scratch and at disadvantage. If you feel buyer's remorse, make that decision immediately please. The best people always find a way to kick ass right away, even if it's in training.