A Junior Software Engineer's Manifesto

Back

I recognise the potential hubris in writing a manifesto as a junior engineer, but I'm masochistic enough to enjoy the exercise anyway:

1. I don't have all the answers—but I will find them.

I'm not yet an expert programmer. But I learn quickly, ask good questions, break problems down, and persist until I find solutions.

2. Technologies will change, meta-skills won't.

Problem-solving, resilience, communication, adaptability, and self-learning are the foundations of my career. Coding is the cherry on top.

3. You're hiring me to solve problems.

Code is one of the tools I use to solve problems. Other tools include: domain knowledge, communication skills, enthusiasm and work-ethic.

4. User needs come first.

I'm not a luddite, I love technology too! But, I'm going to commit heresy: all technologies (including LLMs), should be judged by how well they solve user needs. Simplicity before complexity.

5. Here's things I recognise.

I'll read more code than I write. Great software is built and maintained by teams, not individuals. Engineering is more than syntax. It's requirements, maintainability, security, and performance. I don't understand all these nuances, but I approach it with a systems mindset.

The tools will differ and the landscape will shift. But the ability to think clearly, adapt to new information, communicate well and proactively solve problems won't change. That's what you're hiring me for. I'll pickup the nuances of programming along the way.