I learned the basics of HTML, CSS, and JavaScript in the past, but I have not built many substantial projects with them. I could probably refresh my knowledge enough to create a simple website within a few days, but I am unsure when it is appropriate to list these skills on my resume or apply for development jobs.
I have not used frontend frameworks yet, although I am considering React, Astro, or Angular and wondering whether I should focus on one. I also have some older introductory experience with Java, C#, SQL, Android Studio, and basic app development. My plan is to build a few simple but functional projects, possibly including one or more live websites.
How much practical experience is enough to list a language or technology honestly? Would completing a proper project or several live websites justify calling myself a full-stack developer, or would I still be better described as a junior frontend developer? I also have experience using Wix, Carrd, and WordPress, along with hobby experience in Ren'Py, modding, and rigging, though I am not pursuing game development.
2 Answers
Projects are what make the skills believable. Build something complete, put the code and a working demo where employers can review them, and be prepared to explain your choices and fix basic issues during an interview. A few projects can support applying for junior frontend roles, but simply making a website does not automatically make you full-stack. That label usually implies both frontend and backend work, including things such as server-side code, databases, APIs, authentication, and deployment. Pick one framework and learn it well enough to finish a project rather than spreading yourself across several.
A good rule is to list technologies you can reasonably discuss and use, especially when they match the job you are applying for. You do not need years of professional experience before putting HTML, CSS, JavaScript, Java, C#, or SQL on a resume, but be honest about your level. Group them as beginner, familiar, or working knowledge if that makes the distinction clearer, and tailor the list to each role.
That makes sense. My main concern is that I studied some of these technologies years ago and might struggle with interview questions or debugging, so I should probably refresh them through a project before presenting them as current skills.