#SoftwareDevelopmentSpecialization #CareerAdvice #FrontEnd #BackEnd #DevOps
Hey fellow software developers! 🖥️ How did you decide on your specialization within software development? 🤔
I remember when I was a recent grad, I was in the same boat as you are now. It can be overwhelming to choose between front-end, back-end, or even devOps engineering without much real-world experience. Here are a few tips that might help you in making this decision:
– Start with what interests you the most and where you see yourself in the future.
– Consider taking on different projects or internships in each specialization to get a feel for what you enjoy most.
– Keep in mind that it’s okay to start in one role and transition to another as you gain more experience.
For me personally, I started with front-end development because I enjoyed the creative aspect of it. However, as I gained more experience, I found myself leaning towards full-stack development. It’s all about exploring your options and finding what suits you best. Don’t be afraid to try different roles and see what clicks! 💡
How about you? How did you decide on your specialization within software development? Share your experiences and insights below! 👩💻👨💻 #SoftwareDevelopment #CareerGrowth
I took the first job I could with a decent salary and benefits (non-traditional college grad starting later) and did what was asked. Very few places will be purely backend. You wear many hats at different times and learn through experience. I am a full stack developer not out of a conscious decision to be but because you have to do a lot of different things for different projects and you trial and error and ask for help and learn and learn and learn. Focus on being language agnostic and being able to learn whatever you need to in order to get the next project done. In 3-5 years you will be amazed at how much you know and can reuse and reapply with some rework to so many things! Most of all, have fun learning whatever is in front of you. (Devops is it’s own beast and if unsure the only one i would shy away from outside of writing your own docket and kuberneties files but I probably feel that way because I have the least experience in that. Like there were always project teams and the devops team)
**Is it possible to fully commit without getting experience?**
Yes. You aren’t locked into the role you pick for your first job, you can always change later on down the road.
Example
* After I graduated with my 1st bachelors I was a new grad Area Manager at Amazon
* After a few months of being an Area Manager I internally transferred over to a low code software role at Amazon
* I’m currently working on switching over as a more back end focused software engineer
**How you guys decided when you first start?**
I select whatever I’m interested in and whatever I can get at the time, then later on switch over to a role that I want more.
**Note**
Not only the role, but the company and team change your opinion on the role. That’s all to say that for example if you go with back end engineer, you might not like it at one company/or team but like it on at another company/or on another team.
**Edit – My exepreince**
When I got my first job after graduating with my 1st bachelors degree it was primary focused on getting any job that’d pay me.
*Note: I selected Amazon over other companies because I had already worked at Amazon while in college as a warehouse associate, and I figured Amazon was a good option with being able to move around to other roles*
When I got my first tech role it was primary focused on getting any tech role that met my minimum pay expectations and that would get my foot into the door for the tech industry.
One more thing for a new grad: everyone in software has imposter syndrome. No matter how many successful projects no matter what you learn and what you know, no matter how confident someone appears or in control. Everyone has imposter syndrome and is sure they are not going to be able to do the next project or figure it out and everyone will know. Don’t let it get you down. It’s everyone. Even if they never say it.
try to determine what you want to do with some side projects of your own. yes, figure out how to do any of the roles, locally.
no one wants to hire someone who isn’t sure. Your preference can change later, of course, but you have to convince someone of your own passion to get hired.
I went up and down the stack from front-end/mobile to Devops and settled on Automation/SDET after 10 or so years and been there ever since.
In 5 more years who knows where I’ll be but I’ll at least know I’ll be enjoying it
I just went after the most interesting problems and found them in those areas for me
My point is you find out by trying diff things in your career and you’ll naturally gravitate towards what you like.
This also means trying out things you don’t like. It will make you a stronger engineer in the end
To carve out the career you want, you can never settle or become complacent
What I can get hired in. I got hired in DevOps and transitioned into databases that I learned on the job. I avoided frontend since it pays the least and I hate JavaScript. Apply to all the crap you’re willing to do that you’re vaguely qualified for.
Whatever you get hired for.
I did 6 internships in undergrad and worked with a few research groups as well during that time. My first two internships (same company, diff parts of the stack) were great, my later ones I chose topics/stacks I was familiar with but wasn’t sure if I liked enough. Confirmed it, those were ones I didn’t want to work with.
After graduating I really only focused on the one industry I’d really enjoyed so far. I liked the others well enough but knew I’d get tired of it within a few years. Ended up finding a position that’s pretty close to perfect for me, both in topic/specialty and culture.
I would judge based on other factors for new grad. Like company standing, pay, benefits, long term trajectory… etc.