ฝึกพูดภาษาอังกฤษด้วยเทคนิค Shadowing จากวิดีโอ: 3.3k

Today I'm going to share with you the complete Self-Study Guide to High Frequency Trading SDE interviews.

I'm not here just to tell you to LeetCode and read C++ books.

I had to self-study most of the topics here myself, and I was able to get into tier one trading companies this year.

So I want to share specific resources and which chapters are most frequently asking in views and you must read and which chapters you can really safely skip before we start.

No one, not even the smartest quant in your Discord servers can remember everything.

So tip one, as you study, make your own cheat sheets.

When interviews are close, you can just skim through them instead of rereading entire books or even your highlights.

This will save you from many pre-interview breakdowns.

And tip two, prefer books to videos or vlogs.

Why? Because books are peer reviewed.

And easy to create cheat sheets from.

If you have the digital copy, you can just copy the text directly into your one note page.

And let's be honest, no recruiter is gonna be blown away by your Coursera certificate collection if your student also definitely take the relevant courses if your school offers them.

And lastly, what if one studies but can't get interviews?

I've been there too.

The good news is that there are many ways to boost their chances from how I systematically ask for referrals to how I format my resume in an eye catching yet ATS friendly way to how I have optimized LinkedIn so that recruiters find me instead of the other way around.

I have a full framework for that, and if you want me to make a separate video, drop a comment, say, interview and subscribe to get notified.

Here's the juicy part you've been waiting for first.

Algorithms Aim for around 1900 rating on LeetCode's weekly contests.

Obviously Without cheating, with ChatGPTs, it might take you a year and 200 to 500 questions, so do it concurrently with the other topics the contests have got harder in recent years.

As a matter of fact, the gold standard to get into Google in the past was 2100 in LeetCode contests.

Topic number two C++, which should take you four months in total.

And if you're in the Python track, just skip to the Python section first.

Skim through the latest edition of a tour of C++.

This is the third edition by Bjarne Stroustrup.

Makes sure you understand the big four features of C++ 20.

These are the specific chapters that you should read and the rest you should be safe to skip.

If you do use C++ or have learned it in school, the next resource is obviously Scott Meyers' effective series.

The first one I recommend from it is Effective C++ third edition.

A good number of the principles here are actually outdated, but the rest are very, very useful to read.

And the more up to date book, that would supplement the previous one is effective modern C++, more geared towards C++ 11 and 14.

Scott is no longer writing books.

That's why we have to, refer to a tour of C++ now that you know how to actually write good C++ code, you can also read this book, which nobody else on the internet, I believe has talked about.

It's called a hundred Interview Questions It goes from basic concepts like.

Reference versus pointer to really advanced interview questions like type erasure, that I did get asked in interviews.

I love that book.

And the next one, daily C++ interview.

Some people have talked about it.

It's a pretty decent book.

Both of these two are Kindle books that you can actually.

Read on your phone during bathroom breaks while waiting for meeting to start, or just as bad time readings like I used them for quick bites to keep you sharp basically.

And finally, read through and implement STL constructs like smart pointers.

Data structures like vectors.

Understand how they actually work under the hood and being able to reinvent efficient wheels set you apart from most candidates.

Comment, STL to vote for a video on that.

The next topic is concurrency, which should take you a month, I believe, C++ concurrency Action.

Is obviously the book I would recommend.

I think chapter five, the most important one can be written better, but the consensus is that this is the best we've got on concurrency so far.

And if you on the Python track , you can read this famous book called Fluent Python.

I personally am not on a Python track, but I have read the book.

Because I use Python a lot at work and I have learned a ton by reading it.

The book is a bit dry, so plan to spend two to three months on it.

The next topic is computer networking.

A top down approach you would probably need to spend two months on it, on chapters 1 to 5.

This is the computer network in textbook at Stanford.

And it's very easy and fun to read and you sort of see parallels between computer networking and social networks.

I know I did.

And studying networking helps us ease any existential crisis in, in fact . More importantly, networking is everywhere in HFT, latency, package drops, all that jazz.

So it really pays off even if you're not interviewing.

And the next topic, operating system will take two week, uh, two months, this is a great book many people have mentioned and sworn by.

Operating systems.

Three easy pieces.

The OS textbook at Wisconsin Medicine, it works you through OS concepts compactly, but effectively to understand how your system jiggles processes and memory.

So read these two parts, virtualization and concurrency.

The disk part is very, very rarely asked.

It's actually never asked in my experience.

Computer architecture will take you another two months.

You gotta study caching, branch prediction and memory hierarchies.

This mean a lot in HFT where nanoseconds count.

The book that people really swear by is Computer Organization and Design by Peterson and Hennessy.

I personally have not read it and just reviewed the slides from my college courses.

And here comes system design, which you probably will spend three months on.

In fact, new grads have been asked system design questions for eons.

So I don't know why some people say system designs are not applicable to HFT interviews.

I got asked them all the time.

But for HFT.

System design isn't only how you build Facebook.

It's also how you process millions of packets per second without burning through cache lines.

I call them low level system designs.

Think caching, network latency, throughput.

Start with the classic design data intensive applications.

I actually read the book like four times and talked to the author more than once.

Then you can go lighter with Alex Xu's System design series.

He has two books right now, volume One, second Edition, and Volume two.

At least read the volume one in my opinion.

And behavioral questions will take you, I believe, three days.

Do not underestimate this.

Most people think that quant or trading SDE interviews are purely technical.

But behavioral questions decide whether they will trust you in the pod.

If you want me to drop a high quality BQ cheat sheet, just comment bq.

And lastly, math and stats.

This is commonly referred to as the Green Book, but math and Stats are only asked about 10% of the time in SDE interviews and the candidates with a good math foundation can pass the asked questions pretty easily anyway, so I don't consider it mandatory, but it could be very helpful if you have the time to spare.

So that's the roadmap.

Remember, it's not about memorizing everything.

It's about building mental frameworks and creating your own reference sheets that let you review efficiently until you get a chance to use the learned knowledge in real work.

I'm organizing my own cheat sheets one by one.

So please subscribe and stay tuned.

Please also hit the like button.

It fuels the YouTube algorithm and my dopamine levels equally.

100

Let me know what rabbit hole I should dive into next.

101

Until then, happy studying and may constant runtimes be with you.

✨ วิดีโอแนะนำ

22 ประโยค

I'm an ex-Google interviewer. You're doing LeetCode wrong.

Business EnglishInterview EnglishUniversity Students

190 ประโยค

🔥Launching Analog VLSI Mastery : Cohort (0-100) || A Complete Placement Guide || Himanshu Agarwal

Business EnglishInterview EnglishUniversity Students

187 ประโยค

What It Really Takes to Become a Full-Time Day Trader at 21

Business EnglishInterview EnglishUniversity Students

674 ประโยค

FULL Data Science Mock Interview | SQL, Statistics, Business

Business EnglishInterview EnglishUniversity Students

26 ประโยค

🔥 Java Multithreading Rapid Fire | Can You Answer These Interview Questions? #shorts

Business EnglishInterview EnglishUniversity Students

196 ประโยค

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

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

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

ฝึกพูดภาษาอังกฤษด้วยเทคนิค Shadowing จากวิดีโอ: 3.3k

I'm an ex-Google interviewer. You're doing LeetCode wrong.

🔥Launching Analog VLSI Mastery : Cohort (0-100) || A Complete Placement Guide || Himanshu Agarwal

What It Really Takes to Become a Full-Time Day Trader at 21

FULL Data Science Mock Interview | SQL, Statistics, Business

🔥 Java Multithreading Rapid Fire | Can You Answer These Interview Questions? #shorts

I cloned 3 apps and now make $35K/month

Financial Analyst: Top 3 Interview Questions & Answers

13k

Emirates Cabin Crew Interview in 2026: The Secret Scoring System REVEALED

How I Escaped Help Desk Fast (Step-by-Step)

Phone Interview with a Recruiter

Claude Code: The Advanced Guide (99% of Devs Skip These Features)

ทำไมต้องฝึกพูดกับวิดีโอนี้?

ไวยากรณ์และการใช้สำนวนในบริบท

กับดักการออกเสียงที่พบบ่อย

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