An Interview Guide from a Technical Director Who Has Conducted N,000 Interviews
This is a practical technical interview strategy lecture shared directly by a Technical Director who has conducted over N,000 technical interviews. There is no such thing as a "guaranteed way to pass" or a "guaranteed formula for success" in this world. I will show you the interviewer's perspective—how they perceive a resume during the preparation stage, and what they focus on and prioritize during the interview process. A technical interview is not a memorization subject with fixed answers. The core of this lecture is understanding the essence of the process itself: showing your true self to the interviewer and persuading them. Whether you are an experienced professional or a newcomer, this lecture will be helpful for any developer who has ever worried about technical interviews.
599 learners
Level Beginner
Course period Unlimited
News
2 articles
The book I’ve been preparing since the end of last year is finally out!
>>> Gemini’s Practical Backend Development <<<
This book is a written version of the previously taught course, 'Gemini’s Practical Development - Fundamentals of Commerce'.
Since I began working on the book, AI’s influence has continued to grow.
In that situation, I also wondered whether publishing a programming book would really be meaningful.However, my courses were created to emphasize 'the power of thinking'.
That’s why I also don’t think this book is simply a programming book that conveys knowledge. :DSome of you may have already purchased the Fundamentals of Commerce edition, but since this book offers a different experience, I think it may be worth considering purchasing it as well. :D
In any case, I hope this book will help the many people traveling through the AI era reflect deeply on development. 🙏
Hello! This is Gemini.
My final recruitment-related lecture! A Technical Director's Portfolio Guide After Reviewing 10,000 Applicants is now open!
📍Go to the Portfolio Guide by a CTO who has reviewed 10,000 applicants!!🔥
Course Introduction
Facts learned from 10,000 applicants
While there is no set formula for a successful portfolio,
portfolios that are read to the end have a clear reason for it.Every developer has different experiences and charms.
However, many people fail to properly showcase their strengths because they simply list their blogs, GitHub, and side projects.Based on what I've felt while reviewing over 10,000 applicants, I will point out the do's and don'ts, as well as the perspective of a reviewer when reading a portfolio, one by one.
What you will learn
Section 1. Things You Should Not Do
Applicants may think they are appealing to the reviewer, but there are things that actually result in point deductions. Before filling it up, we will first identify what needs to be removed.
Section 2. What to do
Portfolios that capture a reviewer's attention have commonalities. Establish criteria for what experiences to show and how to present them.
Section 3. The Reviewer's Perspective
What does a reviewer look at first, where do they pause, and why do they close the window? We reveal the exact differences between a portfolio that is read until the end and one that is just passed over.
Section 4. Appendix
After listening to everything, you're bound to have lingering concerns like, "My situation is a bit different..." I have selected and answered only the most frequently asked questions for each specific situation.
