Ask HN: How long did it take you to get your first dev job?
11–20 of 57 posts
Re: Ask HN: How long did it take you to get your first dev job?
#12All that said, what sort of experiences are you putting on your resume? If you're involved in any open source projects, include them. If you've got a Github account with some small code projects, do list the URL in your resume. Every little thing helps!
You need to remember that your resume needs things to help you stand out from the crowd.
Re: Ask HN: How long did it take you to get your first dev job?
#13Also I put a lot of effort into making my resume the best I could. Don't neglect this. It is the #1 most important thing you need to do when searching for a job.
You mentioned your intern experience being at 'lower tier' comonies. Are you maybe being too picky in where you are applying?
Re: Ask HN: How long did it take you to get your first dev job?
#14Re: Ask HN: How long did it take you to get your first dev job?
#15I'm not a typical example -- my experience here is over 20 years ago, I had no formal training in CS/engineering, and I was looking for work in an area that no one had open positions for (what people called a webmaster position in '95, but this was '92). I worked as a temp for a year until I got lucky with contacts / networking and found a company that needed my skills. I did very well for myself once I was able to demonstrate my expertise -- and I believe that's as true today as it was 25 years ago.
Re: Ask HN: How long did it take you to get your first dev job?
#16For anyone who came here to share advice about my resume, here's a link via my VPS: http://162.243.149.58/Resume.pdf
Re: Ask HN: How long did it take you to get your first dev job?
#17And don't be afraid to experiment, tweaking your resume and cover letters. In the meantime, build little projects that are interesting enough to put on github and your resume.
Re: Ask HN: How long did it take you to get your first dev job?
#18Re: Ask HN: How long did it take you to get your first dev job?
#19The total time it took varied by company, but was generally one-two months. Most companies moved quite quickly, regardless of their ultimate decision. The longest lapse was between the initial contact and the first interview, usually. Of the companies I interviewed with, two were big Silicon Valley names, one was a small consulting org, one was a big insurance corporation, and the other two were fairly large private software companies (but not Valley companies). I went with one of the last two. Three of the companies I interviewed with actually contacted me first; interestingly, all of them made me offers.
I have a good single-page resume, and a personal site with more detail on it. More importantly, though, I'm good at the non-technical side of interviews, which helped me everywhere except the companies that do nothing but demand you regurgitate rote CS knowledge (read: Google). One trick I did was a short (But me talking about me won't help you. Let's talk about you. You're anonymous on here, your profile doesn't link to any identifying info, so be real:
Are you a student or recent grad, or are you self taught? What's your story? If you're a new grad, what was your GPA? If What I'm getting at is you need to take a hard look at your networking/interviewing practices and see where the gaps might be. If you put the answers here, I am sure people will help you. Do post your resume as well.
Re: Ask HN: How long did it take you to get your first dev job?
#20 Venture-Capital Investment by City
Rank Metro Venture Capital Investment (millions) Share of Global Venture Capital Investment
1 San Francisco $6,471 15.4%
2 San Jose $4,175 9.9%
3 Boston $3,144 7.5%
4 New York $2,106 5.0%
5 Los Angeles $1,450 3.4%
6 San Diego $1,410 3.3%
7 London $842 2.0%
8 Washington $835 2.0%
9 Beijing $758 1.8%
10 Seattle $727 1.7%
11 Chicago $688 1.6%
12 Toronto $628 1.5%
13 Austin $626 1.5%
14 Shanghai $510 1.2%
15 Mumbai $497 1.2%
16 Paris $449 1.1%
17 Bangalore $419 1.0%
18 Philadelphia $413 1.0%
19 Phoenix $325 0.8%
20 Moscow $318
From http://www.theatlantic.com/technology/archive/2016/01/global...