One Woman in Tech’s Software Engineering Roadmap

Software engineer


Joana Carneiro, a passionate Software Engineer shares her roadmap that has helped her succeed in her tech career. She states ‘What if there was a plan, a roadmap, that we could consult at any point and see where we are and where to go?’ A very helpful article and a brilliant step by step approach.

The software world is always changing.

There are new trends, coming in everyday. Old trends that have now better approaches. New problems to be solved. Old problems, never solved, that now have the right tech to be answered. Old tech that now brings the answers. New buzzwords. Old buzzwords. Languages, paradigms, styles, frameworks, architectures, patterns, methodologies, principles…. Do you feel your brain already? I sure do! With all this knowledge that we, as Software Engineers, are to keep up with! Keep and update at all times! Making sure that we are really craftsman of the software!

Software engineer

What if there was a plan, a roadmap, that we could consult at any point and see where we are and where to go? As professionals to have a systematic view on a step by step approach on how to evolve and what is worth tackling?

This is the intention of this article — to share here, from my experience as a female in software engineering, on what is worth learning and take hold of. With a roadmap structure, step by step approach. Would also love to hear your insight on this and really start the discussion.

As a very dear friend once told me “Learn concepts and not languages”. And I very much agree with that! So my perspective is really to invest heavily into the concepts, because those will not go anywhere as the time goes by. Do you know what is functional programming? That is knowledge that will go nowhere over time. Then learn how to do that in a specific language.

So the proposed structure goes from more abstract concepts into the more tech linked ones.

With the safeguard, that more details is never enough! Note, that the first learning path that I saw with lots of details, that really caught my eye was this one https://github.com/kamranahmedse/developer-roadmap! Check it out! Great resource, where I definitely keep an eye on and take advantage of it for defining my own path as I share here.


As a Software Engineers, we need to cover lots of areas of expertise.

Not only we need to master the technologies that we are developing with, but also the infrastructure where are solutions are running at. And last but not least, a given set of soft skills can really can make our life easier. So I organize the path into 3 sections:

  • Development Skills
  • Infrastructure Skills
  • Soft Skills

Development Skills

Find bellow the path defined for enhancing my development skills, that I try to keep updated and refreshed. Again this is organised, from more conceptual aspects like patters and methodologies, to more practical aspects such as specific programming languages and APIs implementations.

Boxes in yellow are the aspects that I am refreshing right now. For example, I am reading the Blue Bible on it. For Design Patterns, I am going deeper into Microservices ones, so also reading a book on it. Since that is the architecture that I am currently going for.

Software engineer

Infrastructure Skills

In terms, of infrastructure, for me, it is important as a Software Engineer to understand the infrastructure, so that I can take advantage of it, and make an informed decision when implementing a given solutions.

For example, if a given software is being deployed into Microsoft Azure, it is important to know that if in my Java Class I create a new document, I will be consuming the 5GB of available file system space, and that maybe instead I should consider Azure Blob Storage as an option to solve that problem.

So, I leave here a bit, of what I see as overall topics that I keep under my radar.

Software engineer

Soft Skills

Much could be said about this topic, but overall this is a topic very dear to my heart. Because having knowledge is not all there is for being a successful Software Engineer, that brings value into the table.

It would be great if you are able to apply all your knowledge at every given situation. But then, it comes this day, with a Production environment issue with the Project Manager calling you every 5 minutes to check on it, and you already feeling a small drop of sweat in your neck with the stress building up. Wouldn’t it be great, at this point, for you to still be at your A game?

Wouldn’t it be awesome, if you are able to transmite all that you have gathered as experience over the years, to your fellow colleagues, and keep a great collaborative environment, even if there was this situation with a co-worker that is nagging you a bit?

And how about being in a meeting with the customer, and really be able to influence the decision of the most sceptical of the IT managers, towards what you believe really will bring the value to their company?

So, this is where this proposal of steps in my roadmap have entered. As a way, not to forget that soft skills are as important.

So, I will definitely go deeper into this in a later article, but I see this in 3 sections:

Me: tools for self regulation of emotions (stress, anger..), so that I can be in a state that suits me. For example, going into a meeting with a calm state. See what helps you. Might be as simple as thinking about your kid at home and the last time he gave you a big hug.

Team: communication is paramount, so being able to practice non violent communication for example, focused on the facts, and being open to a different point of view on the other side.

Project/Customer: Influence techniques, here are very useful. As for in a positive way to transmit a given view, but also actively listening to the other part. Here, the creation of rapport, is really important.

Software engineer


There are several ways to learn for any given subject. But all depends on what is your way to learn and what works for you! Also some subjects might benefit from a more hands on approach, others from a more conceptual form! So in the next articles I will explore in more details the above areas and what resources would be a good help in its journey to learn, but for now here it is a list of possible approaches to learning.

Read a book

There is in now way better for the most abstract concepts. Why? Because you will find in books authors with proofs given in the area,

Do a course

Sometimes there is no better way than to find an accredited professor with proofs given in a certain area and learn in a formal way. Back to school mode! There are great technical people out there launching updated courses on a great variety of areas! Worth checking and this is less time consuming then going for it yourself or even reading a book! As a transversal hint to all the presented resources is that keep a critical spirit to what is presented to you!

Follow Someone

There are also great resources that people, working in the field, having the same issues as you, put out there! Videos, articles, podcasts, tutorials! The amazing world of the internet! Find your subjects of interest, find your persons of interest and start to check out what they put out there! This might be one of the best ways to learn! Just make sure whomever you follow has a solid background, and you are all set to be up to date!

Join an open source project

Participate on an open source project is a great way to put your skills to practice, upscale them and also contribute into the community. Also you will have a showcase of what are your skills to the outside world!

Some examples of good open source projects for beginners


Develop your own project

Just think about something that really interests you, or might came in hand. My last project was making a Pokémon deck API! What a fun time! Other alternative is of course do a quick search and many ideas will pop up!

Do a certification

Sometimes having an exam scheduled and 2 pages of topics you must master for it, is a good and structured way to go deeper into a given subject. It can be argued if a certification really gives you the tools to work on a given technology, but there are areas where it is a good way to start on it.

Find a mentor or be a mentor

This for me is one of my favorite ways to keep up my continuous learning and improvement! Really making use of the work environment for knowledge share! Either being a mentor, that really makes you step up your game, or having someone that can guide you in your first steps! This can also work by just finding a colleague that is on the same path as you, and so instead of you and your head find the best resources now there are 2! Also it is so much more fun!


SheCanCode caught up with Nikita Clarke from Experian to find out about how she landed her role, important skills needed for a career in tech,...
Katie Hawcutt began working as a software engineer for self-employment tech specialist, wise, after over ten years working in music. In the hopes of helping...
Here are five things that you should do if you want to grow as a software engineer.
In this piece, Erin Gray, Scrum Master, Tecknuovo, takes a look at getting into software engineering and gives her tips for potential women entering the...