There's certainly a huge skill gap between the code campers vs anyone we've hired with previous experience. Just the day to day tacit skills ticket management, git work flows, variance in tech stacks, client feedback, interfacing with designers, interactions with project managers, ux decisions, and so forth just can't be crammed into such a short period.
I'm impressed by code-camps as web development and software development takes a long time but code campers are green. If you're in a position to take on junior devs, it seems a great way to expand a team and delegate jr level tasks to.
TLDR: I'd hire a code camp graduate to fill junior positions - there's just too many soft skill gaps that code schools don't have time to.
I've also worked with a team of recent bootcamp grads who were highly paid and wrote great ui code quickly. They wouldn't necessarily be up on all the newest tech, but if you told them to use something, they would go home, learn it, and implement it pretty well the next day.
Could the bootcamp ui coders do the Stanford guy's data science? Not a chance. But I know who's ui I would want to maintain.
Does this mean that all Stanford grads are writing spaghetti coasting off an Ivy League degree? Does it mean that all bootcamp grads are technically naive craftsmen? No. Assess coders on their code.
Wikipedia: The eight institutions are Brown University, Columbia University, Cornell University, Dartmouth College, Harvard University, the University of Pennsylvania, Princeton University, and Yale University.
Two questions: Are you in San Francisco, and which bootcamp was this?
Some have a very high bar for entry and are basically just a way for someone who could quickly become competent (i.e. someone with a deep math or some type of engineering background) to ramp up on coding.
Others just let anyone in and teach very basic things so the graduates level would vary widely as well.
I was lucky. I ended up working at a CRUD factory, where they were using .NET Webforms to create the same thing 100 times in a row. I learned a ton in the 2 years I worked there, enough to realize they were doing things in a way I just didn't like. They produced slow code quickly, which is what they were paid to do.
Those two years worked for me to fill in some of the gap I have from not majoring in CS. Now I think I fall in the better than average .NET developer, but I also didn't expect 75k right away. Anyway, I didn't go the route of a code camp, but I did have a CS minor.
One note is that many people I worked with had CS degrees and were unmotivated to learn new coding techniques (patterns or even methods within the same language). I'd say they were bad programmers, but they weren't they were just happy with turning the same thing out over and over again. They were smart, good, wrote bug lite code, and it deployed well. They just didn't care to innovate. They were SOLID work horses, and I have nothing against that. It just isn't the environment I like to be in.
After 3 years of experience I feel that I can now drop in just about anywhere and be productive, but I definitely couldn't back when I started.
Funny thing, the 2 best novice programmers at that place were self taught, one a CS minor and another completely self taught through a PHP side project. These two are still my go to guys for coming up with complex solutions.
For instance so much work is getting data from a form or API, doing something with it and rendering HTML (styled by CSS and maybe adding some jQuery to polish the UI) that I wonder how much advantage a CS major has over someone who is not a CS major but is a good analytical thinker (like an English major who plays chess or an analytical philosopher). Good analytical thinking is not exclusive to CS or to STEM. I don't think CS majors have a big advantage over your typical good analytical thinker until you get to large scale applications where N is huge.
My first full time tech gig was for 37.5k at a shady-as-hell direct marketing company. HTML and CSS, a very little bit of javascript for form validation that I learned at my desk. They let me go about eight months in (thank god).
I failed a phone interview with NYT because I didn't know edge side includes.
I was devastated. Prepared to move back in with my dad with hat in hand, the literal prodigal son.
I passed a phone interview a week later with an ad company. After a three hour on-site interview, they offered me a job on the spot as a front-end developer - at 70k/year.
This was in '07.
I would definitely say that I qualified as inexperienced. I knew enough CSS to take just about any design and slice it into something that worked, and I knew enough HTML to lay it out. I knew a smattering of JS, but the language frustrated me. I had probably about a sophomore level understanding of computer science. I was an academic failure and community college dropout. They took a huge gamble on me. (edit: since this is getting a couple upvotes, PSA: I was undiagnosed/treated ADHD until I was nearly 30. If you think you might have it, talk to a professional. I thought I was strong enough to cope without help, and I was wrong)
I came out of that job knowing ASP.net, some C#, and a lot more Javascript.
But 75k for an inexperienced developer in NYC? Not that high at all. I was probably making only a little more than half of what the other developers on the team were. But damn it felt good to have a career.
These were folks who were months to years away from hitting the ground running, and the value of the offer was entirely on their future potential. I found great difficulty finding a mid-career developer for the 130-150k range that it started making an "investment hire" feel like a viable alternative.
Wow, are talented developer really that hard to find? (Especially, considering you're offering 130-150k.)
Are you insistent on a developer being "mid-career" (I interpret that as having "years of experience") -- or would you accept a highly talented who has just begun career (e.g. a recent CS grad)?
Our hiring needs didn't feel too crazy to me. We were a multi-million dollar a year e-commerce shop, I was the first in-house technical hire, and we wanted to expand the team for personnel redundancy.
Ideally, we wanted someone who would be capable of running a business-critical website. On the technical side, I was hoping for a full stack of skills (top to bottom web app security, server ops, managing technical vendor relationships and integrating third-party modules, zero downtime rollouts, performance and architecture, metrics/instrumentation, and fully-independent backend and HTML/CSS/JS skills to build a secure and pixel-perfect feature beginning to end). Plus, we wanted an early technical hire to be able to work the indirectly technical parts, including technical hiring, capacity planning, and expectations management.
None of this felt to me like we were asking for something crazy unreasonable, but you don't learn a good enough coverage of this to independently steer a ship of this scale until a few years on the job. You can learn bits and pieces on the fly with the documentation around, but it's both risky and slow. Given the hiring climate, it was a risk we ending up being comfortable taking, but it fell short of what would be ideal.
In response to some remarks about adjusting our expectations (remote work, higher salary), our particular situation was not doable for remote---there was zero 100% remote staff among 30+ FTEs and none of our workflow was set up for it---although I wish I had influenced the organization of work in more formative stages of the company to optimize more for remote given the personnel advantages. Regarding salary, it's very hard to increase salary past $150k+ because I found it very hard to publicize it in a way that meaningfully increased the quality of candidates we found entering our funnel. I wish there were a job site for "will pay very well above market for strong candidates".
We were a multi-million dollar a year e-commerce shop
top to bottom web app security, server ops, managing technical vendor relationships and integrating third-party modules, zero downtime rollouts, performance and architecture, metrics/instrumentation, and fully-independent backend and HTML/CSS/JS skills to build a secure and pixel-perfect feature beginning to end
Even at a lower end startup not making multimillion dollars, you've just described 4-6 engineer's worth of talents for 1.5x of a single developer's salary. I look at that list and think I'm never going to get a decent night's sleep while in your employ.
Thanks for the feedback about the 4-6 engineer's worth of talents. It's good to know, and we realized a similar thing and pared down the JD to be less oppressive-sounding.
Sleep and balance was important to the team (I personally averaged around 35-45 hours a week, working one weekend and being called in maybe a half dozen times over a year and a half; the system mostly runs itself), but we didn't find a good way to surface it in the description. Any suggestions on this is appreciated too. I struggled in that when we removed or played down aspects of the job, or emphasized work-life balance, we just got more folks who were seriously green in some parts (front-end devs who can pull together jQuery but have never deployed their own code or had to write backwards-compatible apps).
Sleep and balance was important to the team ... but we didn't find a good way to surface it in the description.
That's a tough one. Any company you ask will say they're great on work/life balance. What else are they going to say? 'No, we're going to work you 80 hours a week every week. If we ever hit crunch mode, say goodbye to your weekends!' The only thing I can think of is to show them that everybody goes home at 5pm by having the 3/4 day onsite start later in the day and end at the same time everybody goes home. It also gives the added benefit of allowing the interviewee to interact with everybody as a group.
front-end devs who can pull together jQuery but have never deployed their own code
For what it's worth, that's pretty standard in web development. I've deployed code through beanstalk or jenkins, but devops sets that up. I've also deployed side projects to my own servers, but that's a whole different ball of wax compared to deploying to a corporate data center with load balancers. I wouldn't trust a frontend jquery guy to set up those kinds of deploy environments. It's a completely different discipline and field.
I was car shopping a few months ago, and I found there's a dire shortage of brand new $10K BMWs.
Or they have a hiring process and that weeds out top performers. And/or they have a hiring funnel that appeals to the bottom of the barrel.
Or all three, which was my experience with about a dozen different companies in SF last October. I chose to take the job where I wasn't humiliated during the interview.
It's funny how this is a legitimate filter, from the job-seeker's point of view. And, by "funny" I mean "a sad testament to SV tech interviews".
We're shopping in that compensation range and my experience has been exactly like cairo140's above: https://news.ycombinator.com/item?id=9964934
Area median 75%ile 90%ile
Chicago, IL Metropolitan $88,630 $109,640 $126,370
Los Angeles, CA Metropolitan $102,310 $126,340 $150,320
San Francisco, CA Metropolitan $112,570 $143,390 $174,120
San Jose-Sunnyvale-Santa Clara CA $137,710 $166,280 >$187,000
I'm from the midwest so my frame of reference is where $150k will get you well into in the 90s percentile-wise. I'm conducting my hunt in the LA area. And just so we're on the same page I included Bay Area numbers. Is $180-200k (on the 190 to 200 side) closer to the right number, with the Bay Area as a frame of reference?One very interesting realization I had looking through the data is that software development, at the median, isn't an especially well paid field. Dental Hygenists in SF earn almost as much at the median, and registered nurses earn much more.
Overall, I think a big part of why this "shortage" exists is that the work is very difficult for the pay, and that career stability and age related employment issues may actually be considerably worse.
I know this is hard for employers to accept, but salaries may have to rise dramatically before people with citizenship or residency status that allows for career choice are willing to commit to software development. For now, I really do think one reason we are able to staff these positions at "market rate" is that we have created a visa program that essentially prevents a large number of tech workers from changing fields (i.e.., there are serious obstacles to coming to the US on an H1B as a software developer and deciding to retrain as a dental hygienist, this kind of personal and professional freedom is not permitted under this visa).
Role 1: top to bottom web app security, server ops, zero downtime rollouts, performance and architecture (shared)
Role 2: metrics/instrumentation, fully-independent backend, HTML/CSS/JS skills, integrating third-party modules, performance and architecture (shared)
Role 3: managing technical vendor relationships, work the indirectly technical parts, technical hiring, capacity planning, expectations management, performance and architecture (shared)
These are still three pretty loaded-up people! Even if there was one person capable of and willing to do this all, their current job title is likely "founder of their own startup".
I'm doing a decent chunk of that, aware of the parts I'm doing shitty, and that is my job title. :)
I was talking recruiting with a mentor. He said some of his best hires were founders he met at startup events looking to regroup and earn a paycheck after the failure of their own startup. Dark—but insightful.
I'm in the midwest for reference, but hiring remotely in the bay area is legit too.
When the current cycle ends, the funding dries up and companies start running out of money, more folks will recognize this as the insanity it is.
Companies like Google and Facebook, large, profitable enterprises that can cherry-pick the best college graduates from the best schools and invest in long-term development, are one thing. But unprofitable, angel and venture-backed startups that are pressured to grow (and that includes headcount) are another thing.
A lot of the salary froth at the entry-level end of the market is being driven by the latter, not the former. This has nothing to do with the long-term demand for skilled, experienced software engineers.
[1] hundreds of thousands in sales a day [2] around 10-50k LOC, but a far cry from the greenfield toy apps that bootcamp devs spend 90% of their time with [3] position: relative and z-index: 100 fixes many UI bugs, but if a dev has that as a main piece of their toolkit, you take on UI code debt or drag down the team to steer solutions in the right direction.
My take on bootcamp grads (I am one), is that the purpose is to make them a competitive or superior option to a fresh CS grad. How does that expectation compare to your experience?
$100k for a remote hire mid-career developer shouldn't be hard to find.
I don't know about the GP's situation, however.
Remote work at 6 figures is still worth it and widens the pool alot.
On the first day, the woman who was QA quit because she wanted to do development, despite being explicitly hired as a QA.
2 months later I had to let one of the developers go because she produced very little and was surfing YouTube for much of the day.
The last developer I did not opt to hire at the end of his internship. He was a smart guy, but he needed years more experience to operate at the level of our other engineers and he was demanding a 75k salary.
I used the 75k he wanted and hired a competent developer with a CS degree and a couple years experience. He is orders of magnitude better than the boot camp guy was.
It is possible that a boot camp graduate could be useful after several years' experience, but fresh out of school they are extremely raw and need years of training. Therefore I won't be hiring any fresh graduates again.