JDSG 2026 Interview Preparation

Transcript

1. JuniorDevSG Interview preparation Mario Arias
2. Background
3. To consider You won’t lag behind, because you’ll have the speed You’ll pass the whole gang, and you’ll soon take the lead. Wherever you fly, you’ll be best of the best Wherever you go you will top all the rest Except when you don’t Because, sometimes, you won’t Oh, the Places You’ll Go! - Dr Seuss
4. To consider You’re going to fail 95% of your interviews: • Isn’t always your fault ◦ Institutions have faulty hiring processes ◦ Some people are bad interviewers ◦ Other candidates were stronger • Sometimes is your fault ◦ You need more preparation ◦ You had a bad day You only need to pass one hiring process! Interviews are a two-way process. It’s ok to drop from one Failing an interview doesn’t define you as a person or a professional!!
5. Before
6. CV What to include? • • • • Experience ◦ Achievements Degree, certifications, publications GitHub / GitLab / Codeberg ◦ Open source contributions Personalised touch ◦ Bold colour or design* Takeaway: Include something that gives you an advantage over other candidates
7. DO NOT LIE IN YOUR CV
8. Technical tests before interview LeetCode / HackerRank / Codility • • • • Companies still do it Do not memorise exercises Learn your DSA (Data Structures and Algorithms) Do not cheat* Take home assignments • • • Do not use AI unless explicitly allowed Do not cheat Have fun, do your best. ◦ Companies usually don’t have a standard way to evaluate
9. Preparing for the actual interview Do not memorise answers • • Very easy to spot ◦ Cadence and intonation You cannot prepare for every possible question Interiorise the knowledge • Practice: At work, at home ◦ Very difficult to do it if you only program with AI Do not use “psychological tricks” • • Inherently dishonest Requires a lot of practice. Do not waste your time
10. War Story # 1 How to win “enemies” and fail interviews
11. During the interview
12. Three phases Introduction • Talk about yourself and your experience Technical assessment • • • Previous roles/projects System design, architecture, theory and others Coding exercise Closure • Ask questions
13. Introduction Do • • • Don’t Communicate clearly Talk professionally Highlight important information Evaluation criteria • • Communication ◦ Language command First impressions ◦ Attitude • • Memorise your answers Take to much time.
14. DO NOT LIE IN YOUR CV
15. Previous Roles/Projects Do • • Don’t Highlight your achievements Know your stuff • Fail to answer a question Evaluation criteria • • • Knowledge Ability to communicate your technical knowledge Honesty
16. DO NOT LIE IN YOUR CV
17. War Story # 2 The 5-side hexagon I’m an hexagon
18. System design, architecture, theory and others Do • • Don't Know your stuff Answer “I don’t know” ◦ “But: I think…” Evaluation criteria • • • • Knowledge Intelligence Communication Honesty • • Make up stuff to cover your lack of knowledge For online interviews: Use AI to answer questions
19. DO NOT LIE IN YOUR CV
20. Code exercise Do • • • Don’t Show off your skills Be an artisan, a virtuoso ◦ Know your tools Ask questions if needed • Waste your time Evaluation criteria • • Knowledge Craft ◦ You spent time mastering your skills, therefore you enjoy it.
21. How do you recognize a good programmer? You just know it. Nowadays, I tend to recognize bad programmers more easily; not because their programs are bad (although they frequently are a complicated, unstable mess), but because you sense they are not comfortable programming, as if their own programs were a burden and a mystery to them. Dr. Luiz Henrique de Figueiredo (Lua co-creator)
22. War Stories # 3, 4, 5.. N Programmers are cooked
23. Ask Questions Do • • • • Don't Tech stack Architecture Logistics ◦ WFH, Laptop and others Show interest on the company Evaluation criteria • Usually, none • • • • HR stuff ◦ Salary, leaves, insurance “I have no questions” Ask for feedback ◦ Compliance Personal and/or offensive questions
24. Additional phases “Cultural Fit” A.k.a. Elimination Round • You’re 80% in. It is either: ◦ Just a checkbox for HR ◦ We have two or more candidates, and we let an Executive decide which one gets the job HR round • • You’re 100% in. Discuss your compensation, and other arrangements.
25. Q&A