Ask HN: How do you build up your first career close to age 40?

My company is fully remote. When I interview people, I don’t know how old they are, nor do I care. I look at their job history as it relates to their ability to perform the job for which they are applying. If you were applying for an associate or junior developer position, your lack of experience wouldn’t really matter. I would worry that your bouncing around reflects that you can’t be counted on to stick it out for more than a year.

To change my mind, during the interview, when I ask, you would need to explain what is different about your approach now. Not just that you want to be different, but what you are doing/thinking differently. If you gave a decent answer and everything else lined up, I would take the chance.

So, my suggestion is look for small start ups. Their hiring practices aren’t as rigid.

You can build up a very fine career as a freelance software engineer. My career really took off the moment I quit my job and became a freelancer at age 37.

Of course as a freelancer, working on our network is probably more important than otherwise; you need to be able to find interesting projects, and you need recruiters and hiring managers to be able to find you. I think I've still neglected this aspect a bit too much; I mostly trust recruiters to be able to find my outdated CV on Linkedin, but another freelancer I know makes sure he connects on linkedin with hiring managers of interesting companies. It enables him to get hired more directly, without recruiters getting in the way.

Do polish your CV. Put the focus on the most interesting projects you worked on. Make sure you describe what you worked on, what the broader purpose of the project was, what (interesting) technologies you worked with, and what your responsibilities were.

If you did personal side projects, list them too. Especially open source projects. It's all software experience.

Don't bother listing projects that were both very short and not very interesting, but interesting short ones and boring long ones are still worth mentioning (but the interesting short ones more than the boring long ones: put the focus on the stuff you want to do).

Non-software jobs can still be worth mentioning if they gave you relevant insights or experience, like dealing with customers or other stakeholders, logistic or administrative processes, creative work, etc.

If you look at your work experience from the right perspective, you may find you know a lot more than you thought.

One issue that may be getting in the way of you getting full time work is that you come across as being defensive/testy in response to friendly comments here. Here's some examples below of comments that could have softer phrasing (like first acknowledging the commenters point, then refuting it, instead of jumping into refutation):

"Do I need to make that distinction explicit?"

"What good would a code bootcamp do for me which I can't already do self-taught?"

"Just because that is your preferred experience, you want me to follow it? "

You did not follow the typical path and that's fine. Own it. As a hiring manager, I would want to talk to an engineer who had diverse experience and insight into a variety of businesses. Is there a particular engineering area you want to build a career around?

I'm not sure a bootcamp is necessary but I would suggest whatever intensive interview training you think you need to get into a good tech company. Working at a bigger one is a solid way to bootstrap a professional network.

What I did is set myself apart by going deep on Ruby. I studied for a couple years. I learned it better than most people. Then I found a company that really needed Ruby expertise. I got my first coding gig a few weeks after my 40th birthday.

I'm 40-ish and have been self-employed for about 5 years now. I have no plans to go back to full-time employment. You should consider that route.

There are very few benefits to being a full-time employee that you can't obtain yourself. Plus, having a wide portfolio of freelance clients helps insulate you against business downturns and future age discrimination.

Granted, it's a lot of work to curate a good client list and network yourself. But it's actually the same amount of work as jockeying for promotions and good projects at a corporate job.

And there is some risk involved in working for yourself. But at a corporate job there is similar risk; you are always one bad quarter away from being laid off.

Working for yourself IS a career. Consider fortifying your position and staying the course.

You have several years of software development experience. If that's true, you aren't really starting your career now, you're just looking for a more stable position. I think that the distinction is important especially in interviews because without it you might be underselling yourself.

My $0.02:

When I applied for my first fulltime job the company in question was offering both a contract and fulltime option. I was asked, probably in addition to my history of freelancing, why I was gunning for the fulltime option. I responded by saying that I appreciated the steadiness of work (with freelance you are often looking for the next opportunity), and to help contribute to the success of a particular organisation in the long term. They seemed satisfied by this response. I think they were coming from the point of view that you could make more money by freelancing / contracting, so were just curious as to why I wanted to "downgrade" (not their words, this is just my speculation).

Based on that experience (admittedly I was 23 at the time), you may find prospective employers more open to entertaining your application than you might think due to them having a different perception of your history.

I think given Covid you could make a pretty good case for wanting to shift to a more stable career path. I also wouldn't belittle your own experience thus far as not being a "career". There are many advantages of chopping and changing between different business contexts that you now have, that someone who only ever worked in 2-3 companies would not have.

You say you have no network. I would suggest reflecting a bit more on this, as I'm certain you would at least have some amicable contacts / temporary colleagues that you've made along the way, even if you wouldn't necessarily think of them as your "network" right now. Do you have a LinkedIn profile? If not, consider making one and connecting with some of the people you've worked with in the past.

Popping up a GitHub profile with a simple project that demonstrates what you think your skills are (e.g. perhaps it's a business web application that has a well-written set of unit tests, or applies a particular design pattern in a clear and logical way) could be a good compliment to your CV that employers can use to verify your expertise. If you find yourself relating more to the student crowd, then this is the sort of tack that graduates would take to prove their ability.

Here are some random things that are guaranteed to work for landing a well paid IT job.

* get your CCNA and become a junior network engineer.

* Join the military. You can join the US military without living in the US or being a US citizen and achieve citizenship in 3 years instead of 5. If you have a 4 year university degree you can start life as a management intern as a 25A. If not you can be a 25B or if you are more ambitious and not afraid of failure a 17C or 25D.

* Learn JavaScript. When I say learn it I mean actually learn it as in writing original applications, walking the DOM, avoiding frameworks. Most people paid to write JavaScript never actually learn it and they need tremendous help from frameworks, abstractions, tools and other things that slow them down and makes for slow/shitty products. Employers generally realize the incompetence associated with this technology but they have products they need to ship. If you actually learn the technology with confidence companies will hire you just for the potential of solving problems other developers refuse to accept.

Hi. Here's what you can do:

- Start a company and build product for enterprise. The amount you get paid as a company vs. as an individual is not even comparable.

- Learn to sell more, or hire someone who can, and then learn to sell. Someone who can ask for a price you would never ask without blushing, blinking, sweating. Most engineers I've seen have a problem with sales and you don't know what's valuable for clients. I was in meetings where the client ignored features we spent weeks on, and was amazed by a feature we implemented in a day. One colleague engineer who tagged along was just amazed: "From all the features, they loved that?". Sometimes the amount of engineering you spend on something and the value it has to someone are two independent variables.

- Get an attorney who'll draw your contracts and make sure your company doesn't get abused. Clauses to protect you. To make sure you get compensated for the opportunity cost of an exclusivity contract, and to make it constrained in space, time, and limited to some entities. Obviously never sign something before they read it. The contracts you're handed were probably written by people from a legal department, so it's good to run it through someone cut from the same cloth.

- Amicable relations. Always deliver. Build a reputation. Repeat customers are a thing. Recommendations are definitely a thing. This can be very profitable.

- Network. The energy it takes is considerable. To be able to positively pitch your services, build relations, follow up on enquiries, spread good vibes... Build relations, build trust... And sometimes, sometimes, you might have to do a solid to a relation in a large enterprise to get in, but when you get in, you get in. Again, this can be profitable.

- For hiring, surround yourself with people you can learn from, who can complement you. Your objective is to grow the company.

- After servicing many customers, you'll learn patterns. You can sell a product many times over.

I'm excited for you. All the best!

I think a code bootcamp will def help you