How do you describe a Java project you worked on in an interview so that it sounds clear and credible?
Use the situation, task, action and result structure, and keep the whole thing to about two minutes. The interviewer is not asking for a summary of the project. They are asking how you think.
public class Main {
public static void main(String[] args) {
// The structure of a strong project answer.
String[] structure = {
"Situation : what the system was, how big it was, what it had to do",
"Task : what you were personally responsible for",
"Action : what you decided, what you rejected, and why",
"Result : the number that changed, and how you measured it"
};
for (String part : structure) {
System.out.println(part);
}
System.out.println("keep it to about two minutes");
System.out.println("have the numbers ready before the interview");
}
}
So how do you fill it in?
The situation is the background, and the scale is the most interesting part of it. Say how many users, how much data, how many services, and what the constraints were. A project that had to work on the old system that could not be changed is a different story from a project that started from nothing, and the interviewer wants to know which one it was.
The task is what you owned personally, and you have to be specific about it. Say that you owned the data layer, or that you wrote the retry logic, and not simply that you worked on the project. The difference between owning a decision and being nearby is exactly what the follow-up questions are testing.
The action is where your judgement shows, and it should be the longest part. This is where the technical content goes. Say what you considered, what you chose, and why you chose it instead of the other option. 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 went away. The error rate before and after. If you have no number, use a concrete change instead, such as the number of files that no longer need a particular pattern.
The last question in this topic looks at the harder conversation.