What do Software Engineers Really Do Day-to-Day?

When you're just starting out, like as a junior dev, you'll likely be focused on learning one tech stack. As you gain experience, you'll start tackling multiple stacks and eventually shift to higher-level design and management. A big part of the job is understanding what stakeholders truly want versus what they say they need, so being a good communicator is key!

Honestly, job postings can be pretty misleading. They often list a ton of tech stacks but in reality, most companies don’t use everything listed. For instance, I had to pick up Kafka and CircleCI at my last job, which I'd never touched before! But most of the time, you're tweaking and maintaining existing code rather than starting from scratch. If you hit a snag, just reach out to your colleagues for help—they're usually happy to share their experiences. It’s all about learning and adapting as you go!

Job descriptions are often just wish lists written by HR. In practice, you might spend around 30-40% of your time actually coding. A lot of your time is just reading code, debugging, writing solutions to problems, and reviewing what others have done. Don't let those intimidating job descriptions scare you—they're typically looking for the perfect candidate, not the one who has to hit the ground running without any training.

In my experience, software engineers spend a good part of their day fixing bugs! And while we do have to know a lot of tech stacks, it's not like we're using every single one every day. The tech stacks you work with can vary widely depending on the project demands, but don’t stress about it—focus on building strong fundamentals and problem-solving skills!

Here’s the secret—it’s often more about problem solving than anything else. You might get requests like "we need a button to export data," and then it’s your job to figure out how to implement that. Sure, you’ll be learning and using new technologies, but you learn a lot on the job just by diving in and figuring things out as you go.