4 ms·

This is one of those things that you'd be amazed once you start looking at interviewer's ability to judge effort. Often times the questions asked or expected of

by monksy 4y ago

This is one of those things that you'd be amazed once you start looking at interviewer's ability to judge effort. Often times the questions asked or expected of is just excessive. They'll ask problems that if you didn't know the trick or (years of ) research behind it, you'd never solve it. They'll give a take home asking for a full service and full deployment on K8s and claim "it should only take 6 hours".

ozim 4y ago
I fail to see the problem. If companies look for people who have years of experience in k8s or for people who don’t trip on something specific it is fair game. If they look for full stack dev and then grill on some obscure details of one tech stack piece it is also their problem.
- yuliyp 4y ago
  Someone can have lots of k8s experience but not have needed to set things up end-to-end. Most people generally are familiar with "X as used at my job" which is very different from "X as what happens when I use it from scratch". This is true not just for orchestration systems like k8s, but also programming languages: people are used to the libraries they have for solving common problems, which are not necessarily OSS / standard libraries.
  - ozim 4y ago
    We discuss "experience with" which for me is really vague. Is company looking for experience like "someone who could connect to k8s and debug application"? Is company looking for "someone who can setup k8s and have networking up and running"? How do deal with people claiming "experience with" where someone set something up for them and they were using stuff but never had to dig into details. In the end it is also like driving - while driving is driving then "F1 driving" is so much more and while F1 driver is not an engineer you still expect him to understand how ICE engine works and bunch of other technical details. For everyday driver you expect no more than "put in fuel, turn the key, throttle and you drive, break you stop".
- monksy 4y ago
  Context of this is: Senior engineer expectation: Build an app that returns results for x problem. Deploy it [there are a lot of requirements there to make that at least a week long] Staff: Create and deploy the app with a CI/CD+deployment platform. (K8s)

by monksy 4y ago

ozim 4y ago

I fail to see the problem. If companies look for people who have years of experience in k8s or for people who don’t trip on something specific it is fair game. If they look for full stack dev and then grill on some obscure details of one tech stack piece it is also their problem.

yuliyp 4y ago
Someone can have lots of k8s experience but not have needed to set things up end-to-end. Most people generally are familiar with "X as used at my job" which is very different from "X as what happens when I use it from scratch". This is true not just for orchestration systems like k8s, but also programming languages: people are used to the libraries they have for solving common problems, which are not necessarily OSS / standard libraries.
- ozim 4y ago
  We discuss "experience with" which for me is really vague. Is company looking for experience like "someone who could connect to k8s and debug application"? Is company looking for "someone who can setup k8s and have networking up and running"? How do deal with people claiming "experience with" where someone set something up for them and they were using stuff but never had to dig into details. In the end it is also like driving - while driving is driving then "F1 driving" is so much more and while F1 driver is not an engineer you still expect him to understand how ICE engine works and bunch of other technical details. For everyday driver you expect no more than "put in fuel, turn the key, throttle and you drive, break you stop".
monksy 4y ago
Context of this is: Senior engineer expectation: Build an app that returns results for x problem. Deploy it [there are a lot of requirements there to make that at least a week long] Staff: Create and deploy the app with a CI/CD+deployment platform. (K8s)