3 ms·

There is a very wide range of openings and talent out there. And of course you're aware that one uses different tools for different needs right? There's plenty

by edoceo 6y ago

There is a very wide range of openings and talent out there. And of course you're aware that one uses different tools for different needs right? There's plenty of room for those who aren't so ace like you to land that AWS gig in six hours.

scarface74 6y ago
Before the AWS gig, I was a bog standard “Enterprise Developer” or Architect depending on the month of the year doing yet another software as a service CRUD app bumping around in mostly small local companies that no one had ever heard of. When I was looking for a job in 2016 locally, I emailed a bunch of local external recruiters and was juggling eight or nine openings. I did six phone screens in one day from different companies. I was no special snowflake. Anyone who could call themselves a “full stack developer” with 5 years of experience could do the same thing. Heck, I didn’t know any of the $coolkids front end frameworks. The process was the same - one phone screen, a half day in person where you spoke about your past projects, maybe did a coding test that was barely above FizzBuzz level of complexity and show that you know SQL. A local full stack developer who had any kind of experience could get the “right now” job within a month if they weren’t being picky. Of course post-Covid, things are different. So either way. If you are looking for framework developers (no insult intended - that’s what I was as a developer until recently) the process is easy if you’re any good. If you are looking for “smart people” (tm). They are able to do the leetCode monkey dance. Who is left that is willing to spend hours doing take home tests? All of the best candidates know how to play one game or the other.
- edoceo 6y ago
  > Who is left that is willing to spend hours doing take home tests? I've used this process to help place entry level all the way to C-Level -- maybe I've not provided enough details (it's more than just a simple test) or maybe you're over-simplifying the process? It's not a perfect process (hiring in general is still looking for that) and clearly it's not the right process for you. I'm happy you found a job you enjoy.
  - scarface74 6y ago
    Two non developer anecdotes from what I’ve heard or seen Solutions Architect - answer the soft skill questions aka “tell me about a time when..” and they had to do a writing sample either a sales blog post or an SOW. Project Manager - same soft skill questions, talk about processes, previous challenges and outcomes. Maybe do a simplified project plan. Are those the types of take home tasks you are referring to for non developer roles? Just curious.
    - edoceo 6y ago
      It's not an unguided take home. It's an interactive gig, imagine a process to demonstrate your skill. eg: when hiring a PM, we'd have them demonstrate, same with Architect - my whole process is about SHOW rather than tell.
    - blaser-waffle 6y ago
      I've done sales engineering and solutions architecture for years and never once written a sales blog post. I'm not sure how I'd respond to that if I was asked to do it. SOW also seems tricky... I'm usually putting out 27+ SOWs, and there is a lot of "standard language" cut-n-paste.

by edoceo 6y ago

scarface74 6y ago

Before the AWS gig, I was a bog standard “Enterprise Developer” or Architect depending on the month of the year doing yet another software as a service CRUD app bumping around in mostly small local companies that no one had ever heard of. When I was looking for a job in 2016 locally, I emailed a bunch of local external recruiters and was juggling eight or nine openings. I did six phone screens in one day from different companies. I was no special snowflake. Anyone who could call themselves a “full stack developer” with 5 years of experience could do the same thing. Heck, I didn’t know any of the $coolkids front end frameworks. The process was the same - one phone screen, a half day in person where you spoke about your past projects, maybe did a coding test that was barely above FizzBuzz level of complexity and show that you know SQL. A local full stack developer who had any kind of experience could get the “right now” job within a month if they weren’t being picky. Of course post-Covid, things are different. So either way. If you are looking for framework developers (no insult intended - that’s what I was as a developer until recently) the process is easy if you’re any good. If you are looking for “smart people” (tm). They are able to do the leetCode monkey dance. Who is left that is willing to spend hours doing take home tests? All of the best candidates know how to play one game or the other.

edoceo 6y ago
> Who is left that is willing to spend hours doing take home tests? I've used this process to help place entry level all the way to C-Level -- maybe I've not provided enough details (it's more than just a simple test) or maybe you're over-simplifying the process? It's not a perfect process (hiring in general is still looking for that) and clearly it's not the right process for you. I'm happy you found a job you enjoy.
- scarface74 6y ago
  Two non developer anecdotes from what I’ve heard or seen Solutions Architect - answer the soft skill questions aka “tell me about a time when..” and they had to do a writing sample either a sales blog post or an SOW. Project Manager - same soft skill questions, talk about processes, previous challenges and outcomes. Maybe do a simplified project plan. Are those the types of take home tasks you are referring to for non developer roles? Just curious.
  - edoceo 6y ago
    It's not an unguided take home. It's an interactive gig, imagine a process to demonstrate your skill. eg: when hiring a PM, we'd have them demonstrate, same with Architect - my whole process is about SHOW rather than tell.
  - blaser-waffle 6y ago
    I've done sales engineering and solutions architecture for years and never once written a sales blog post. I'm not sure how I'd respond to that if I was asked to do it. SOW also seems tricky... I'm usually putting out 27+ SOWs, and there is a lot of "standard language" cut-n-paste.