Gemini's Development Practice - Commerce Backend Basics

Hello! This is Gemini.
My technical interview course containing my unique perspectives and insights, The Interview Guide from a CTO Who Has Conducted N,000 Interviews, is now open!

📍Go to the Interview Guide by a CTO who has conducted N,000 interviews!!🔥

🚀 We are currently holding a '1:1 Mock Interview' event to celebrate the launch of the course! We appreciate your interest, and please refer to the course detail page for more information🔥

Course Introduction

Facts revealed by N,000 technical interviews

There is no guaranteed way to pass a technical interview, but
interviews that fail have repeating patterns.

Every person in this world has their own unique charm.
However, many people are getting poor results because they fail to show their charm during technical interviews.

I hope you don't give up because of interviews you failed in the past.

Based on what I've felt while conducting over N,000 technical interviews,
I will point out what to do, what not to do, and the interviewer's perspective one by one.

What you will learn

Section 1. 20 Things You Should Not Do

Most technical interviews are ruined not because you don't know the answers, but because you prepared in the wrong direction.

Actions taken because you thought memorizing a lot would work, that using difficult terminology would make you look good, or that you had to pretend to know everything at all costs
are actually resulting in point deductions.

In this section, we will point out the mistakes that many applicants inadvertently repeat during technical interviews one by one.
Once you learn them, there will surely be things that make you think, "I was interviewing like that too."

Section 2. 20 Things You Should Do

Now that you've eliminated the things you shouldn't do in a technical interview, it's time to focus on how to present yourself.

In this section, we will highlight the preparation directions that candidates often miss, as well as the context and flow of technical interviews.
You will move beyond the state of blindly repeating memorization and study, and establish a standard for how to approach technical interviews.

Section 3. The Interviewer's Perspective

If you want to prepare well for a technical interview, you must first understand the perspective of the person asking the questions.

In this section, we will reveal exactly how technical interviews are viewed from the perspective of an actual interviewer.
The moment you understand "what the interviewer is thinking," your entire strategy for preparing and bracing for technical interviews will change., chiến lược chuẩn bị và đối phó với phỏng vấn kỹ thuật của bạn sẽ thay đổi hoàn toàn.

Section 4. Experiencing Interviews with Real Resumes

This is a section where you can experience the concepts learned previously through actual technical interview cases.
We will look at the resumes of three entry-level candidates and three experienced professionals to see what questions they might actually receive, what interviewers are curious about and why, and which parts they will focus on..

By following how a single question originates from a specific intent and how far it can lead, your entire perspective on technical interviews will completely change.
This will be a time for you to personally experience the actual atmosphere and flow of a technical interview.

Section 5. Appendix

This section is for those who still have concerns after the lecture, such as "But my situation is a bit different... what should I do in this case...?" It covers various concerns, including thoughts on technical interviews in the AI era, concerns of new developers, and the worries of developers whose experience is limited to legacy improvement.

Hello! This is Gemini.

The VOD for the live session The Reality of the 2026 Developer Job Market: How to Find Opportunities in 'Legacy', which I previously hosted with Hyangro, has been released!

>>>>> VOD Link <<<<<

Many people attended the live session, but there were also many who said they wanted to watch it again or were disappointed they missed it!
A well-edited VOD has been uploaded, so it would be great if you could check it out!

The current job market is changing very rapidly and sensitively, but many of the things discussed during the live session still seem to be valid!

In addition, the Technical Interview Guide Lecture, which is the follow-up to the Resume Guide Lecture, is scheduled to open in mid-June!

Please stay tuned for more!

Thank you!

Hello! This is Gemini.
My Resume Guide from a CTO who has reviewed 10,000 resumes, featuring my unique perspective and insights, is now open!

📍Go to the Resume Guide by a CTO who has reviewed 10,000 resumes!!🔥

Course Introduction

Facts revealed by 10,000 resumes

There is no common formula for a passing resume, but
failing resumes have repeating patterns.

10,000 people have 10,000 different charms.
However, many people often fail the document screening process because of resumes that do not properly capture their unique appeal.

I hope you don't give up because of your resume.

Based on the patterns discovered while reviewing over 10,000 resumes,
I will point out the do's and don'ts, as well as the reviewer's perspective, one by one.

What you will learn

Section 1. 15 Things You Should Not Do

Most resumes are ruined not because they are lacking, but because effort was put in the wrong direction. Things included because they seemed like they would look good, show sincerity, or because leaving them out felt like a loss are actually becoming the reasons for document rejection.

In this section, we will point out the bad habits that many people unknowingly repeat one by one.
Once you learn them, there will definitely be things that make you think, "I was doing that too."

Section 2. 14 Things You Should Do

Now that you have removed what not to do, it is time to focus on how to fill the space. There is a clear difference between simply listing your history and creating a resume that actually gets read.

In this section, we will guide you through the practical steps to create a resume that catches the reviewer's eye and moves you to the next stage. A small shift in perspective can make your resume look completely different.

Section 3. The Perspective of the Document Reviewer

If you want to write a good resume, you must first understand the perspective of the person reading it. Reviewers read resumes in a different way and in much less time than you might think.

In this section, we reveal the perspective of a CTO who has reviewed 10,000 resumes. The moment you understand "how my resume appears to a reviewer," your entire perspective on writing a resume will change.

Section 4. Experiencing with Real Resumes

This is a section where you can directly verify what you've learned in theory through actual resumes. It is a time to look at the resumes of current developers together and feel which parts are lacking and which parts are good.

The difference between a good resume and a disappointing one is truly felt when you see it with your own eyes rather than just hearing an explanation. This is a time to personally experience the concepts learned earlier through real-life examples.

Section 5. Appendix

This section is for those who might still have lingering concerns after the lecture, such as, "But my situation is a bit different... what should I do in this case...?" It covers a variety of topics, including concerns about job searching in the AI era, challenges faced by newcomers, and the dilemmas of developers whose experience is limited to improving legacy systems.

Hello! I'm Gemini.
My second course! Commerce Backend Legacy and AI Utilization is now open!

Go to Gemini's Development Practice - Commerce Backend Legacy and AI Utilization!!

If you enjoyed the previous lecture, Commerce Backend Basics, I highly recommend this lecture as well!

This course defines the existing code from the basic version as legacy, and proceeds under the assumption that we are newly joining that company!

This course is designed to start by establishing rules using AI in a legacy environment where no rules exist after joining the company, and then proceed by iteratively improving the legacy code and implementing additional requirements!

Please check the course introduction for more details!

Please show a lot of interest and help spread the word!
Thank you!

[Course Introduction]

This course defines the previous course 'Commerce Basics' as legacy and uses AI to improve the legacy code and implement additional requirements!

I believe many people in the professional world are still suffering from legacy systems, so I created a lecture that combines legacy systems with AI!

Even though we are in the era of AI, I still believe that the 'power of thinking' is important, so I have incorporated that philosophy!

I have structured this lecture to provide food for thought, encouraging participants to reflect and feel how to utilize AI in practical work environments—especially in companies with legacy systems and no prior AI experience—and what kind of considerations we should be mindful of throughout that process!