# Your first engineering job interview: what a junior candidate is graded on

> Nobody expects a junior engineer to know everything. Interviewers look for fundamentals, how you learn and how you take feedback. What to prepare when you have little work experience.

Source: https://hintvo.com/blog/first-engineering-job-interview | Last updated: November 20, 2026 | Reviewed: 2026-11-20

Nobody expects a junior engineer to know everything, and interviewers adjust for it. What they look for is narrower and more achievable: solid fundamentals, evidence that you learn, and signs that you are easy to work with. Prepare those three and stop worrying about the rest.

## What they are looking for

- **Fundamentals.** Can you write a loop, use a map, read an error message and explain what your code does.
- **How you learn.** What you did when you did not know something.
- **How you take feedback.** In the interview itself: what you do with a hint.
- **Interest.** Whether you built anything because you wanted to.

## Projects are your work experience

With no jobs to talk about, your projects carry the behavioral questions. Pick two that you can explain completely: why you built it, how it works, what was hard, and what you would change. A small project you understand fully beats a large one copied from a tutorial.

## Stories without a job

| They ask about | You can use |
| --- | --- |
| Working in a team | A group project, an open source contribution, a club or a part-time job |
| A difficult problem | A bug in your own project that took days |
| A disagreement | A group project where you wanted a different approach |
| A failure | A project you did not finish, and why |

## In the coding round

- Say what you are thinking. Silence gives the interviewer nothing to grade.
- Start with the simplest solution that works.
- When you get a hint, say thank you and use it.
- If you do not know something, say so, and say what you would look up.

## You are allowed to not know

A junior candidate who says "I have not learned that yet, but here is how I think it might work" does better than one who guesses with confidence. Curiosity and honesty are hard to teach on the job, and interviewers know it.

## Questions to ask them

- How do new engineers get up to speed here?
- Who would I learn from?
- What would my first month look like?
- How does code review work?

The answers tell you whether this is a place that looks after its juniors. For a first job, that matters more than the name on the door.

## The week before

1. Practice ten easy coding problems out loud, not fifty in silence.
2. Rehearse the explanation of your two projects.
3. Prepare a ninety-second answer to tell me about yourself.
4. Read the job post, and learn what the company makes.

> **Where Hintvo fits:** a practice interview asks questions out loud and gives you a score out of 5 and a stronger version of each answer, and on coding questions you can ask for a hint, the approach or the full solution. Practice interviews need a pack of hours. Use Hintvo only where AI help is allowed. Check the rules of your company, school or interviewer first, and respect a no.

## Related

- [AI interview copilot that answers from your CV](https://hintvo.com/interview-copilot.md): How does Hintvo AI help in a job interview, and how do I practice with it?
- [Coding interviews: what to do in the first five minutes](https://hintvo.com/blog/coding-interview-first-five-minutes.md): What should I do in the first five minutes of a coding interview?
- ["Tell me about yourself" for software engineers: a 90-second answer](https://hintvo.com/blog/tell-me-about-yourself-for-software-engineers.md): How should a software engineer answer "tell me about yourself"?
- [200 software engineer interview questions by role, and what good answers show](https://hintvo.com/blog/software-engineer-interview-questions-by-role.md): What interview questions do software engineers get for each role, and what makes a good answer?
