Ask Lemmy
A Fediverse community for open-ended, thought provoking questions
Please don't post about US Politics. If you need to do this, try [email protected]
Rules: (interactive)
1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, and toxicity are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either [email protected] or [email protected].
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email [email protected]. For other questions check our partnered communities list, or use the search function.
Reminder: The terms of service apply here too.
Partnered Communities:
Logo design credit goes to: tubbadu
view the rest of the comments
I had an interview where they asked me to set up 3 micro services (with full functionality), a Kafka broker, a frontend and to configure everything to run on Kubernetes.
According to them this would take "more or less 4 hours" and those hours would obviously not be paid.
I'm still not sure whether they were just trying to get free work out of people or if their expectations for what a software engineer is supposed to do in half a day are completely absurd.
I had a similar task to
"Set up a web service, load balancer and infrastructure to scale it to handle a large amount of requests. Harden the security of it to the best of your ability. Document how it works, how to scale it, why you built it the way you did, what measures you took to harden it and why, and any future improvements you would suggest. All code and documentation should be production quality. This should take about four hours."
Maybe you can write this code in four hours, but all this documentation and motivation as well? Fuck off.
They also asked for a made up report from a security audit (this was for a security engineer position) containing a dozen realistic vulnerabilities with descriptions, impact assessments, and remediation suggestions. Once again of production quality. This is at least six pages of highly technical, well researched, and carefully worded text. Four hours is tight for this task alone.
And if those are their expectations going forward they can keep their position. Imagine doing twice that much every day.