Can't speak for your country, but when I look at entry level job candidates, I look for people that have a personal project and passion. Portfolios are good, bu

Can't speak for your country, but when I look at entry level job candidates, I look for people that have a personal project and passion. Portfolios are good, but I like adding people that can show they dabbled at home, even if it's a personal file server, or game server. Full CS people probably have a leg up on you, but it's not unsurmountable. Many full CS candidates I've seen only have education portfolios and no personal projects. Again here, I found people who do full stack work on their own projects are easier to train and bring on board. Your milage will vary -- most of what I said above means nothing if your resume is only read by a computer. So my advise is maintain a personal project or three -- even small ones. Don't go too wide on languages, focus on 1-2 main languages and go deeper. It's easier to side step to a new language later (most of our new hires don't know Typescript, sometimes only barely JavaScript, but if they know ably programming language well, they tend to pass our open-internet code challenges)