I’ve fixed the CV link, not sure what happened there?!?
Yep, working now.
Again the loader and hidden header seems to be adding confusion to the page your right
Yeah, just remember what the purpose of this page is. It isn’t to show off your coding skill - do that in your projects. The purpose of the portfolio is to make it as easy as possible to find out about you in as little time as possible.
Your resume - holy crap! 4 pages? I think 2 pages is too long for most people. Try to get it down to 1 page. Like with the portfolio, you want to make it as easy as possible to find the information. Filling it with fluff and irrelevant information makes it more difficult.
Your summary should be one or two lines, just enough to tell them what you are looking for. You can be more descriptive in a cover letter - this is a data sheet.
The skills section is OK - though you might save some space by making it three columns. And don’t include things you are currently studying - either include them or don’t. Don’t list Microsoft Office - they assume you can use basic Word and Excel.
Have less information in the portfolio section, just the basics, maybe just titles and links.
In Employment, any job that is not relevant to web dev should be one liners. They really don’t care about all the details - don’t waste their time. If you think there is some valuable skill you learned that applies, you can mention it in a cover letter or interviews.
All those education entries should be one line, and drop anything that isn’t tertiary level. I would combine the two degrees into one line. I would want to include them because they show you can finish something, and the fact that they are a scientific field is helpful, but beyond that they just won’t care.
You don’t need to tell them that references are available on request - they know.
You don’t need a link to an unformatted version.
For that matter, this should be pdf. If it extremely portable, everyone can open it, and they can’t easily change it. I think it’s good to have Word and plain text versions because sometimes people ask for them, but you don’t need to waste space with this here.
In short, pare it down significantly. There is no reason for a junior developer to have more than 1 page. I should be able to scan your page in 5 seconds and know who you are. Every detail that I don’t care about (at least 80% of what you have here) is a waste of my valuable attention. The hirer is looking for an excuse to skip yours and move onto the rest of the pile - don’t give it to them.
As far as your projects…
I don’t have time to dig into the code too much, but what I see looks OK.
I would want you to keep building apps, keep building increasingly complex apps. Things like shopping list and rps are fine if you have nothing else, but really, they’ve seen thousands of those.
I don’t see anything there with a backend. I know you’re calling yourself frontend, but often they expect at least a touch of backend work. And that would also make it possible to build more complex apps. If you’re working through the FCC material, the “Back End Development and APIs” section will give you the basics.
So, I would say that it is a good start, but you’ll want to build increasingly complex things. I think you also want to get away from the cookie-cutter apps, the ones that everyone does. Try to think up some original ideas. Or maybe it doesn’t need to be original, just not one of the 10 apps that every beginner puts in their portfolio. It doesn’t even have to be a great idea - they are interested in you as a coder, not an “idea guy”.
Or maybe even spruce it up. What about a shopping app with different columns for different types stores? Or that persists in local storage? Or that persists in something like firebase? Or that has a map that shows the nearest grocery stores? Or that has more animation, etc. This is where you can show off - if done with good taste.
