I learned the basics of HTML, CSS, and JavaScript a while ago, but I never built anything substantial with them. I could probably refresh my skills quickly enough to make a simple website, but I'm unsure what level of experience is enough to list these technologies on my resume or use them to pursue a job.
I'm mainly interested in frontend development. Should I focus on one framework, such as React, Astro, or Angular, or learn more than one? I also have some earlier exposure to Java, C#, SQL, Android Studio, and .NET, although my projects were basic and I'm not sure how much of that knowledge I still retain.
My plan is to build a few simple but functional projects, possibly including a live website. Would that be enough to describe myself as a full-stack developer, or should I use a more specific title? I also have experience using Wix, Carrd, and WordPress, plus some hobby experience with Ren'Py, modding, and rigging, though I'm primarily aiming for web development. How should I decide what belongs on my resume, and how can I prepare for interviews when my practical experience is limited?
2 Answers
Tailor your resume to each position. Include older experience if it is relevant, but label your skill level honestly, such as familiar, beginner, or project experience. Coursework in Java, C#, SQL, Android, and .NET can be listed in an education or projects section, especially if you can describe what you built and what you learned.
A good test is whether you could complete a small task without following a tutorial line by line and explain your decisions during an interview. If you’re worried about forgetting things, rebuild one project from scratch and keep notes on the parts you had to look up. That process will also give you something concrete to discuss with employers.
List technologies you can reasonably discuss and use in the type of job you’re applying for. You don’t need to be an expert before adding HTML, CSS, or JavaScript, but you should be able to explain the basics and demonstrate them in a project. It’s better to show a small, finished application with readable code than to list a huge collection of tools you barely remember.
For frontend work, build a few complete projects first, then choose one framework based on the jobs you want. React is often a practical starting point because there are many roles and learning resources, but the important part is understanding JavaScript, accessibility, responsive design, version control, and how to deploy a site. Only call yourself full-stack if you can also build and explain the backend, database, authentication, and deployment—not merely because you made several live pages.
That makes sense. I found the outlines for my old programming courses, which covered introductory and intermediate Java, HTML and CSS, JavaScript and jQuery, C#, .NET, SQL, ASP.NET, and Android development. I’m just concerned that I won’t remember enough to answer interview questions or fix problems without revisiting the material.