4 ms·
Damn, that guy busted his butt. I got a creative writing degree from a decent but relatively unheard of Texas state school, spent a month studying Javascript, g
by komali2 10y ago
Damn, that guy busted his butt. I got a creative writing degree from a decent but relatively unheard of Texas state school, spent a month studying Javascript, got into a bootcamp, worked for the bootcamp as TA for 3 months, then got a ~120k/yr job in the bay area within a month of leaving the bootcamp. I had 3 projects on my resume and absolutely nothing technical to show for the time period prior to the bootcamp, other than a single Intro to CS MOOC.
I always marveled at the people like this that seemed to do so much more concrete things than me. I leveraged my strength - talking, knowledgeably - and that worked well, but many of my peers got in on their technical ability and work ethic alone.
I haven't written as in-depth a blog post as this guy but I have a couple articles for those interested:
1. Linkedin tips for bootcamp grads http://blog.calebjay.com/2016/11/14/how-to-use-linkedin-as-a-coding-bootcamp-grad/ http://blog.calebjay.com/2016/11/14/how-to-use-linkedin-as-a...
2. Jobsearch tips for bootcamp grads http://blog.calebjay.com/2016/10/18/how-this-coding-bootcamp-grad-found-a-job/ http://blog.calebjay.com/2016/10/18/how-this-coding-bootcamp...
This makes me think maybe I should put together a more holistic article on the entire process.
EDIT: I'll be watching this for a while if anybody has questions on the bootcamp experience, resulting jobsearch, etc.
- jhmj98foeiedkj 10y ago"spent a month studying Javascript" + 3 months seems surprisingly short; a very large return on investment. I'm CS undergrad(almost half-way), but by job requirements none of my skills are even close to being employable. I guess I should start Js If you don't mind sharing, What topics/frameworks did you learn in that time and if not the same, what frameworks/skillets are mostly used day-to-day?
- komali2 10y agoThere's about 1,000 Web-dev specific jobs posted to Linkedin, daily, in the SF Bay Area, so yes if you're interested in getting a job fast I recommend it. But if you're a CS undergrad I'd target some of the more niche stuff that you can leverage your degree to get, like Machine Learning, Machine Vision, AI type stuff that are inaccessible to me until I get projects under my belt. If you're halfway, in two years you'll be up against even more bootcamp grads than I was - not something that would be much fun. We focused on: Javascript Node Express, and building a server/routing HTML CSS Angular React Backbone MVC client-side Security and XSS basics Auth basics (I wish they had focused on this more) Basic algorithms and data structures (your binary search trees and whatnot) Interview Prep SCRUM stuff (couple group projects) Git Deployment (mostly heroku) To condense it down, I'd say you should be able to, upon graduation: Build from scratch a functioning web application, with a backend that you wrote, that is accessible via the internet one way or the other. You should definitely have some projects published by the time you graduate, because you'll be going up against bootcamp grads with 2-3, or more, demonstrable projects. A big sell the bootcamps go on is that their grads are actually more "job-ready" than someone fresh out of a CS program, the perception being the CS person will have a spotty knowledge of actual hands on programming and deployment. Obviously your program results may vary, but just be aware that's the perception bootcamps and their grads are exfiltrating into the tech community, so it'd be a very bad idea to fall on that radar. EDIT: I'm remembering now that a lot of CS applicants to my bootcamp would have projects on github, but would need to be pulled down and compiled to actually work (python projects and whatnot). If you end up with a lot of these from your classes, see if you can use that language's server systems to set up a simple API, with a very basic front-end, that allows interaction via the internet. Being able to, in a job fair, literally pull a project up on my phone and show it to a company rep was a very powerful tool.
- popdoit 10y agoMay I politely say "fuck you" for getting a 120k job after completing a bootcamp. Starting salary of 120k/yr for someone with a 3-month vocational program and an unrelated undergrad degree? That is literally insane.
- komali2 10y agoHah, you may, it does seem pretty crazy, doesn't it? I would say that the reason it seems crazy isn't rational, however. If I was forced to break down the reasons that this worked, I would condense it to three: 1. I focused entirely upon a single skill that is highly desired right now (Javascript / Web Development in JS/HTML/CSS/JS Frameworks). I didn't "waste" any time learning other programming languages, systems designs, or even anything beyond the most basic of algorithms and algorithm design. These things are not necessary to build webapps in Angular/Backbone/React/Vanilla. My bootcamp (hack reactor) assisted with a very focused curriculum. 2. I was able to condense this learning to a short period of time by being utterly focused on it and nothing else, all day, every day. I was learning the one skill I needed to be employable from 8a-9p Mon-Sat for 3 months, and then 8a-5p Mon-Fri for another 3 months (when I was a TA). 3. I am a highly sales-trained ex-recruiter, and know through experience and training exactly what I need to do to get a job, fast. This includes being an annoying little bastard ;) but also includes streamlining my processes (never spending more than 10 minutes on a single application, etc) and being very good at turning a "no" into a "oh, ok, let's talk more."
- ryandrake 10y ago> being very good at turning a "no" into a "oh, ok, let's talk more." Honestly wish there was a 3 month bootcamp for this.
- komali2 10y agoBe a recruiter for a bit :P or any sales job, really. Best advice I can give is treat every "no" like a probe from the other side to learn more. They're not saying no, they're saying "I don't know enough about this to want it." Obviously use common sense to avoid harassing someone, and don't waste your time where no opportunity exists (Mark Cuban reacted to the infamous "sell me your pen question" with "Do you need a pen? No? Ok, have a nice day.") So every "no" has a response - 1. "No, you don't have enough experience." Response: "I understand that this role requires the right experience. I applied to the job because I'm confident I have the experience you need. What about my background makes you feel otherwise? Do you have a coding challenge I can complete to demonstrate my ability?" 2. "No, we've had issues with bootcamp grads in the past. " Response: "Hm, I can understand why having an experience like that would make you wary about bootcamp graduates. Was there something specific about why that grad didn't deliver? (choose response based on further information gathered, then: ) Hm, that does sound challenging. I think that my x y or z demonstrates why that issue wouldn't arise with me / I would love to demonstrate via a code challenge why I wouldn't x y z / If you go to myproject.calebjay.com you can see that I have quite a bit of hands-on experience with x y or z, so I'm confident that a b c wouldn't be an issue. I'm remembering now an old sales training "no" breakdown: 1. Acknowledge the concern. Make the client feel that their concerns are valid, do not challenge or attack them, but at the same time avoid perfectly validating their belief that this is a harbringer that all similar solutions warrant "nos." So: "Yea, it is quite frustrating when recruiters send candidates that aren't even close to a good fit. You should see some of the resumes we people send to us when we open a job!" === good. "Oh man recruiters are so annoying, yea I would definitely never use them" === bad (when you're a recruiter trying to sell your services. Also, "psh, recruiters never act that way, you must have done something to annoy them" === bad. 2. Information gather. Always good all the time anyway. Usually the first "no" gives very little information and you could make some bad assumptions. "We've had bad experience with recruiters in the past" tells you literally nothing. The answer they give you can lead you straight into one of the fifty sells your company has drilled into your head. "What happened with the previous agencies?" "Well, they were sending bad resumes." --> "Oh, we get some hilariously off resumes. We like to think of ourselves as a filter for our clients, so we get maybe fifty resumes for a posting which allows us to hand-pick the best 3 for our clients." "Well, they would have three or four recruiters constantly calling us." "That is frustrating, we decided two years ago to only allow a single recruiter point of contact for our company because of that exact feedback from our clients." Etc. 3. Close. Of course.
- spraak 10y agoI'd say a lot of luck, too? I did the same but my salary is only half that. Edit: I do get to work remotely though, and the salary is in UK terms
- BinaryIdiot 10y ago> I'd say a lot of luck, too? I did the same but my salary is only half that. Depends on the area. In the Bay area it's not uncommon to start at a job as a junior for around $100k. Living expenses really push this up. In the MD / DC / VA area, in my experience, juniors can start at most tech / consulting companies at $65k or higher.