What I mean by front end projects are projects that mostly consist of using HTML, CSS JavaScript and a framework. I actually like to build projects but learning Javascript is making things a bit harder for me.

spend only one hour maximum on a problem, then check solution. no matter what people say, our imagination is not beyond this unverse, so whatever you see creative has already been produced by nature or somebody else.
just try for 1 hour check solution after 100 problems, 1 may repeat, then you can enjoy, that you make it your own, after 1000 problems, you may start getting solution from what you have learn't from these many problems.
learn basics of all then start building projects.
first learn javascript , then html then css then react js. learning javascript is not huge chalenge, learn most required javascript for react and then you are good to go.

I cannot tell you what in the interview will be used, but here my recommendation:
Do not worry too much, usually in the projects (my experience) it will not be too much about complicated "coding challenges". It will be more about building complex systems in a good way.
But you still should learn and practice a lot something like coding problems, because it will still teach you a lot about solving problems with programming. The experience which you gather will be worth it, just do not always try to limit your learning to topics, which seem to be necessary and actually used.
Keep doing, if this is the path of your choice!

It really depends on the position and the scale of the company you apply to. A small company that wants you to build them a front end for a private api probably doesn't care about what data-sci their junior dev knows, ya know?

But maybe a larger company with a web-app that handles tons of data, might care a lot more about an efficient & performant app which demands some knowledge of data-sci.

If you're unsure, I would just focus on whichever you are more passionate about 👍

Learning HTML,CSS and JavaScript to learn about frontend web development. Eventually I would like to learn other technologies like mobile development and python. I just want to get my foot in the door and becoming a web developer is a bit "easier".

Wow! Now this is very helpful. I'll definitely look into learning more about Wordpress. And that is exactly why I can't wait to start working. I think learning on the job WHILE getting paid is a win-win situation. Doesn't matter what job I start with. As long as someone is willing to give me a chance to learn and grow, I'll be happy.

The most valuable things to know as a frontend engineer is not writing algorithms.

Focus on:

• Creating SEO friendly pages with semantic markup
• Create performant pages (load fast, no layout shifts, no heavy JS load)
• Maintain accessibility (again, semantic markup - no div-itis)

Those three points really inter-depend on eachother. To have an accessible and fast page gives you a SEO boost as well as good and clean markup. And having a performant website both user and SEO wise makes it much more valuable for your client.

So I personally would recommend working on "real website projects", not algorithms. But as others noted, it highly depends on where you want to apply.

Thats good you found something you enjoy doing. So far I'm enjoying learning web development even though I face some challenges.

Is PM short for project manager ?

Learning is something you will always be doing as a programmer. Many forget about having fun. This path is not for everyone, it is for those who really like it and enjoy it. That said, I think that you are feeling overwhelmed and that is normal at your stage, the reality is that tech is continously evolving and getting more complex, and every year there is more to learn than the previews one. My suggestion is to not put so much pressure in your timelines, this is something that is going to take time, you need to know that reality. Don't fall into the trap of wishful thinking.

The pressure on your timelines will prevent you from building a strong foundation. Is very important to learn very well A to go to B to go to C and so on.. But that takes time. At the same time if this is your thing it can be an enjoyable experience.

Don't focus to much on algorithms. Yes, do one of them from time to time. I recommend been active on Stack Overflow, studying fundamentals of HTML, CSS and when you feel strong with those, study the fundamentals of JS and start using frameworks. Also play around with them and YES build stuff.

I wrote a fun coding JS session here in dev.to.. Explained in detail, I would say is for begginers.. check it dev.to/gass/fun-coding-start-multi...

I think, build logic is good for you life and dessision, but for a career build a real project is good

I once worked with a front-end team that had to implement some kind of google drive, so basically displaying a filesystem. We noticed that we couldn't handle more than 7 level of directory.

Instead of implementing a recursive tree structure, "someone" had implemented a list< list< list< list< list< list< list< file>>>>>>>...

So don't worry, you will never ever had to implement a bubble sort algorithm in your career. But for me, minimum skills in datastructure, algorithm and splitting problems is part of basic knowledge any developper should have, or should acquire.

Okay cool. I'll look into that as well.

I always ask the mechanic to parallel park.

If they can't manage that, they have no business playing with my nuts.

I've spent quite a lot time on solving problems, not only interview problems but also competitive programming problems (which is much harder). The result is I can easily pass coding challenges in most of companies and secure the position but later I feel myself far behind my colleagues in the actual job and the thing is I've never used any of my problem solving skills in the job :))). My suggestion is focusing on building project and find a company that values your skills.