This whole hardcore quizzing and testing during interviews has to go. As far as I can see, all it does is create selection bias for people who memorize things or like to practice interview questions. Maybe that's just me being too old for that kinda' crap.
What I learned from spending 3 months applying to jobs after a coding bootcamp
41–50 of 398 posts
Re: What I learned from spending 3 months applying to jobs after a coding bootcamp
#42Re: What I learned from spending 3 months applying to jobs after a coding bootcamp
#43This whole hardcore quizzing and testing during interviews has to go. As far as I can see, all it does is create selection bias for people who memorize things or like to practice interview questions. Maybe that's just me being too old for that kinda' crap.
Re: What I learned from spending 3 months applying to jobs after a coding bootcamp
#44How do you even manage this amount of information? A notebook can help but once you hit the 20 applications mark, it's impossible to know to which companies you applied for.
Re: What I learned from spending 3 months applying to jobs after a coding bootcamp
#45This whole hardcore quizzing and testing during interviews has to go. As far as I can see, all it does is create selection bias for people who memorize things or like to practice interview questions. Maybe that's just me being too old for that kinda' crap.
I have been interviewing the last couple months and have the same opinion. I've been coding for years and have some pretty complex stuff up on my GitHub. I quickly found out that nobody looks at your GitHub, maybe 10% max. didn't matter that I had code from two weeks ago that did complex segmented locking on a concurrent hashtable. still got asked "what is threading" level questions at every place. After botching my…
I'm usually giving the holistic system design question which the interviewee can take any direction they like they just have to go all the way down in one area.
Jr devs on my team give the algorithms question much of the time and I make sure they're looking for the right things. Problem solving not memorization... Comfort in a language not trivial knowledge or formatting issues... Etc. They get sent to the interview class if they ask anything that is a named algorithm... Like three sum, tortoise and hare, etc and expect a candidate to derive it in a 30 minute coding section of an interview. T&H for example took 10 years for industry to derive.
On a side note don't use a language you're not familiar with in an interview because you heard the company likes it. Use what you are solid in. Python and ruby and the like make most interview questions trivial. I cringe on the inside when people jump for c/cpp in an interview esp college hires as it seems to take longer to get fluent in these languages.
Re: What I learned from spending 3 months applying to jobs after a coding bootcamp
#46Are people in America seriously getting offers of $120k with no degree, no experience, and not even a side-project? That is mind-blowing. In London, probably the biggest/richest market outside of USA, that sort of salary is beyond what most experienced developers get, even some very good ones. I must be missing something here (some sort of bubble?) because I can't see how businesses can be profitable paying those sor…
1. Programmers have lower status in the UK relative to the US - UK is more status/class conscious in general whereas US is more about money/productivity/impact.
2. Due to a bigger entrepreneurship culture in the US the opportunity cost for programmers is higher and that drives salaries higher across the board.
Re: What I learned from spending 3 months applying to jobs after a coding bootcamp
#47Earlier quoted context omitted.
I have been interviewing the last couple months and have the same opinion. I've been coding for years and have some pretty complex stuff up on my GitHub. I quickly found out that nobody looks at your GitHub, maybe 10% max. didn't matter that I had code from two weeks ago that did complex segmented locking on a concurrent hashtable. still got asked "what is threading" level questions at every place. After botching my…
I'm not shocked that nobody looks at your GitHub. Reading other people's code takes time and energy that a lot of people aren't going to spend if they have a ton of candidates to sift through.
I think it's just that they have a process built up over time like "interview process.doc" and the devs don't want to make any waves going off script
Re: What I learned from spending 3 months applying to jobs after a coding bootcamp
#48Earlier quoted context omitted.
That's over £90k in our terms you can see why Google and othe reengineering companies set up in the UK as we are cheap
I have no familiarity with the UK tax practices, but what kind of burden are you for an employer? The US has 7.5% tax per employee. There are a few others such as health insurance.
Because the National Health Service is generally considered to offer a decent-enough level of care, there's normally no private health insurance in most tech jobs -- so no extra costs there.
Re: What I learned from spending 3 months applying to jobs after a coding bootcamp
#49well first thing - that code at the top can be simplified. function getDevJob(studying, hardwork, luck){ return study && hardwork && luck; } But more seriously - I actually really like point #2. I firmly believe that job interviews have a strong bias towards people with experience doing job interviews. Your "offer-ladder" seems to confirm that for me. It reminds me of that freakonomics article about how real estate a…
Re: What I learned from spending 3 months applying to jobs after a coding bootcamp
#50Are people in America seriously getting offers of $120k with no degree, no experience, and not even a side-project? That is mind-blowing. In London, probably the biggest/richest market outside of USA, that sort of salary is beyond what most experienced developers get, even some very good ones. I must be missing something here (some sort of bubble?) because I can't see how businesses can be profitable paying those sor…