Frontend internships: a link beats a description

What the job is made of

• Layout that survives contact with real content — long names, empty states, a narrow phone
• Accessibility as a default: keyboard navigation, focus states, labels that exist
• Performance awareness, because the interface is judged on how it feels before what it does
• Managing state without the app becoming impossible to reason about
• Working from a design and knowing which details are load-bearing

Deploy it, even if it is small

An unlinked project is an assertion. A deployed one is evidence, and free hosting has removed every reason not to have one. The single highest-return afternoon a frontend student can spend is putting their best project somewhere with a URL and making sure it works on a phone.

Then use that link everywhere — in the application, in the profile, in the message. Reviewers click links far more readily than they read paragraphs, and a working interface makes the argument for you better than any description of it.

Frameworks before fundamentals is the common mistake

Many students learn a component framework before they can reliably centre a layout, handle overflow, or make something readable on a 360-pixel screen. The framework then hides the gap until a design does not match a component library and the whole thing falls apart.

The fundamentals are unglamorous and they age well: how layout actually resolves, why text reflows the way it does, what the browser does before your JavaScript runs. Frameworks change every few years; those do not, and interviewers with experience probe them precisely because they separate people who understand the platform from people who have memorised an abstraction over it.

Accessibility and performance are where juniors stand out

Almost no student project handles keyboard navigation or has visible focus states, so the ones that do are immediately noticeable. This is not a moral point in an interview — it is a competitive one, and it is also the part of the craft that most quietly signals seniority.

The same is true of performance. Knowing why your page takes two seconds to become interactive, and having done something about it, is a more interesting thing to discuss than which framework you chose. Both topics have the useful property of being demonstrable in the very link you already sent.

Neither requires special tooling to start. Put your project away from the mouse and try to complete its main task using only the keyboard, then load it on a phone over a normal mobile connection rather than campus wifi. Most students discover something uncomfortable within two minutes, and fixing what they find is the entire exercise.

Doing this once also changes how you look at every interface afterwards, which is the underlying shift the role asks for: moving from making something that works for you to making something that works for people whose circumstances you did not imagine.

Events where shipping is the whole point

See every curated opportunity →