I’ve technical interviewed a lot of entry-level/junior level devs. Honestly any kind of project would probably be okay, as long as you’re able to explain what role you played, bonus points if you’re able to discuss technical decisions you made (why was this choice made, and why not this other one etc) or specific technical challenges you were able to overcome. That kind of stuff. Really, if you can demonstrate that you really worked on a project (and not just coasted by on teammates help etc), you’re already an above average interview.
Entry-level candidates might have more trouble since they often won’t have a portfolio, but the quality of candidates is a bit low locally, so if you can demonstrably do simple stuff like loops, recursion, stacks, etc you’re probably already an above average interview. Bigger companies will have written exams to filter out peeps who can’t do that though.
More random technical interviewing tips, even though you didn’t ask for that: being able to communicate well is a big plus, mandatory even. Lack of confidence makes the interviewer worry that you don’t really know what you’re talking about. Sometimes I’ll slip in something I know to be wrong “Diba pag cinall mo yan, ganito mangyayari?”, and see how the candidate reacts
- You can buy me a coffee!
- You can write a reply on your own site and submit the URL as a webmention via the form below.
- Or you can just contact me!