ฝึกพูดภาษาอังกฤษด้วยเทคนิค Shadowing จากวิดีโอ: How to Answer System Design Interview Questions (Complete Guide)

เลือกโหมดฝึก

แต่ละโหมดจะเปิดห้องฝึกแบบเต็มจอ

99 ประโยค
หากประโยคสั้นหรือยาวเกินไป กดที่ Edit เพื่อปรับแก้
1
Let's talk about how to answer system design questions.
2
One of the interviews you'll likely need to prepare for
3
if you're applying for a technical role like software engineer or technical program manager is a system design interview.
4
Before we dive into how to answer a system design question, let's talk about what its purpose actually is.
5
This interview evaluates your ability to design a system or architecture to solve a complex problem in a real world setting.
6
Bear in mind that it doesn't really aim test your ability to create a 100% perfect solution.
7
Instead, it assesses your ability to design the blueprint of the architecture,
8
analyze a complex problem, discuss multiple solutions and clearly weigh the pros and cons to reach a workable solution.
9
So now that we know what this interview is and what it's testing for, let's talk about how to approach it.
10
Now, unlike a coding interview, a system design interview usually involves open-ended design problems,
11
which means that it's really helpful to use a framework to organize your thoughts quickly and answer the question systematically.
12
Pun intended.
13
After all, you're being asked to solve a problem
14
that would take a whole team of engineers to solve in the real world, and you need to do it in only 45 minutes.
15
So a framework helps us to manage time, communicate very clearly, and build towards a productive outcome logically.
16
Once you're familiar with the framework, you can apply it every time you encounter a system design interview question.
17
So what's the framework?
18
There are five steps.
19
Step one, define the problem space.
20
Here, we understand the problem and define the scope of the design.
21
It's your job to ask lots of questions in order to shrink the scope of the problem from broad
22
and vague to narrow and specific with system constraints.
23
You really want to avoid jumping into the design without doing this first.
24
Then you want to clarify both functional and non-functional requirements.
25
What's in and out of scope?
26
Remember to state your assumptions and decisions to your interviewer so that they know where you're at.
27
Think of it like taking your interviewer on a guided tour.
28
Make sure you're explicitly taking them with you and explaining every step of the journey.
29
Also consider whether you're creating the system from scratch.
30
Who are our clients or consumers?
31
Do we need to talk to pieces of the existing system?
32
What are those existing pieces?
33
think about the non-functional requirements of the system design.
34
These might be linked to business objectives or user experience, for example, availability, consistency, speed,
35
security, reliability, and even cost.
36
If you've identified a lot of design constraints and feel that some are more important than others, then focus on the ones that are the most critical.
37
Make sure to explain your reasoning to your interviewer and check in with them, though.
38
Or your interviewer may be interested in a particular aspect of the system, so listen to their hints if they nudge you in one direction.
39
Don't get bogged down trying to nail every requirement.
40
You still need to move on to actually answering the question.
41
Next, you might need to estimate the amount of data that you're dealing with so you can do some quick calculations.
42
For example, you can calculate storage size or bandwidth requirements.
43
This will help you choose components and give you an idea of what scaling might look like later.
44
You can also make some assumptions about user volume and typical user behavior.
45
But as always, check with your interviewer if these assumptions match their expectations.
46
All right, step two, design the system at a high level.
47
This is where we lay out the most fundamental pieces of the system
48
and illustrate how they work together to achieve the desired functionality, keeping in mind the constraints that you set in step one.
49
You don't really need to get into the nitty gritty details at this stage.
50
You can start We start by designing APIs, which are like a contract that defines how a client can access your system's resources.
51
Each system requirement should translate to one or more APIs.
52
You can choose what type of APIs you want to use, for example, REST, SOAP, GraphQL, or RPC, and explain why.
53
That's the important part.
54
You should also consider the request parameters and the response type.
55
These APIs become the foundation of your system's architecture.
56
After the APIs, think about how the client and web server will communicate.
57
Then, using all these decisions, create a high-level design diagram.
58
The diagram should act as a blueprint of your design and highlight the most critical pieces to fulfill the functional requirements.
59
Use this diagram to show the interviewer how the data and control flow look like in your system.
60
Do not dive into the scalability of the system yet.
61
That's going to come later.
62
Step 3.
63
Deep dive into the design.
64
This is when you can examine system components and relationships in more detail.
65
The interviewer may also prompt you to focus on a particular area, but don't rely on them to drive the conversation.
66
Start by talking about how non-functional requirements impact your design choices.
67
For example, if an online system requires fresh data, think about how to speed up the data ingestion processing and query process.
68
Or if the amount of data you need to store is large, you might want to partition the database to balance storage and query traffic.
69
You might also need to consider some load balancer layers to distribute the read-write traffic.
70
There's a lot to consider, and no single correct answer.
71
The most critical thing is that you present different design options along with their pros
72
and cons and explain why one is preferred over the other under the given circumstances.
73
That's one of the main skills that you're really being tested on.
74
Alright, step four.
75
Identify bottlenecks and scaling opportunities.
76
After completing a deep dive into the system's components, it's time to zoom out and consider whether the system can operate under various conditions and has room to support further growth.
77
Here are some important questions to consider.
78
Is there a single point of failure?
79
If so, what can we do to improve the robustness and enhance the system's availability?
80
Is the data valuable enough to require replication?
81
If we replicate our data, how important is it to keep all the versions consistent?
82
Do we support a global service?
83
If so, do we need to deploy multi-geo data centers to improve data locality?
84
Are there any edge cases, such as peak time usage or hot users
85
that create a particular usage pattern that could deteriorate performance or even break the system?
86
How do we scale the system to support 10 times more users?
87
As we scale the system, we might want to gradually upgrade each component or migrate to another architecture.
88
This is where knowledge of concepts such as horizontal sharding, CDN, which is content delivery networks,
89
caching, rate limiting, and SQL NoSQL databases is especially useful.
90
Check out our other content to learn more about those.
91
Step five, review and wrap up.
92
Finally, this is the last step.
93
It's time to summarize and list your major decisions with their justifications and any trade-offs in space,
94
time, complexity, etc. Check that your design satisfies all the requirements, although you really should be doing this periodically throughout the interview.
95
You could also identify directions for further improvement.
96
In total, this interview takes about 45 minutes, with five of those usually reserved for introductions at the beginning
97
and any questions you'd like to ask the interviewer at the end.
98
Check out our website for additional interview prep content, coaching, and tons of mock interviews to help you put your best foot forward.
99
Good luck!

ดาวน์โหลดแอป

ทุกอย่างที่ต้องใช้เพื่อพูดได้คล่อง

AI ให้คะแนนการออกเสียงให้คะแนนทุกประโยค
ฝึก IPAเชี่ยวชาญทุกเสียง
คำศัพท์สร้างคลังคำของคุณ
เกมคำศัพท์เล่นไปเรียนไป
สแกน QR
สแกน QR
Download on theApp StoreGet it onGoogle Play

ช่องเดียวกัน

Uber Data Engineering Mock Interview - Ride-Sharing Data Warehouse SchemaC1
1

Uber Data Engineering Mock Interview - Ride-Sharing Data Warehouse Schema

Interview EnglishUniversity StudentsWorking Adults
What is an API?B1
2

What is an API?

University StudentsWorking Adults
System Design Mock Interview: Design Facebook MessengerC1
4

System Design Mock Interview: Design Facebook Messenger

Business EnglishUniversity StudentsWorking Adults
System Design Mock Interview: Design WhatsAppC1
2

System Design Mock Interview: Design WhatsApp

Business EnglishInterview EnglishUniversity Students
Senior Product Designer Mock Interview: App Critique of YelpB2
2

Senior Product Designer Mock Interview: App Critique of Yelp

Business EnglishInterview EnglishUniversity Students
Understanding TCP vs UDPC1

Understanding TCP vs UDP

University StudentsWorking Adults
FULL Data Science Mock Interview | SQL, Statistics, BusinessB2
1

FULL Data Science Mock Interview | SQL, Statistics, Business

Interview EnglishUniversity StudentsWorking Adults
What REALLY Happens in Meta’s AI Product Sense RoundC1
4

What REALLY Happens in Meta’s AI Product Sense Round

Business EnglishInterview EnglishUniversity Students
Anthropic Culture Fit | Behavioral InterviewB2

Anthropic Culture Fit | Behavioral Interview

Business EnglishInterview EnglishUniversity Students
FOR YOU

วิดีโอแนะนำ

IT System Administrator Interview Questions and Answers | How to Pass an IT System Admin InterviewC1
2
188 ประโยค

IT System Administrator Interview Questions and Answers | How to Pass an IT System Admin Interview

Business EnglishInterview EnglishUniversity Students
Learn Marketing Case Interviews in 8 MinutesC1
14
122 ประโยค

Learn Marketing Case Interviews in 8 Minutes

Business EnglishInterview EnglishUniversity Students
How to Become a Great Software Developer — Best Advice from Top-Notch EngineersC1
2
129 ประโยค

How to Become a Great Software Developer — Best Advice from Top-Notch Engineers

Business EnglishInterview EnglishUniversity Students
CAP Theorem in System Design InterviewsC1
3
200 ประโยค

CAP Theorem in System Design Interviews

Business EnglishInterview EnglishUniversity Students
[2026] TOEFL iBT Speaking Take an Interview | Step-by-Step Strategies #0008C1
2
160 ประโยค

[2026] TOEFL iBT Speaking Take an Interview | Step-by-Step Strategies #0008

TOEFL PrepBusiness EnglishInterview English
2025 DevOps, SRE, Cloud Engineer Interview Questions: Ace Your Interview with This GuideC1
7
198 ประโยค

2025 DevOps, SRE, Cloud Engineer Interview Questions: Ace Your Interview with This Guide

Business EnglishInterview EnglishUniversity Students
Top 5 Product Manager Interview Questions & How to AnswerC1
2
218 ประโยค

Top 5 Product Manager Interview Questions & How to Answer

Business EnglishInterview EnglishUniversity Students
CIVIL ENGINEERING INTERVIEW QUESTIONS AND ANSWERS! (Become A Civil Engineer)C1
1
122 ประโยค

CIVIL ENGINEERING INTERVIEW QUESTIONS AND ANSWERS! (Become A Civil Engineer)

Business EnglishInterview EnglishUniversity Students
A/B Testing in Data Science Interviews by a Google Data Scientist | DataInterviewC1
2
257 ประโยค

A/B Testing in Data Science Interviews by a Google Data Scientist | DataInterview

Business EnglishInterview EnglishUniversity Students
Distributed Task Scheduler: System Design Interview (Stripe & Amazon Offers)C1
8
324 ประโยค

Distributed Task Scheduler: System Design Interview (Stripe & Amazon Offers)

Business EnglishInterview EnglishUniversity Students
What do Design Managers do?B2
1
4 ประโยค

What do Design Managers do?

Business EnglishUniversity StudentsWorking Adults

คำศัพท์และข้อสังเกตด้านการพูดสำหรับบทเรียนนี้

วิดีโอนี้มี 99 ประโยค และ 1305 คำ สำหรับฝึกพูดตาม ช่วงที่มีเสียงพูดยาว 7:02 ผู้พูดพูดเร็ว ประมาณ 186 คำต่อนาที จึงมีการเชื่อมเสียงและลดเสียงค่อนข้างมาก 83% ของคำอยู่ใน 3,000 คำที่ใช้บ่อยที่สุดในภาษาอังกฤษ ส่วนที่เหลือควรดูไว้ก่อนเริ่มฝึก

คำศัพท์สำคัญในวิดีโอนี้

คำที่พบไม่บ่อย 15 คำจากวิดีโอ พร้อมคำอ่านและความหมาย:

  • architecture /ˈɑː.kɪˌtɛk.t͡ʃə/ (คำนาม) — สถาปัตยกรรม. The art and science of designing and managing the construction of buildings and other structures, particularly if they are well proportioned and decorated.
  • dive /daɪv/ (คำกริยา) — ดำ. To swim under water.
  • solve /sɒlv/ (คำกริยา) — แก้, แก้ไข. To find an answer or solution to a problem or question; to work out.
  • scope /skəʊp/ (คำนาม) — ขอบข่าย. The breadth, depth or reach of a subject; the extent of applicability or relevance; a domain, purview or remit.
  • diagram /ˈdaɪ.ə.ɡɹæm/ (คำนาม) — ไดอะแกรม, แผนผัง. A plan, drawing, sketch or outline to show the function or operation of something, or to show the relationships between the parts of a whole.
  • database /ˈdeɪtəˌbeɪs/ (คำนาม) — ฐานข้อมูล. A collection of (usually) organized information in a regular structure, usually but not necessarily in a machine-readable format accessible by a computer.
  • query /ˈkwɪɹ.i/ (คำนาม) — สอบถาม. A question, an inquiry (US), an enquiry (UK).
  • server /ˈsɝvɚ/ (คำนาม) — เซิร์ฟเวอร์. A program that provides services to other programs or devices, either in the same computer or over a computer network.
  • layer /ˈleɪ̯ɚ/ (คำนาม) — ชั้น. A single thickness of some material covering a surface.
  • narrow /ˈnæɹəʊ/ (คำคุณศัพท์) — แคบ. Having a small width; not wide; having opposite edges or sides that are close, especially by comparison to length or depth.
  • objective /ɒbˈd͡ʒɛk.tɪv/ (คำนาม) — เป้าหมาย. A material object that physically exists.
  • fundamental /ˌfʌn.dəˈmɛn.təl/ (คำคุณศัพท์) — พื้นฐาน, เบื้องต้น. Related to a foundation, base, or basis; serving as a foundation.
  • ton /tʌn/ (คำนาม) — ตัน, โตน. The short ton of 2000 pounds (about 907 kg), 20 hundredweights of 100 pounds avoirdupois each.
  • nail /neɪl/ (คำนาม) — เล็บ, เล็บมือ. The horny plate or appendage at the ends of the digits of various animals, including most reptiles, birds, and mammals (both nonhuman and human).
  • wrap /ɹæp/ (คำกริยา) — ห่อ. To enclose (an object) completely in any flexible, thin material such as fabric or paper.

การออกเสียงที่ควรระวัง

ผู้พูดใช้รูปย่อและรูปลดเสียง 15 ครั้ง เช่น you're, don't, doesn't ให้พูดแบบสั้นตามที่ได้ยิน

  • เสียง “sh” และ “zh”: assumption /əˈsʌm(p).ʃ(ə)n/, expectation /ˌɛk.spɛkˈteɪ.ʃən/, justification /ˌd͡ʒʌstɪfɪˈkeɪʃən/, calculation /ˌkælkjuˈleɪʃn̩/, partition /pɑɹˈtɪ.ʃən/
  • คำยาว — ลงเสียงหนักให้ถูกพยางค์: architecture /ˈɑː.kɪˌtɛk.t͡ʃə/, communicate /kəˈmjuːnɪkeɪt/, availability /əˌveɪ.ləˈbɪl.ɪ.ti/, fundamental /ˌfʌn.dəˈmɛn.təl/, complexity /kəmˈplɛk.sɪ.ti/

วิธีฝึกกับวิดีโอนี้

  1. ฟังวิดีโอให้จบหนึ่งรอบโดยยังไม่ต้องพูด แล้วจดคำที่ยังไม่รู้จัก
  2. เริ่มที่ความเร็ว 0.75× พูดตามทีละประโยค แล้วกลับไปใช้ความเร็วปกติเมื่อเริ่มคล่อง
  3. อัดเสียงตัวเองแล้วเทียบกับต้นฉบับ โดยสังเกตคำอย่าง architecture, dive, solve เป็นพิเศษ

ไวยากรณ์ในวิดีโอนี้

โครงสร้างที่ผู้พูดใช้บ่อยที่สุด พร้อมคำพูดจริงจากวิดีโอ:

โครงสร้างในวิดีโอ
Passive voice be + กริยาช่อง 3 — เน้นสิ่งที่เกิดขึ้น ไม่ใช่ผู้กระทำbeing asked · might be linked · is preferred
Relative clauses who / which + อนุประโยค — ข้อมูลเพิ่มเติมเกี่ยวกับคนหรือสิ่งของones that are · APIs, which are · CDN, which is

เทคนิค Shadowing คืออะไร?

Shadowing เป็นเทคนิคการเรียนรู้ภาษาที่ได้รับการรับรองทางวิทยาศาสตร์ พัฒนาขึ้นสำหรับการฝึกนักแปลมืออาชีพ วิธีการนี้เรียบง่ายแต่ทรงพลัง: คุณฟังเสียงภาษาอังกฤษจากเจ้าของภาษาและพูดตามทันที — เหมือนเงาที่ตามผู้พูดด้วยช่วงเวลาห่าง 1-2 วินาที การวิจัยแสดงว่าเทคนิคนี้ปรับปรุงความแม่นยำในการออกเสียง ทำนองเสียง จังหวะ การเชื่อมเสียง การฟังเข้าใจ และความคล่องแคล่วในการพูดได้อย่างมีนัยสำคัญ

เทคนิค shadowing: อ่านคู่มือฉบับเต็มทีละขั้นตอน →