Getting a job in tech part 3: GitHub and articles

Carolina Cobo
3 min readFeb 28, 2022


image source: stories

Having a well-rounded profile will take you a long way. Today I wanted to cover the new option for a personalised Readme file.

Bringing attention to your code is important as well if some potential employers might be looking at your work, but you will definitely leave an impression if your profile is more personalised.

I think there’s no one better to explain how to do it than GitHub themselves, so here’s the documentation on how to change your home Readme file.

Said that there are other tweaks you can add that will make it stand out.


That’s right, you can add GIFs. Here’s my little cute one greeting whoever visits my page, the code for how to use it is below.

<img src=”" width=”90px”>


There are badges for alot of things, languages, frameworks, editors, etc. and also in different styles. Here are some links to different sources where you can find them:


If for your social media instead of using badges you prefer to use icons, you can create them by adding them to a folder, here you have one to make things easy for you.

The code to include this in your Readme:

<a href=”"><img align=”left” src=”" alt=”icon | LinkedIn” width=”21px”/></a>

Stats card

It’s a good way to summarise all the contributions you’ve done in a really visual way, you can change colours and personalise it as well.

To add it use the code below:

![YOUR-USERNAME’s GitHub stats](

Make sure to change the GitHub username to your GitHub username.

You can change the themes to any other you like. Here’s the documentation so you can pick any other style you might like.


For the rest of the body you can use normal markdown. Here’s the guide from the official site in case you want it handy as well.

Here’s mine as usual if you want to take a look:

Bonus: start writing

This is something that not everyone enjoys and it’s really not necessary to do but I really enjoy being able to share some of my knowledge or experiences with other people that might be helpful.

Writing is probably the best way to do it (I’m also always available on LinkedIn or my email if you need any help). But clearly writing it’s easier to have a bigger reach.

How to start?

You might feel as I felt thinking I had no idea of what to write about, so for me to start it’s been either problem I faced such as understanding what was the difference between em and rem or how I learnt not to use -f in my commits on Git.

But also things I knew from my previous role as a recruiter, such as how exactly recruiters use LinkedIn to find people and how to improve your profile

And I can tell you that have an endless list of other things I didn’t know and had to learn that I want to write about. But I wanted to start sharing my journey to become a software developer and how my first month as one was.

So I’m sure you have a lot of interesting ideas, problems or experiences that you could share with other people, and writing about them is probably the best way to get a better reach/

Thanks for reading, I really appreciate your time! 🎉 If you need any help please reach out!

Next week I’ll be sharing another post about how to prepare for interviews, so please subscribe so you will receive it on your email when it’s out!

If you have any questions feel free to drop me a message on LinkedIn or send me an email. 😊

Have a nice day!



Carolina Cobo

Frontend Software Engineer @ Genesys | Career switcher