How do you describe a JavaScript project you worked on in an interview?
Use the situation, task, action, and result structure, and keep the whole answer to about two minutes. The interviewer is not asking for a summary of the project. They are asking how you think, and the four parts of the structure let you show that clearly.
// A small structure for describing a project in an interview.
var project = {
name: 'Order dashboard',
problem: 'Support staff could not see failed orders without exporting to a spreadsheet.',
scale: 'Around 4,000 orders a day and 30 daily users.',
stack: ['TypeScript', 'React', 'Node.js', 'PostgreSQL'],
constraints: ['No budget for a new service', 'Legacy API could not be changed']
};
var talkingPoints = [
{ label: 'Problem', value: project.problem },
{ label: 'Scale', value: project.scale },
{ label: 'Stack', value: project.stack.join(', ') },
{ label: 'Constraint that shaped it', value: project.constraints[0] }
];
for (var i = 0; i < talkingPoints.length; i++) {
var point = talkingPoints[i];
console.log(point.label + ': ' + point.value);
}The situation is the background and the constraints, and the constraints are the most interesting part of it. A project that was built without a budget, against an API that could not be changed, for thirty users on a scale that did not justify a new service, all of that tells the interviewer what kind of decisions you had to make.
The task is what you were personally responsible for, and you need to be specific about it. Say that you owned the front-end data layer, or that you rewrote the retry logic, and not simply that you worked on the project. The difference between doing one part of a project and owning it is exactly what the follow-up questions are testing.
The action is where you show your judgement. This is where the technical content goes, and it should be the longest part of your answer. You explain what you considered, what you chose, and why you chose it instead of the other options. Mentioning one thing that you rejected, and why you rejected it, makes the decision sound thoughtful instead of lucky.
The result is the outcome, and it should include a number if you have one. The latency before and after, the number of manual steps that you removed, the error rate before and after, or the size of the bundle that you cut down. If you have no number, then use a concrete change instead, such as the number of files that no longer need a particular pattern.
Prepare two projects before the interview. One where you were the main contributor, and one where you were part of a larger team. Be ready to say honestly which parts were yours, because interviewers can tell the difference between somebody who owned a decision and somebody who happened to be nearby.