4 ms·

You have to pick a specialty and get certified. Certificates are the only way you'll be able to break into the field you want to pursue. They don't guarantee an

You have to pick a specialty and get certified. Certificates are the only way you'll be able to break into the field you want to pursue. They don't guarantee anything but for a hiring manager, they at least signal that the person has received training. Additionally, I would volunteer at work on projects that are specially useful towards your career path. Going forward you'll need to start looking for jobs that will move you forward on what you want to specialize in. It won't be easy but eventually, you'll get something. Learn from every interview and get a better understanding of what employers are looking for. Also. don't pick a specialty just because it pays well. Money is nice but remember you'll have to do your job for the rest of your career. Money will not make up for the mental stress of doing a job you hate.

scarface_74 2y ago
I have 6 AWS certifications. Certifications have always been easy to memorize enough to pass a multiple choice test and no one who hires thinks because you have a certification means you are competent. Also I have been working for almost 30 years. My first “specialty” was writing C and Fortran for mainframes. Being in tech is all about pivoting
- mech422 2y ago
  >>Being in tech is all about pivoting And remembering stuff 30 years later so you can be one of the last 10 people left that remember it. I figure COBOL should make a nice lil side hustle when I retire :-P
- Shaun0 2y ago
  I'm curious - how do you maintain the energy to learn new technologies while keeping your existing skills sharp? Don't you ever feel burnout or fatigue from the constant need to stay current? Would love to hear your strategies for sustainable learning in this field.
  - scarface_74 2y ago
    > how do you maintain the energy to learn new technologies while keeping your existing skills sharp? I don’t keep my existing skills sharp. This was in response to another comment. But should give a little context. https://news.ycombinator.com/item?id=42704502 https://news.ycombinator.com/item?id=42704502 By 2018, I stopped trying to be a “full stack developer”. I gave up on keeping up with what was going on the front end and start learning AWS. I was the first technical hire by a then new CTO who was bringing development in house from a third party consulting company. I jumped on every AWS related initiative who threw at me and started leading them by doing proof of concepts and working with teams to establish patterns and processes. Stepping back for a second, I got my first AWS certification without ever opening the console and my first six within the first year of opening the console. The purpose of them were merely a guided learning path so I would know what I didn’t know. Between 2018 and 2020, I got a lot of hands on experience combining development + AWS. A full time position working at AWS in the Professional Services (consulting) department fell into my lap in 2020. https://news.ycombinator.com/item?id=38474212 https://news.ycombinator.com/item?id=38474212 While there, slowly I started being put on projects where I was over the DevOps “work stream” showing clients how to automate builds and deployments on AWS. A work stream is basically a smaller project in a larger implementation. I was a mid level (L5) “Cloud Application Architect” supposedly specializing in cloud architecture + application development. But it soon became DevOps + a few Python scripts. That means I started doing even less development and became hyper focused on one or two specific niches I worked at a shit show of a third party cloud consulting company for a year doing the same thing and now I work as a “staff software architect” at a much better third party consulting company. I come into a project right after sales and validate the business requirements, current state, desired future state and then work with the client to propose a high level technical design and implementation plan. We as a company get paid for giving the client an “assessment”. They can either take it and run with it or have us do the work. At this phase, I have to have a broad enough understanding of the AWS ecosystem to know what questions to ask and how to implement what they need in broad strokes and ask the subject matter experts at our company in areas that are not my strong points. In other words, I don’t need to be the best developer, data analysis, cloud engineer, etc. I just have to know the specialties well enough to talk the talk. Part of the assessment is breaking down the projects into “work streams” - sub projects based on specialties. If the client wants us to do the work, I then turn into a tech lead and assign the work streams to “architects” who are the hands on specialists. I for the most part defer to their technical expertise and they are responsible for leading their work streams and working with the client to make sure their work stream is done. My job is to coordinate the architects, client, sales and project managers. My hands on skills may not be as sharp as they were. But I spend my down time learning and staying abreast of industry trends. I use getting certifications mostly as a guided curriculum to force me to keep learning. It’s not for resume building. The next logical question is what happens if I need to work as a hands on software developer or God forbid a “cloud engineer”? I have a year’s worth of expenses in the bank aside from retirement savings to give me the runway to get interview ready.
Shaun0 2y ago
I appreciate your advice about certification and specialization. However, from my experience in software engineering, I've observed that certificates seem to carry less weight compared to previous employers and actual work experience. Companies tend to focus more on demonstrated skills and project history. Nevertheless, thank you for sharing your perspective!

scarface_74 2y ago

I have 6 AWS certifications. Certifications have always been easy to memorize enough to pass a multiple choice test and no one who hires thinks because you have a certification means you are competent. Also I have been working for almost 30 years. My first “specialty” was writing C and Fortran for mainframes. Being in tech is all about pivoting

mech422 2y ago
>>Being in tech is all about pivoting And remembering stuff 30 years later so you can be one of the last 10 people left that remember it. I figure COBOL should make a nice lil side hustle when I retire :-P
Shaun0 2y ago
I'm curious - how do you maintain the energy to learn new technologies while keeping your existing skills sharp? Don't you ever feel burnout or fatigue from the constant need to stay current? Would love to hear your strategies for sustainable learning in this field.
- scarface_74 2y ago
  > how do you maintain the energy to learn new technologies while keeping your existing skills sharp? I don’t keep my existing skills sharp. This was in response to another comment. But should give a little context. https://news.ycombinator.com/item?id=42704502 https://news.ycombinator.com/item?id=42704502 By 2018, I stopped trying to be a “full stack developer”. I gave up on keeping up with what was going on the front end and start learning AWS. I was the first technical hire by a then new CTO who was bringing development in house from a third party consulting company. I jumped on every AWS related initiative who threw at me and started leading them by doing proof of concepts and working with teams to establish patterns and processes. Stepping back for a second, I got my first AWS certification without ever opening the console and my first six within the first year of opening the console. The purpose of them were merely a guided learning path so I would know what I didn’t know. Between 2018 and 2020, I got a lot of hands on experience combining development + AWS. A full time position working at AWS in the Professional Services (consulting) department fell into my lap in 2020. https://news.ycombinator.com/item?id=38474212 https://news.ycombinator.com/item?id=38474212 While there, slowly I started being put on projects where I was over the DevOps “work stream” showing clients how to automate builds and deployments on AWS. A work stream is basically a smaller project in a larger implementation. I was a mid level (L5) “Cloud Application Architect” supposedly specializing in cloud architecture + application development. But it soon became DevOps + a few Python scripts. That means I started doing even less development and became hyper focused on one or two specific niches I worked at a shit show of a third party cloud consulting company for a year doing the same thing and now I work as a “staff software architect” at a much better third party consulting company. I come into a project right after sales and validate the business requirements, current state, desired future state and then work with the client to propose a high level technical design and implementation plan. We as a company get paid for giving the client an “assessment”. They can either take it and run with it or have us do the work. At this phase, I have to have a broad enough understanding of the AWS ecosystem to know what questions to ask and how to implement what they need in broad strokes and ask the subject matter experts at our company in areas that are not my strong points. In other words, I don’t need to be the best developer, data analysis, cloud engineer, etc. I just have to know the specialties well enough to talk the talk. Part of the assessment is breaking down the projects into “work streams” - sub projects based on specialties. If the client wants us to do the work, I then turn into a tech lead and assign the work streams to “architects” who are the hands on specialists. I for the most part defer to their technical expertise and they are responsible for leading their work streams and working with the client to make sure their work stream is done. My job is to coordinate the architects, client, sales and project managers. My hands on skills may not be as sharp as they were. But I spend my down time learning and staying abreast of industry trends. I use getting certifications mostly as a guided curriculum to force me to keep learning. It’s not for resume building. The next logical question is what happens if I need to work as a hands on software developer or God forbid a “cloud engineer”? I have a year’s worth of expenses in the bank aside from retirement savings to give me the runway to get interview ready.

Shaun0 2y ago

I appreciate your advice about certification and specialization. However, from my experience in software engineering, I've observed that certificates seem to carry less weight compared to previous employers and actual work experience. Companies tend to focus more on demonstrated skills and project history. Nevertheless, thank you for sharing your perspective!