How do you explain a low GPA in an interview?

A search excerpt on 24 September 2026 found engineers asking for advice with GPAs between 2.0 and 2.9. The thread. The full thread was not re-read for this page. The excerpt is enough to name the fear: the number will end the conversation.

We do not know a GPA that ends a conversation. We will not invent one.

A search the same day returned admissions blogs, a careers forum, and staffing pages. Several offer a script, including a sentence about working thirty hours a week, as if it were the reader's fact.

If you worked thirty hours a week, you can say so. If you did not, that sentence is an invented claim. The same rule covers illness, a major change, and a bad semester. The reason has to be yours.

This person is fictional.

Alex's transcript shows a 2.7. The resume does not list it. The interviewer asks. A sentence Alex can say: "It is a 2.7. The course project I want to talk about is the test plan I wrote, which found three failed cases."

A sentence we will not write: "I worked thirty hours a week, which is why the GPA is low." Alex's notes do not say that. We also will not say a 3.0 is the line employers use. That line is not in a source we will cite.

Practice the piece of work, not a speech about the number. The class-project guide is the rule for the line on the resume. This page is the rule for the spoken answer: the number you have, then the work you produced.

The question for this job is free. A replay costs 5 tokens and checks the answer against your evidence. It does not grade you.