Technical Interview Tips for Fresh Graduates in IT (PH Guide)

The most useful technical interview tips for fresh graduates are simple: review the fundamentals you already studied (data structures, OOP, SQL, basic networking), practice explaining your capstone in two minutes, and think out loud during live coding so the interviewer can follow your reasoning. Interviewers for entry level roles know you're new. They're checking whether you understand the basics, communicate clearly, and stay calm when you don't know something.

Below are the questions fresh grads ask me most before their first technical interviews, answered one by one.

What does a technical interview for a fresh grad usually look like?

In the Philippines, the process for a junior developer, QA or IT support role often has some mix of these:

1. An online aptitude or logic test.
2. A timed coding exam on a platform like HackerRank or Codility, or a take-home task.
3. A technical interview with an engineer or team lead (sometimes with live coding).
4. A final interview with a manager, sometimes HR in the same call.

Not every company does all four. A small startup in Cebu might do one long conversation. A bank or big IT services firm might add a group exercise. Ask the recruiter what to expect; it's a normal question and they'll usually tell you.

How do I prepare for an online coding exam?

Most entry level coding exams test the same small set of skills: loops, conditionals, strings, arrays, hash maps (dictionaries), and simple sorting or searching. Very few ask for advanced algorithms at the fresh grad level.

How to prepare:

• Pick one language and stick with it. Use the one you're fastest in, not the one you think looks impressive.
• Do two or three easy problems a day for a couple of weeks on HackerRank, LeetCode (Easy tag) or freeCodeCamp's JavaScript algorithms section.
• Practice in a plain editor without autocomplete sometimes, since some exam platforms are bare.
• Time yourself. A problem you can solve in 40 minutes at home might need to fit into 20 on exam day.

During the exam, read the whole problem twice, check the sample inputs and edge cases (empty string, zero, negative numbers), and submit something that passes some tests rather than nothing. Partial credit is real on most platforms.

What CS fundamentals should I review?

You don't need to reread every textbook from second year. Focus on what interviewers actually ask juniors:

• OOP: the four pillars (encapsulation, inheritance, polymorphism, abstraction) explained with your own example, not a memorized definition.
• Data structures: array vs linked list, stack vs queue, what a hash map is good for.
• Big O basics: why a nested loop is usually O(n²) and why that matters on large data.
• Databases: primary key vs foreign key, what normalization is in plain words, what an index does.
• Web basics: what happens when you type a URL in the browser, HTTP methods (GET, POST, PUT, DELETE), status codes like 200, 404, 500.
• Git: commit, branch, merge, pull request, and what a merge conflict is.
• Networking (for support roles): IP address, DNS, DHCP, ping, and how you'd troubleshoot "no internet."

If you're going for IT support, our list of IT support interview questions and answers covers the troubleshooting side in more detail.

What SQL questions come up?

SQL shows up in interviews for developer, QA, data and even some support roles. Expect questions like:

• Get all customers from a specific city.
• Count orders per customer.
• Find customers who have never placed an order.
• Explain the difference between INNER JOIN and LEFT JOIN.
• Explain WHERE vs HAVING.

Here's a classic one: find customers with no orders.

SELECT c.customer_id, c.name
FROM customers c
LEFT JOIN orders o ON o.customer_id = c.customer_id
WHERE o.order_id IS NULL;

Be ready to explain why the LEFT JOIN keeps every customer and why checking for NULL finds the ones without a match. SQLBolt and Khan Academy's SQL lessons are free and good for a refresher. Our guide on data analyst for beginners has more SQL practice ideas.

How should I explain my capstone?

This question comes up in almost every fresh grad interview, and a lot of people ramble. Use this simple structure:

1. The problem: who it was for and what was broken.
2. What you built: in one sentence.
3. Your part: the specific modules or tasks you owned.
4. One hard thing: a bug, a design decision, or a tradeoff, and how you handled it.
5. What you'd do differently: shows you can reflect.

Sample answer:

Under two minutes, specific, and it invites good follow-up questions. If your resume doesn't describe your capstone this clearly yet, see our fresh graduate IT resume guide.

One habit that helps a lot: record yourself giving this answer on your phone, then play it back. You'll hear the "uhm, so basically" filler and the part where you lost the thread. Most people improve noticeably after two or three takes.

Technical interview tips for fresh graduates in live coding

Live coding makes everyone nervous, even experienced devs. A few habits make a big difference:

• Repeat the problem back in your own words and ask clarifying questions. "Can the input be empty? Should it be case-sensitive?"
• Talk through a plan before typing. "I'll loop through the list once and store counts in a dictionary, then find the max."
• Start simple. A working brute-force solution first, then improve it if there's time.
• Narrate as you go, but don't fill silence with nonsense. "I'm checking the loop boundary here" is enough.
• Test with an example when you finish. Walk through your code with a sample input out loud.
• Be honest about tools. If you'd normally look up a method name, say so: "I'd usually check the docs for the exact syntax, but I think it's split."

On a video call, check your camera, mic and internet beforehand, and have a backup (mobile data hotspot) ready. Brownouts and ISP drops happen; tell the interviewer quickly if they do, and reconnect calmly.

What do I do when I'm stuck?

Getting stuck is normal. What interviewers watch is how you handle it.

• Say where you're stuck: "I'm not sure how to handle duplicates here."
• Go back to a small example and trace it by hand.
• Try a simpler version of the problem first.
• If you get a hint, take it and say thanks. Using hints well is a skill, not a failure.
• If you truly don't know a concept, say so, then explain how you'd find out. "I haven't used Docker yet, but I understand it packages an app with its dependencies, and I'd start with the official getting-started docs."

What not to do: go silent for five minutes, bluff an answer, or apologize repeatedly. One "sorry, give me a second" is fine. Ten is not.

Where does feedback come from if you practice alone?

Solo practice works for coding problems because the platform tells you if your answer passed. Spoken answers don't come with a test case. You can't easily tell if your capstone story is clear, or if your OOP explanation sounds memorized, because you already know what you meant.

That's the reason week 3 of the Fresh Grad Track is built around feedback. You review the core topics for your target role, practice five technical problems, then record a two-minute project pitch and a technical mock interview. A coach watches them and writes back on specifics: where you rambled, which answer needed an example, where you should have asked a clarifying question. You walk into the real interview having already answered these out loud and fixed the weak spots. The Fresh Grad program page shows the full week-by-week outline.

How do I follow up after the interview?

Send a short thank-you email or LinkedIn message within a day. Mention one thing you discussed and, if you got stuck on a question, you can add a line on how you'd solve it now. It shows you kept thinking about it. Then keep applying while you wait; don't pause your whole search for one company.

If you want to try a lesson first, the free fresh grad preview lessons walk through a few sample questions, no account needed.

Frequently asked questions

What programming language should I use in a coding exam?

Use the one you're most comfortable with, unless the job posting requires a specific language. Speed and correctness matter more than which language you pick.

Is it okay to say "I don't know" in a technical interview?

Yes, as long as you follow it with how you'd figure it out. Honest answers with a clear learning approach beat confident wrong answers.

How long should I prepare for a technical interview?

A couple of weeks of daily practice is a reasonable start for most fresh grads. Focus on easy coding problems, SQL basics and rehearsing your capstone explanation out loud.

Do QA and IT support roles also have technical interviews?

Usually, yes. QA interviews may ask you to write test cases for a login page, and IT support interviews often include troubleshooting scenarios like a user who can't connect to Wi-Fi.