I'm a computer science graduate. Most of my college subjects are about algorithms, data structures, database systems, and some basic maths. So, they are close to what we call backend-engineering, right? and that's why I am a backend-engineer at first.

Being a backend-engineer could be awkward if you applying for a job as a web developer. Let's say the backend-engineers' jobs are rare compared to web developers' jobs and left you with no choices. The employer expects you could make a complete website. That's why at least you need a basic of frontend stack (HTML+CSS+JS) in order for your backend works to be 'visible' and functional. Another reason to have frontend basic is useful when you do a side-job for creating another website that you're capable to make while you're a backend-developer at your main job.

But learning frontend stack especially CSS is a bit more frustrating for a backend-developer because maybe you're lack of creativity for UI/UX or the CSS itself never stays in your head 😄
Somehow some people are good at designing something using a graphic editor (e.g Adobe Photoshop/Illustrator, Corel Draw, etc) but they have no idea how to slice them perfectly into HTML and CSS, and also the responsive design may hit you even harder 😆

That's why there are CSS frameworks/UI-kits for you (the backend-developers...) to use such as Bootstrap, Foundation, Bulma, or even Tailwind to help you rapidly create UI for your apps. I could say backend-engineer + these CSS frameworks still makes you as Fullstack Developer, am I right? But here comes when you applying for a full-stack developers' jobs, you may be considered not good in the frontend. That's a little bit bitter for you. Your journey as a backend-developer is not completed yet, and yet this frontend thing still haunt you along the way 😆

So, Is it okay for not to be great at FrontEnd as a Full-Stack Developer?