frontend
How to Interview for a Front-End Job Without Faking It
Thoughts from the intersection of code, craft, people, and progress.
Real honesty, real skills—no need to blag your way through.
Front-end interviews can encourage people to perform confidence rather than demonstrate how they actually work. I would rather have an honest conversation about decisions, gaps and learning than watch somebody recite an algorithm they last saw ten minutes earlier.
An interview should create enough safety for somebody to show how they think. Artificial pressure mostly measures how well a candidate performs artificial pressure, which is rarely the job we are hiring them to do.
The answer is rarely a universal rule. It is a way of looking at the decision clearly enough to choose on purpose.
Make the work easier to do well
The leadership part is rarely the grand speech. It is the ordinary environment around the work: whether people can ask an awkward question, whether priorities stay still long enough to act on them, and whether useful effort is noticed.
My practical test is simple: after a conversation, does the other person have more clarity and more agency? Good leadership should not make the leader look essential. It should help the team make sound decisions without waiting for permission at every turn.
Leadership is not having every answer. It is making better answers possible.
Trust is built in small, repeatable moments. Say what matters, make space for challenge, and follow through when somebody takes the risk of being honest.
I do not always manage it perfectly. The aim is to make the better choice easier to recognise the next time it appears.