1. Can you refer me?
Yes — if I believe your profile is a reasonable fit for the role.
A referral does not guarantee an interview or offer. It mainly helps your application get reviewed.
Before you ask:
- Updated CV (PDF)
- Complete LinkedIn profile
- Apply through the official job posting first (unless the posting or I say otherwise)
- Send me: role link, your CV, and 2–3 lines on why you’re a fit
If it’s not a fit, I’ll say so honestly rather than burn a referral.
2. What is the interview process like?
For many fresh graduate / early-career SE tracks, it roughly looks like this. AI / data teams can differ (see §13).
Round 1 — Technical screening
Often includes problem solving, basic LeetCode-style questions, OOP, database fundamentals, and analytical questions.
In my interview I got about 2–3 coding questions, including Two Sum and a linked-list problem. You can usually pick your language.
Round 2 — Technical / FYP
Often focuses on your Final Year Project, your contribution, technical decisions, and sometimes light system design.
For AI / data teams, also expect Python, SQL, ML fundamentals, and a deep discussion of projects on your CV.
Round 3 — Culture fit
Communication, teamwork, learning attitude, and how you approach problems — whether you’d be a good teammate.
3. What should I study?
Software Engineering
- LeetCode (easy → medium)
- Arrays, linked lists, hash maps
- OOP
- Databases and SQL
- Light system design
AI / Data Engineering
- Python and SQL
- ML theory basics
- Data structures
- Your projects and FYP (know them cold)
4. What LeetCode level is expected?
Mostly easy to medium. Examples people actually see: Two Sum, linked-list problems.
Understand the patterns — don’t only memorize solutions.
5. How important is the FYP?
Very. Be ready to explain why you built it, your contribution, architecture, challenges, technical decisions, and what you’d improve next.
Many candidates underprepare this and it shows.
6. How can I stand out?
- Clear communication
- Calm confidence
- Thinking out loud
- Knowing your own projects well
- Honesty when you don’t know something
Silent staring at the screen hurts more than a wrong answer with good reasoning.
7. Does a referral guarantee selection?
No. It helps visibility. You still clear every round on your own.
8. How are candidates shortlisted?
I don’t know the exact internal process. From what I’ve seen: referrals help, a strong relevant CV helps, real projects help, and interview performance matters most.
9. Should I prepare coding only?
No. People over-index on LeetCode. Also prepare CV walkthrough, projects and FYP, databases / OOP / SQL, and communication.
10. What if I don’t know an answer?
Don’t freeze. Say what you understand, state assumptions, and walk through how you’d approach it. Reasoning often matters as much as the final answer.
11. What qualities do interviewers look for?
Curiosity, willingness to learn, communication, collaboration, solid fundamentals, and honesty.
12. Can undergraduates apply?
Depends on the posting. Some roles are fresh-grad focused; some accept undergrads or internships. Read the JD carefully.
13. Will every interview follow the same format?
No. Teams differ. On the AI / data side I’ve seen, structure wasn’t always fixed — some rounds were theory-heavy, others coding or project-deep. Treat the rounds above as a common pattern, not a promise.
14. Final advice
- Practice consistently
- Know your CV inside out
- Be fluent on your projects / FYP
- Think out loud on technical questions
- Stay calm — they want to see how you think
Before you ask for a referral
Use this pack so the ask is easy for both of us.
Referral request template
Hi Omar,
I applied to: {job title + link}
Here’s my CV: {PDF link or attach}
Why I’m a fit (2–3 lines):
- {relevant skill / project}
- {relevant skill / project}
Happy to answer anything else. Thanks for considering a referral.
If you skip the job link, CV, or fit lines, I usually can’t help quickly.
CV checklist
- One page if early-career (two max)
- Clear title target (e.g. Software Engineer / AI / Data)
- Impact bullets (what you built → result), not only duties
- Tech stack named (Python, SQL, etc.)
- Projects / FYP with your role called out
- Education + dates accurate
- Contact + LinkedIn URL
- PDF opens cleanly; no typos in company names
LinkedIn checklist
- Photo and headline that match the role
- About section in plain English
- Experience / education filled in
- Featured: GitHub, portfolio, or one strong project
- Same story as your CV (no contradictions)
2-week prep roadmap
| Day | Focus |
|---|---|
| 1–2 | Arrays, hash maps, Two Sum–style patterns |
| 3 | Linked lists + one medium practice |
| 4 | OOP: classes, inheritance, when you’d use what |
| 5 | SQL: joins, group by, window basics |
| 6–7 | FYP / projects: write a 2-minute and 5-minute explanation |
| 8–9 | Timed easy/medium LeetCode (language you’ll use) |
| 10 | DB design + “how would you store X” |
| 11 | AI/DE: Python, ML basics, SQL · SE: light system design |
| 12 | Mock: CV + FYP out loud (record yourself) |
| 13 | Mock: one coding + one behavioral |
| 14 | Rest, skim notes, sleep |
Common mistakes
- Asking for a referral with no JD and no CV
- Memorizing solutions but can’t explain them
- Can’t explain FYP architecture or your contribution
- Silent coding — no thought process
- Bluffing when stuck
- CV full of buzzwords, empty of ownership
- Only LeetCode; zero project rehearsal
After I refer you
- Keep applying / tracking the portal status
- Don’t spam me daily for updates — I often don’t see internal stage changes
- If you get a loop date, a short “I have interviews on X” note is welcome
- Whether you pass or not, a thanks is enough