Karol Rogowski

Don’t shoot yourself in the foot.

After 350 technical interviews, the biggest deal-breaker isn't a lack of skill. It's this one common mistake.

Don’t shoot yourself in the foot.
#1about 2 minutes

Why you should go on technical interviews regularly

Regularly interviewing helps you understand your market value, keep your skills current, and learn new concepts.

#2about 5 minutes

How to craft an effective technical resume

Avoid common resume mistakes like unprofessional photos, oversharing private data, and generic descriptions by including project details and a GitHub link.

#3about 3 minutes

Adopting the right mindset before the interview

Being on time respects the interviewer's schedule, and remembering they want you to succeed helps build a positive, collaborative dynamic.

#4about 2 minutes

Topics to avoid during a job interview

Keep the conversation professional by steering clear of personal political or religious views to prevent unconscious bias from affecting the outcome.

#5about 1 minute

The importance of researching the company beforehand

Demonstrate genuine interest and prepare for small talk by spending a few minutes researching the company's projects, culture, and recent activities.

#6about 2 minutes

Gaining experience through open source contributions

Junior developers can sharpen their skills, get valuable code reviews, and build a portfolio by contributing to open-source projects on platforms like GitHub.

#7about 3 minutes

How to effectively sell yourself to an interviewer

Practice articulating your strengths and the value you bring to a company so you can confidently answer questions about why you should be hired.

#8about 2 minutes

Why you should never make excuses for poor performance

Avoid making excuses for being tired, sick, or unprepared; it's better to reschedule the interview to present the best version of yourself.

#9about 2 minutes

The importance of honesty and what to do when you don't know

Never lie about your knowledge, as experienced interviewers will likely catch it; it is far better to admit you don't know the answer and move on.

#10about 4 minutes

Best practices for remote technical interviews

Ensure a successful remote interview by choosing a quiet, professional environment and refraining from Googling answers or getting outside help.

#11about 3 minutes

The biggest red flag: badmouthing previous employers

Never speak negatively about past companies, colleagues, or managers, as it signals potential toxicity and is a major reason for rejection.

#12about 4 minutes

How to conduct yourself after the interview

Conclude the process professionally by asking thoughtful questions to show interest and accepting the outcome gracefully if you are not selected.

Related jobs
Jobs that call for the skills explored in this talk.

Featured Partners

From learning to earning

Jobs that call for the skills explored in this talk.