Live data from Hacker News

What I learned from spending 3 months applying to jobs after a coding bootcamp

medium.freecodecamp.com

291–300 of 398 posts

Re: What I learned from spending 3 months applying to jobs after a coding bootcamp

#291
post #104

Is anyone else bothered by the code at the beginning of this article? Simply returning the expression would have had the same effect, ie: function getDevJob(studying, hardWork, luck){ return studying && hardWork && luck; } I know that it might not make the code readable to novice javaScripters, but it bothers me anyway..

That's not even the biggest problem with this method. The name is totally wrong.

Re: What I learned from spending 3 months applying to jobs after a coding bootcamp

#292

Earlier quoted context omitted.

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'm not too surprised either, but I marvel at the amount of time wasted preparing and asking all the stupid questions when they could just look at my code for 5 minutes. Like, the main file in one of my libraries clearly uses concurrent locking, it even says so in readme.md . These were all last round on site interviews and we spent maybe 30 minutes of 2 devs time going over pointless stuff when they could just skim…

This.

A company, that advertised here on the last "Who's Hiring" sent me a code project.

Wasn't quite enough to be 'you're doing a sprint item for us', but merited decent effort:

- write a log monitoring console program that consumes an actively written to file

- parse out specific parts of the log and aggregate them every 15s, display summary data

- generate 'alert' notification when log messages/second (over the last two minutes rolling average) exceeds a threshold

- remove notification when fall back under this limit

- continue to generate stats while doing so

- develop some unit tests to demonstrate alert logic

This is, at least to me, _several_ hours of decent work. Certainly was nearly 500 lines of code.

Submitted.

"Thanks for this. We'll review."

Last I ever heard.

Thanks.

Re: What I learned from spending 3 months applying to jobs after a coding bootcamp

#293

Earlier quoted context omitted.

I went to one of these programs in America and my starting salary was "only" 85k, mainly because I took a job that wasn't in New York or SF. Most of my classmates who took one in one of those high cost of living cities did 90-110k I believe. I would call 120k+ an outlier on the high side, but not inconceivable. This was years ago and I don't know if the bar has slipped as coding bootcamps have gotten more popular, bu…

What's funny is that those figures were the pay back in the mid-1990s as well.

Indeed. Which proves there is no shortage of tech workers if salaries aren't even keeping pace with inflation

Re: What I learned from spending 3 months applying to jobs after a coding bootcamp

#294
post #48

Earlier quoted context omitted.

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.

There's an extra tax paid by the employer, technically "employer's National Insurance contributions", which is about 10% (up to a limit). So that's comparable to US payroll taxes. 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.

Odd.

Admittedly my sample size is low (2), but some level of private health insurance was offered at all the places I've worked in the UK.

Re: What I learned from spending 3 months applying to jobs after a coding bootcamp

#295

Earlier quoted context omitted.

That's a huge point. "Code bootcamp" can mean a huge variety of things. At its best, it often means "technical, business experienced, just transitioned into intensive software study", which is an enticing candidate. At its worst, it means something like "paid $50k to learn basic Javascript". Lumping those two together makes it really hard to draw any conclusions about experience.

The average age in my class was 28. People weren't ex-baristas. They were people from various backgrounds, often technical-related. I was a Math and Econ double major with a minor in applied statistics, then spent 6 years in finance doing equities trading. I was drastically more qualified than the average 22 year old with a CS degree.

Just curious why you went from equities trading -> software engineering? I have thought about doing the reverse in the past.

Re: What I learned from spending 3 months applying to jobs after a coding bootcamp

#296

>> I applied to 291 companies, did 32 phone screens, 16 technical screens, 13 coding challenges, 11 on-sites, and received 8 offers. How much time would that take? Figure 15 minutes per company - 4,365 minutes, or 72 hours. And that's time just spent finding the company, changing around a cover letter, and then emailing it and responding etc. 32 phone screens? Let's say 30 minutes each, that's 960 minutes, or 16 hour…

15 minutes per company for applications is high. Organization helps a lot, and you can really optimize your workflow for sending out resumes. Finding the company: approximate amount of time spent here is 5 seconds. You have a spreadsheet, just go to the next one on the list. Changing the cover letter: template it with variables. Should end up being a single bash command, most of the time is locating and properly form…

>> 15 minutes per company for applications is high.

Applications can be more than just sending out resumes. The worst is when you have to deal with some crappy web site, upload your resume, then fill out a bunch of web forms with your job history, take silly tests, fill out other pages of personal information...

Re: What I learned from spending 3 months applying to jobs after a coding bootcamp

#297
post #285

Holy shit. Is this some kind of a joke? > Otherwise, companies automatically categorize us into junior developer roles or tag us as “not enough experience.” ??? What do you think you are after a TWELVE WEEK coding seminar (no matter how intense it was)? It looks frightening to me that he doesn't even know what "junior developer" really means. How ignorant can someone be to NOT think to be a junior dev right after "gr…

The article does read a lot like the "Psychopath's Guide To Career-Hunting". Honestly, the tone reminded me a lot of some of my undergrad peers who were pursuing investment banking jobs, which I suppose makes sense considering his about section.

That all said, if your goal is to get the highest paying job possible, this seems like useful advice.

Re: What I learned from spending 3 months applying to jobs after a coding bootcamp

#298

Earlier quoted context omitted.

That's because that's what a lot of these bootcamps sell. I've interviewed several grads, and while it's not universal, many of them literally tell their graduates they're going to be better prepared for the Real World™ than their college educated counterparts. Almost like, "You'll be better than a CS grad. All they can do is explain and apply the fundamental thinking process behind all this 'engineering' crap. You ,…

Looks like this author fell for it. I also don't mean to typecast anyone, but the author's profile on that site reads, "Full-stack dev @Radius, ex i-banker, @HackReactor grad, @UCBerkeley," so perhaps he thought his prior experience in an unrelated field or his alma mater should've helped him get a leg up over other entry-level devs. Again, I don't mean to judge since my path to software development was also non-stan…

"UCBerkeley" and "can program" seems likely to help people assume a Berkeley CS background without actually having to claim one.

Re: What I learned from spending 3 months applying to jobs after a coding bootcamp

#299
post #104

Is anyone else bothered by the code at the beginning of this article? Simply returning the expression would have had the same effect, ie: function getDevJob(studying, hardWork, luck){ return studying && hardWork && luck; } I know that it might not make the code readable to novice javaScripters, but it bothers me anyway..

I'm more bothered because it's becoming "so clever" to put everyday life activities into a function. I saw code written in chalk on a sidewalk billboard at the door of a coffee shop yesterday. No, I will not reciprocate that cringe and verbally call a function to order my coffee because the barista learned Hello World the previous night.

Becoming? It's been this way since I first started hanging out in internet tech circles (eight years, longer I'm sure).

Re: What I learned from spending 3 months applying to jobs after a coding bootcamp

#300

Earlier quoted context omitted.

Github makes it hard to tell what code is yours and what is something you just forked from somebody else.

I thought it showed on the page if a project was forked; perhaps it makes fraud possible but wouldn't it be spotted almost immediately when you started work, if it wasn't spotted then arguably it doesn't matter.

Forks of GitHub repositories are marked as such, forks of projects hosted on other sites are not.
Post reply on HN