4 ms·

"we’ve come up with a replacement for resume screens, and shown that it works well" No you haven't. You might have, but you'll have no way of knowing that unt

"we’ve come up with a replacement for resume screens, and shown that it works well" No you haven't. You might have, but you'll have no way of knowing that until they've been on the job at least 3 months. Personally, I think it's bullshit that I can show employers all the things I've built and they still expect me to write a reverse sort btree or whatever the fuck thing that has nothing to do with web development. College grads are perfect at passing these tests and they have no fucking idea what they are doing, but will get more offers and better pay every time. Experience counts and if you disregard it then I'm firmly in the "Fuck you, I don't want to work for you" camp. Unfortunately, I've resigned myself to memorizing the typical interview questions or going into management. I'd love to stay a dev, but being ruthlessly quizzed about shit that you never use in real life makes changing jobs a pain in the ass.

odonnellryan 11y ago
> Personally, I think it's bullshit that I can show employers all the things I've built and they still expect me to write a reverse sort btree or whatever the fuck thing that has nothing to do with web development. Aye. It's a hard problem: as an employer, you want to be pretty sure that you're getting someone on team that's going to bring you value. How do you do that? I guess ask them as much as you can. You definitely present a good problem, it is the same they're trying to solve over at triplebyte. > College grads are perfect at passing these tests and they have no fucking idea what they are doing, but will get more offers and better pay every time. Yeah, you have to study for interviews. It sucks, but almost every software company asks the same questions. Just prepare, I guess, and it'll pay off with that higher salary. > makes changing jobs a pain in the ass. You might have nailed it here. Employee retention is good for everyone! I think the solution is you need connections. When someone works at the company and they know you're a good dev they aren't going to ask you questions they ask other developers.
- hamitron 11y ago
  >> makes changing jobs a pain in the ass. >You might have nailed it here. Employee retention is good >for everyone! I'd say having a good work environment is good for employee retention, not arbitrary limitations to prevent people from switching jobs.
  - odonnellryan 11y ago
    Yeah, it's the XY problem. Sorta.
fredgrott 11y ago
I recently did an experiment where I took 50+ Android UI libraries opened them in a modern IDE and did code audits to find glaring errors ranging from Java to Android Best practices. Even exp will not help if you are TOO DAMN STUPID TO RESEARCH THE WARNING AND ERRORS the IDE points out to you AND RESOLVE THEM!
enraged_camel 11y ago
>>Personally, I think it's bullshit that I can show employers all the things I've built and they still expect me to write a reverse sort btree or whatever the fuck thing that has nothing to do with web development. As a business analyst interested in a software development career, this is what worries me the most about interviews. I write a fair amount of code. I have developed apps that work really well and solve important business problems. I can talk intelligently about everything I've developed, but if you asked me to write something on the spot I'm not sure how well I'd do. Most of the time I find the information I need through exhaustive searches on the Internet as well as lots of trial and error. Is it really a deal-breaker that I can't write a tree sort algorithm off the top of my head?
serge2k 11y ago
How do they know you built anything? Why should they expect that your experience will count for anything if you aren't willing learn a bit about data structures to pass that portion of your interview?
- Mc_Big_G 11y ago
  I have a large portfolio and I've never needed to write an algorithm to sort a binary tree (for example).
  - serge2k 11y ago
    How do they know you actually did the work on the sites/apps you present? Dead easy to take credit for someone else's work. I'm saying a desirable trait is that you can learn new things to solve problems. You know approximately what the problems they will give you are, if you aren't willing or able to go out and learn the necessary skills then why should they hire you?
    - Mc_Big_G 11y ago
      The large portfolio comes with a large list of references. I could also show them the code for every project. I've never been asked to produce either of those in an interview. No one has ever looked at my github account either. I never said I don't want to learn new things. Quite the contrary. I stay up to date on the latest web tech and have been frequently contracted for that exact expertise. However, I do find it frustratingly annoying that I need to learn a multitude of "interview puzzles" that I'll never use in real life.

odonnellryan 11y ago

> Personally, I think it's bullshit that I can show employers all the things I've built and they still expect me to write a reverse sort btree or whatever the fuck thing that has nothing to do with web development. Aye. It's a hard problem: as an employer, you want to be pretty sure that you're getting someone on team that's going to bring you value. How do you do that? I guess ask them as much as you can. You definitely present a good problem, it is the same they're trying to solve over at triplebyte. > College grads are perfect at passing these tests and they have no fucking idea what they are doing, but will get more offers and better pay every time. Yeah, you have to study for interviews. It sucks, but almost every software company asks the same questions. Just prepare, I guess, and it'll pay off with that higher salary. > makes changing jobs a pain in the ass. You might have nailed it here. Employee retention is good for everyone! I think the solution is you need connections. When someone works at the company and they know you're a good dev they aren't going to ask you questions they ask other developers.

hamitron 11y ago
>> makes changing jobs a pain in the ass. >You might have nailed it here. Employee retention is good >for everyone! I'd say having a good work environment is good for employee retention, not arbitrary limitations to prevent people from switching jobs.
- odonnellryan 11y ago
  Yeah, it's the XY problem. Sorta.

fredgrott 11y ago

I recently did an experiment where I took 50+ Android UI libraries opened them in a modern IDE and did code audits to find glaring errors ranging from Java to Android Best practices. Even exp will not help if you are TOO DAMN STUPID TO RESEARCH THE WARNING AND ERRORS the IDE points out to you AND RESOLVE THEM!

enraged_camel 11y ago

>>Personally, I think it's bullshit that I can show employers all the things I've built and they still expect me to write a reverse sort btree or whatever the fuck thing that has nothing to do with web development. As a business analyst interested in a software development career, this is what worries me the most about interviews. I write a fair amount of code. I have developed apps that work really well and solve important business problems. I can talk intelligently about everything I've developed, but if you asked me to write something on the spot I'm not sure how well I'd do. Most of the time I find the information I need through exhaustive searches on the Internet as well as lots of trial and error. Is it really a deal-breaker that I can't write a tree sort algorithm off the top of my head?

serge2k 11y ago

How do they know you built anything? Why should they expect that your experience will count for anything if you aren't willing learn a bit about data structures to pass that portion of your interview?

Mc_Big_G 11y ago
I have a large portfolio and I've never needed to write an algorithm to sort a binary tree (for example).
- serge2k 11y ago
  How do they know you actually did the work on the sites/apps you present? Dead easy to take credit for someone else's work. I'm saying a desirable trait is that you can learn new things to solve problems. You know approximately what the problems they will give you are, if you aren't willing or able to go out and learn the necessary skills then why should they hire you?
  - Mc_Big_G 11y ago
    The large portfolio comes with a large list of references. I could also show them the code for every project. I've never been asked to produce either of those in an interview. No one has ever looked at my github account either. I never said I don't want to learn new things. Quite the contrary. I stay up to date on the latest web tech and have been frequently contracted for that exact expertise. However, I do find it frustratingly annoying that I need to learn a multitude of "interview puzzles" that I'll never use in real life.