The best thing I ever did was look at my friends early on who were getting found on linked in and organized my linkedin profile to look as similar as theirs as I could truthfully. The next best thing was taking 6 months off from freelance work to just build a portfolio of small projects that demonstrated the skills people were looking for, and it made interviews much simpler.
I honestly refuse technical interviews at this point because they're a waste of time and I don't study the crap they ask for and it indicates technical leadership can't spot a good developer by looking at what they've built and talking to them about their methodology.
If I really want a new job pronto, I email 5 recruiters who send me the most random postings and tell them what I'm looking for. Last time I did this I had 6 interviews scheduled that week and was in a new job that met my requirements in 2. This is in Kansas City, and while there is a fair amount of tech worker shortage here it's no where near what it is other places.
Honestly the OP's story doesn't sound all that different from my own. Started a tech company in grad school, taught myself javascript and front end work, left just before what we started was sold for a small amount and didn't get anything out of it except exhaustion and credit card payments on top of student loans. But my "40 hour a week vacation" as I called it didn't work out and I got dumped in an executive reshuffling. Did one of those code bootcamps to learn back end C# .Net MVC work in 6 months and got my first developer job at $40k, got the next one at $60k 6 months later, $75k 6 months after that, and $100k 6 months after that.
It's very doable anywhere in the country right now, but you can't just float down stream. You have to have a plan and actively work it and check yourself against the market and learn stuff people want you to know to get to the next level. Your skillset is not a constant, and it's up to you to demonstrate that you have it. If you leave it up to someone else to figure out how to do all that you're screwed, because if they knew how to do that they wouldn't hire so many developers who don't know what they're doing.
1. If you're going to swear, don't use an asterisk to try and make it look good. We can take it, honest.
2. Something in between two asterisks on HN gets shown in italics.
That's a ridiculously good trajectory actually. Did you go to each next job based on what you built previously (plus the business experience), or were you also doing your own stuff in parallel to work?
Front-end work was really undervalued as we priced our work, but the only thing that was less valued were my MBA and business operations skills, so I kept doing that until student loans kicked in.
I did a lot of community centered work for free and freelance stuff on the side after I left especially after my Senior UX job at a startup that was making money fell through, but it wasn't until I built my portfolio and assembled what I could that was all over the place and used it as my initial resume that I realized people would hire me as like an actual employee web developer.
It's a couple years out of date now, and really starting to show its age, but this is what I used when doing my initial job hunting early in 2013. http://www.startup-designs.com
So some of the trajectory is due to the foundation I had already, but most of it was talking to people I knew who were where I wanted to get to and blatantly copying what they told me I needed to do. It's not rocket science the stuff that actually works, but it's not intuitive either.
I second this experience. In fact having an easily accessible portfolio (aka website) was what got me interviews and current job.
I was let go from help desk position about 3-4 years ago. I admit I was over paid help desk tech. I tried to use that time to restart my career (study) as a linux admin/tech. Despite my years in IT working as IT tech and Windows admin, I didn't get much response. What really helped get my current job was putting up a blog with tutorials explaining how to do certain tasks on Linux/webdev. I have a few dozen articles and each blog post is 2000+ words. Each took many hours to complete, some days. It goes from learning something, start writing, editing, going through the steps again to ensure it works.
For anyone who's having a hard time getting a job in tech industry, your goal should be putting up online an example of what you can do that others can view easily. Our industry is blessed with workers having this option. In most other career fields, this is not possible.
I would encourage the original poster of pen.io to put up his work as part of his resume. I feel his pain as I'm also not in the early 20's age bracket but don't give up.
How could you do that if you don't have a degree? Very few grad schools will admit someone without an undergrad degree.
If you live in a small town, I can believe that the opportunities are limited, but in basically any metro area of any size, it's a developers' market.
I live in Fort Worth, I was in the market last month and I got flooded with offers for interviews from the North Dallas area (Addison, Plano, Frisco). Not talking about these "urgent requirement" emails from indian recruiters, this is actual local recruiters I have dealt with before.
My background is pretty much like OP: I learned to program BASIC on the C64 and dropped off college, the difference is I did all that in South America. Since I came to the US in 1999 I haven't had trouble finding a dev job besides being unemployed for 6 months after the dot-com bubble.
We could easily put you in San Antonio or Austin. We might even be able to do Seattle or Cambridge (near Boston), though those are tiny offices.
If I remember right and we did reject you, try a different office.
Third sentence: "If I remember right and we did reject you..."
---------
Where do I even begin with this.
Guess what? The employers were pickier than the recruiters.
I've learned to deeply distrust recruiters: they are known to make up lie after lie just to throw as many names in front of an employer as possible on the off chance one of us gets hired so they can grab their commission. They'll ask employers to interview blatantly incompetent candidates (including myself: I was absolutely not competent for some of the positions recruiters tried to get me) just because they're that desperate.
Then, when I was looking for a new job in 2014 (employed, but unhappy at my then-current position), I got innundated with so many recruiters lobbing utter shit at me. This time, I could afford to be picky, and I wasn't afraid to say to some of the shadier ones, "never contact me again". I had multiple recruiters try to offer me a six-month contract in another state, despite my profile on every job site saying both "unwilling to relocate" and "full-time only, no contracts". I had recruiters try to get me positions that required twice the amount of experience I had in technologies I've never touched. I had one recruiter repeatedly send me calls and emails for a position I explicitly told them I wanted no part of the first time he contacted me, and he didn't stop until I sent an email saying "please cease and desist from contacting me again, or I will take legal action against both you and your firm" (I should've also called his firm's HR department, but c'est la vie...).
Oh, and now that I'm happily employed at my current employer, I still get frequent calls from recruiters. I legally changed my name (first, middle, and last) in June 2014, but most of the recruiters calling me ask for me by my old name, and I'm at a point in my life where even hearing my old name causes me emotional distress.
In short: recruiters are sleazy, and being contacted by recruiters has no bearing on whether or not you'll actually get a job.
But the good ones look for good matches and good candidates, and don't waste people's time with junk. One recruiter placed more people on my team, with a much higher hit-rate, than any other one I dealt with; when I was interested in changing positions, I let him know, and after a month in which he didn't bother me at all, he pointed me toward an opening that was a perfect fit for me.
If you build up relationships with recruiters, you'll learn which are which, and how to ignore the Robert Halfs and Manpowers while still getting the benefit of the good ones.
I had one recruiter call me and sell me on a position as a portal developer. At the end of the call he finally asked "by the way what is a portal?" He was dead serious. I was livid.
I'd bone up on that, and learn angular inside and out as well as a couple of other JavaScript frameworks for good measure. That's what gets me hired as a C# developer in php, ruby, and java shops where I can then gradually show them I know UX, devops, and other little valuable things. The trick is that the hot thing in short supply will change this time next year and you'll need to keep a finger on the pulse of it and learn that if you're looking to job hunt.
I'm actually writing a UI in Angular right now or a Java-based system I wrote. I hate it. It is a pain I'm going through because I need a UI for this prototype, but there is no way I would want to do this full-time.
For node work you really need it, but if you're using .net you're running a framework on top of your framework. So kind of more of a pain in the ass than you need to deal with for most things.
Businesses move slowly, and new project uptakes on technology is usually 3-5 years after initial release... .Net was out int 2002, but it wasn't until close to 2005 that it really started getting popular... jQuery was 2006, and almost an exception, but still not really strong until 2009... 2009 started Node, but it didn't start to shine until 2012-2013... it takes a while.
As it stands, at this point Angular is out there and a lot of current jobs are using/require it... if you can't sell a better option (polymer, react, etc), then you're stuck with it.
(The last couple are usually Idaho or Nebraska or one of the other corporate-fief states.)
For example, you might not expect much good in Melbourne, FL. You'd be wrong if you happen to like low-level code (assembly, reverse engineering, vulnerability research, embedded development, etc.) or EE stuff. There are both larger companies (Harris, Lockheed, Northrop Grumman, and the http://advancedsecuritylabs.com/ part of Raytheon) and lots of startup-ups.
Since a specialized area (like Melbourne, FL doing low-level stuff) doesn't have too many nerds outside that specialty, the cost of living stays low. You can get a cheap house within a mile of work and there isn't much traffic.
I don't know your background, but would suggest going with a modern Java framework, or ASP.Net MVC and build something... go through the latest Apress or O'Reily book on the subject in question... At the same time start going to user group meetings locally. This will tend to get you at least in the door as far as interviews go... from there you're on your own.
Yes, some places you won't get past H.R. without a degree, but I've been at this for a couple decades now, and as long as you get current or keep up, you should be employable.
I've found employment since (and even changed jobs over the new year), so it's definitely something one can recover from, and for all I know the job market might have changed since then so things are better now.
Anyone saying there are no jobs in this area has a crappy resume or no skills
believe me, we don't have millions of those ready. Many can code, but code in "real" life where you don't have luch room to learn from mistakes, well, there ain't many...
I enjoyed that.
I was talking to a recruiter recently for a managerial job and somehow got onto the topic of hiring. I asked him what's the hardest jobs for him to fill right now. He told me he's dying for entry level .NET/ASP and Java developers. Corporations have built their castles on these technologies, not FOSS/Mobile and need staff. Degrees were an issue but he said he could place people with two year degrees.
We talked about pay, and it wasn't terrible impressive, but for someone straight out of community college it sounded pretty good to me and he also revealed that if the person wasn't a complete nightmare socially, he could expect to be promoted quick.
Why does he need so many entry level programmers?
> We talked about pay, and it wasn't terrible impressive
Is the recruiter trying to staff a company with mostly entry-level programmers, paying low wages? I've seen plenty of companies like that, including those who used mostly trainees. Usually, the work environment was the crappiest possible, and word gets around.
My theory is that technology trends are leading the entry level developers to learn Python, Ruby, and JavaScript rather than .NET or Java, thereby reducing the supply and putting these candidates in high demand.
All they care about is # of jira/tfs tickets that are open, and the number of features, and how many warm bodies based on their averages they need. The smoothest project I ever worked on was staffed by all senior people, with relatively diverse and overlapping skills. That wouldn't be possible with 3x the developers if 2/3 of them were junior to mid level.
It doesn't sound like you're describing a world in which someone with 10+ years of solid experience with techs is going to be struggling to find a job, right?
Overqualification (or the perception thereof) happens. The development world, like most others, is a bit of a pyramid. More experience doesn't necessarily translate to more positions being available. Some (many, even) are specifically targeted at young, entry level devs.
How many years of experience and how much demonstrated expertise did he require from these" entry-level" candidates that he supposedly can't find?
It took them 9 months from the interview to get back to me with an offer (which is why I was already working somewhere else) and the offer was $30k for a one year contract.
If that's still typical of their hiring process, I'm not surprised they're having trouble hiring people.
Pass along his email if you can: [email protected]
On the flip side, I share knowledge and work to leave code better when I'm done than when I start. Others will show up/leave on time, but won't share anything and will leave very obfuscated code in place.
Lets face it though... the personality traits that make one adept at somewhat technical and often mundane tasks have a pretty high correlation to some generally less than desirable personality traits. Programming is much more of a craft (or even art) than it is an engineering discipline in most places, but we have to interact with business roles where expectations and mindsets are vastly different.
During those two months, I had phone interviews with two other companies, one of which I bowed out of the process because as I learned more I didn't believe in their mission, and the other I got turned down on.
The sum total of my "trying to find a job" was making a profile on StackOverflow Careers and answering a Reddit ad.
For what it's worth, I have no degree and am self-taught. In 2012, I had ~5 years of experience as a full-time dev, and none of it was in a traditional environment.
In several countries in Europe and in LatinAmerica, landing in a well-enough job can be a matter of several months depending of the skill-set.
My advice to the OP would be to find and get in touch some of the older recruiting companies, the ones that exist more than 10 years on the market, and work with them. Steer clear from the startup scene. Normal companies still need the job to be done - why not by you?
2 actual interviews that were offered to me early in my career :
1. The weekend hackathon (which actually ran from Friday until Monday)
2. The full-week trial
I took #1, but not #2. I was working at the time, and in no way could justify taking a week of vacation just to work for free for someone else.
I haven't found that to be the case here in the Raleigh/Durham, NC area. I never finished my bachelors degree (although, I do have three different associates degrees), and I have never found it to be an inhibition to my career.
Why don't you just change the domain your working in? Why not web dev? If you're a programmer, you should be able to code anything, anywhere, with a bit of effort.
I skimmed your post (https://wmkrug.com/on-the-technical-skills-shortage-and-hiri...) and honestly I'm not sure. I mean, you're saying that requiring "years of experience" in "specific technology" makes "good candidates" to get rejected. But why do you think that someone without these years of experience would be a good candidate?
Experience and skill are necessary. People without experience have little skill by definition: you only improve your skills by doing and remembering what you've done (well and badly) is called experience. Such people are not worthless, but as employees they are worth significantly less than people who demonstrably have both experience and skill.
You seem to be thinking that the employers should let you learn your profession on the job because the college failed to do it. I don't think so. I believe you're the (like we all are) one responsible for teaching yourself enough to be a viable choice for at least an entry position. It's not that hard if you have a passion for the craft and patience to continue learning over the years.
Is that really true? I do database programming, and I feel like I would be absolutely screwed if somebody demanded I do, say, embedded programming for small microprocessors. I guess theoretically I could study up, but it would be at least a year or two before I could be competitive in interviews, right?
Maybe I just suck and there are genius programmers who are equally competent at embedded systems, mobile development, distributed systems...
Yes, I believe so. And it has nothing to do with genius!
First: of course you wouldn't be able to get senior dev positions in a domain you never worked in. You have to be prepared for this. Pay cut is obvious just after the change, and you need to decide if you can afford it.
Second: it's a matter of how long you're going to stay junior in your new domain. In practice, this is a question of how solid your foundations are and how experienced you are already, and also how determined you are. I believe in what jwz said in "Coders at Work": different domains have different vocabularies, best practices, and myths, but deep down it's still just standard coding. There are variables and loops and branching constructs everywhere, no matter the domain.
> there are genius programmers who are equally competent at embedded systems, mobile development, distributed systems...
I doubt there are many people who are competent in many domains at once. There are such people out there and they're very expensive specialists. Still nothing to do with genius, but rather hard to achieve. However, you don't need to be like that: you just need to change the domain, not master a new one while retaining all your skills specific to the previous domain.
The two most important things for making a switch are your foundations and experience. In your example - embedded dev - you'd need to have a good prior understanding of how CPUs work plus knowledge of C and Asm. Given this you're almost immediately ready to code, after maybe a week of reading the codebase, manuals, and refreshing AT&T asm syntax (for example). You - every programmer, really - should know at least the basics of such things from college or self-study.
The experience is important because it gives you an intuition as to where the potential problems and hurdles in your learning would be. More than anything, experience provides you with an essential skill, a systematic (working for you) way of assessing and learning a new technology. It's much easier to change your domain for the fifth time than it is for the first time. Even if the previous areas you worked in have nothing to do with the one you're learning right now.
For me, programming is a lifelong career choice. That means I have ~50 years of programming still ahead of me. I can't imagine working for such a long time in a single domain! In a bit more than a decade of my professional programming, I already switched domains four times. Despite the fact that I'm self-taught, and my foundations were lacking for quite some time. (I like to believe I fixed this after a couple of years.) It wasn't easy, but if I did it, then I'm sure almost anyone can :-)
What is baffling is this Valley-centric, web and mobile development-centric line being repeated constantly in this thread. Most of the world is a different story. Outside the Valley and a couple other metros, and outside the web and mobile fields in general: 1) degrees are usually required; 2) employers are much pickier.