Landed my dream job!

First, this is not a post about a first dev job. This is actually my 5th job, in 2.5 years.

I started my new career (at 37 years old) working small contract with startups, often just for prototypes. There were challenges along the way, but overall the apps were never overly complicated. My first two contracts were in front-end (although the first one I had to have some sort of backend, so I used firebase). Then by my third contract, I had learned backend too, so I was working full stack.

Once those small contracts ran out and I needed a more stable income, I started applying to more long term jobs. I ended up somehow landing a job at Autodesk. That was a huge change! I went from building small web apps to working on super large projects, surrounded by very experienced software engineers. I had to quickly learn to work in an object-oriented way, to write tests, write documentation, etc. It’s been a very humbling experience, sometimes too humbling. On many occasions, my self-confidence took big hits and I never felt quite good enough. But somehow I always found a way.
After a year and a half there, I realized that the problems I was facing were not just from lack of knowledge, but not being in the right environment. The company culture was good… but it was not right for me.

I started applying to other jobs. By that point I figured I was ready for something beyond the entry-level jobs. That turned out to be an uphill battle. I faced a lot of rejection, some of which really stung. I started thinking about lowering my expectations, but I couldn’t really afford a pay cut either… so I felt stuck.
At some points, I stopped applying, and recently started again. Once again I got some rejections but eventually got lucky. In fact, I ended up with two job offers. The first one was very good. It was a full stack job, good pay and benefits, and the people were friendly. But then I went to another interview and fell in love at first sight with the job. It was for an open-source project with positive social impact, working with really cool people, for a boss who is completely willing to trust his employees. It all seemed so perfect, but I was having doubts about whether they would hire me to be in charge of the backend.
Well… they did hire me!!
It is really daunting to have so much responsibility, but also very exciting!!
I haven’t started yet, but that will give me some time to review some skills that have gotten rusty.

So overall, if I was to give advice to those starting out, I would say…

  • Network. It doesn’t have to be showing up to official networking events, but get to know people in your local tech community if you can. Volunteer for stuff, show up to events, organize events if you feel up to it. Knowing people will open a lot of doors!

  • Know your strengths and weaknesses. Do not apologize for your lack of formal education: be aware of the limitations it has, but also think about how it has its advantages. If you are self-taught, you have a drive and resourcefulness that is really valuable.

  • Don’t be afraid of saying “I don’t know”. Whether it is during an interview or at a job, remember that nobody knows everything. I cannot count the number of times I heard “I don’t know” by people who have many degrees and years of experience.

  • Figure out what you want in a job. You might move around a lot in the beginning of your career. Some jobs will be better than others, but always use them as a learning experience to figure out what you want and don’t want out of a job. Then don’t be afraid to go for what you want. For me, it was all a question of having a purpose, feeling my impact and being constantly challenged.

  • Don’t take rejection too hard. Not everyone will see your potential or understand your value. Just make sure that you do.

  • Even if you don’t have all the requirements for a job, apply anyways. Employers don’t usually expect to get everything, but if you are a good fit, you can fill in the gaps later. For my job at Autodesk, I met NONE of the requirements. Seriously. I think employers often mix up the terms “minimum requirements” and “over-the-top wish list” :wink:

Wow. that was long. I will stop now. Honestly, my brain is really fuzzy right now, so if any parts don’t make sense, sorry!

18 Likes

Congratulations! Thank you for sharing your experience with us all.

None of the requirements? Woa this is very surprising and encouraging as well. Sometimes I don’t even bother when I see that I don’t meet 2 or 3 of the requirements, after seeing this, I will reconsider it.

Thanks for sharing your story and congrats.

This is awesome!!! Congrats and thanks for the advice!!!

@Gilbert1391 Ive heard the same thing, to apply anyways and I was always so hesitant, it just seems wrong to apply for a job asking for skills I dont have! But time and again I hear this, so there has to be truth to it. Some of it is HR is putting out the ad and just using whatever skills they see on other listings, even if they have nothing to do with the actual job, another part of it is if they like you and want to work with you, they may be inspired to take a chance.

My first job offer was for a DevOps job…all I knew about DevOps was what I googled two days before the interview! lol I didnt end up taking the job, but yeah…its advice worth taking!

You started a new career at 37 and here I was stressing Im getting old and every day I dont have a coding job im stressin at 27. Inspiring. Congrats and Im glad you were able to find a job thats fulfilling!

Despite popular belief, life does not end a 30. :laughing:

1 Like

LIES (im delusional here, no offense to anyone. Just a way of motivating myself :sweat_smile:)

And I’m at 29. we’re never too late. :slight_smile:

Some great advice here. My experience at interview is that a good attitude and a willingness to learn is more important than any specific technology.

Also, companies usually put their whole stack in the job advert, and recruiters will look for people based on this. But in practice, most developers will either work on the front or the back end.

1 Like