4 ms·

45 minutes - write a simple API matching the spec in one of the 3 languages on your/our laptop. Use Google if you have to. Someone will be in the room to help a

by sg47 6y ago

45 minutes - write a simple API matching the spec in one of the 3 languages on your/our laptop. Use Google if you have to. Someone will be in the room to help answer questions. API should be functional. Returning fake data is fine (or provide data in a sqlite db) 45 minutes - do code review of this extremely buggy code like you'd review a coworker's code 45 minutes - presentation on a technical topic to one or more team members 45 minutes - behavioral. Let's talk about failures, conflicts in your career. Who are your role models? What do they do well? Leadership abilities, career progression 45 minutes - troubleshooting. Here's a docker container. Make the service inside it work

Supermancho 6y ago
That's 4+ hours if you count initial setup, meet, breaks, etc.
- richardknop 6y ago
  A lot more since you have to prepare for the interview / interviews. So there's several hours to prepare at least.
  - sg47 6y ago
    Which part. Except the presentation, there's no prep required. It's all about what you know and what you have done in your career. No Leetcode, no algorithms, no bs questions.
    - richardknop 6y ago
      Presentation sounds really vague to me, it could mean anything from 1-2 hours of prep or a day or two of intense preparation to make a good presentation. Also number 1 (writing simple API matching a spec) - this doesn't require prep if it's using language that I am using currently / have been using in my daily job for a long time. But I have found often been required to write code in languages that are on my CV but I haven't used them in 5+ years. Also talking about past failures, career history. I can barely remember in detail 2-3 years so I would need to spend a little time to just be prepared about a random very specific question about a project I worked on 5 years ago that might come up during interview because it would silly if I didn't remember (which I wouldn't if you ask me randomly about something I did 5 years ago). Small things like these add up, obviously the more you want to get a certain job the more time you would spend preparing, it's only natural. If you are only looking around you might just wing it since you don't care much. I am not criticising your system, it seems pretty sensible actually btw.
- edmundsauto 6y ago
  That seems like a minimum amount of time to know if you want to hire someone, IMO.
- finolex1 6y ago
  That doesn't seem too different from the 4-7 hour-long interviews tech companies have candidates doing nowadays.
angrais 6y ago
Where do you work? This process sounds solid and based on that I imagine your team setup is great to be part of. Am interested to learn more. Are there open positions?
- sg47 6y ago
  I'm in the process of changing jobs and will be hiring/rolling this out in my new role. Will reach out once that happens.
snypox 6y ago
Man, you’d be surprised what rate of engineers I interviewed for a .NET job ever seen a Docker image. I think maybe a few out of 30. Most of them still coming from the classic Windows/.Net framework/IIS eco-system.

by sg47 6y ago

Supermancho 6y ago

That's 4+ hours if you count initial setup, meet, breaks, etc.

richardknop 6y ago
A lot more since you have to prepare for the interview / interviews. So there's several hours to prepare at least.
- sg47 6y ago
  Which part. Except the presentation, there's no prep required. It's all about what you know and what you have done in your career. No Leetcode, no algorithms, no bs questions.
  - richardknop 6y ago
    Presentation sounds really vague to me, it could mean anything from 1-2 hours of prep or a day or two of intense preparation to make a good presentation. Also number 1 (writing simple API matching a spec) - this doesn't require prep if it's using language that I am using currently / have been using in my daily job for a long time. But I have found often been required to write code in languages that are on my CV but I haven't used them in 5+ years. Also talking about past failures, career history. I can barely remember in detail 2-3 years so I would need to spend a little time to just be prepared about a random very specific question about a project I worked on 5 years ago that might come up during interview because it would silly if I didn't remember (which I wouldn't if you ask me randomly about something I did 5 years ago). Small things like these add up, obviously the more you want to get a certain job the more time you would spend preparing, it's only natural. If you are only looking around you might just wing it since you don't care much. I am not criticising your system, it seems pretty sensible actually btw.
edmundsauto 6y ago
That seems like a minimum amount of time to know if you want to hire someone, IMO.
finolex1 6y ago
That doesn't seem too different from the 4-7 hour-long interviews tech companies have candidates doing nowadays.

angrais 6y ago

Where do you work? This process sounds solid and based on that I imagine your team setup is great to be part of. Am interested to learn more. Are there open positions?

sg47 6y ago
I'm in the process of changing jobs and will be hiring/rolling this out in my new role. Will reach out once that happens.

snypox 6y ago

Man, you’d be surprised what rate of engineers I interviewed for a .NET job ever seen a Docker image. I think maybe a few out of 30. Most of them still coming from the classic Windows/.Net framework/IIS eco-system.