跟讀練習: 3.3k - 通過影片學習英語口語

選擇練習模式

每種模式都會開啟全屏練習室。

101 句

如果句子過短或過長，請點選 Edit 進行調整。

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.

下載應用

流利口語所需的一切

AI 發音評分逐句打分

音標練習掌握每個音

詞彙學習建立你的詞庫

詞彙遊戲邊玩邊學

掃碼

Download on theApp Store Get it onGoogle Play

FOR YOU

關於本課

在本課中，學習者將會探索如何有效地準備高頻交易軟體開發工程師的面試。通過影片中的個人經驗分享，學習者將瞭解到自學的重要性以及如何通過合理的資源選擇提高英語水平和麵試技巧。通過這種方式，學習者能夠在準備事業、提高英語發音和麵試能力方面更加自信。

關鍵詞彙與短語

自學 (Self-study)
面試 (Interview)
作弊 (Cheating)
推薦 (Referral)
高頻交易 (High Frequency Trading)
資料結構 (Data Structures)
併發 (Concurrency)
讀書 (Reading)

練習技巧

為了提高英語口語能力並更好地掌握這一材料，建議學習者在觀看影片時進行影子跟讀。具體來說，您可以嘗試以下方法：

在觀看影片時暫停，重複影片中講解者的每一句話。儘量模仿語音的語調和節奏，這將有助於改善您的發音。
將影片速度調至速度適中（如0.75倍速），確保您可以清晰跟上講解內容並準確理解。
將某些複雜的詞彙或句子進行分解，逐步練習並提高自己的表達能力和信心。
在反覆練習時，可以加入個人的理解或示例，使學習更具互動性。

運用這些技巧，並結合使用shadow speak和相關的學習網站，您將能夠
有效提高英語口語流利度和發音準確性，給未來的面試帶來更大的成功機會。

影片中的語法

說話人最常用的結構，並附上影片中的原話：

結構	影片中的用法
現在完成時 have/has + 過去分詞 — 過去發生但與現在仍有關聯的事	I've been · have optimized · have learned
被動語態 be + 過去分詞 — 強調發生了什麼，而不是誰做的	be blown · are actually outdated · can be written

什麼是跟讀法？

跟讀法 (Shadowing) 是一種有科學依據的語言學習技巧，最初開發用於專業口譯員的培訓，並由多語言者Alexander Arguelles博士普及。這個方法簡單而強大：您在聽英語母語原聲的同時立即大聲重複——就像是一個延遲1-2秒緊跟說話者的影子。與被動聽力或語法練習不同，跟讀法強迫您的大腦和口腔肌肉同時處理並模模擬實的講話模式。研究表明它能顯著提高發音準確性，語調，節奏，連讀，聽力理解和口語流利度——使其成為雅思口語備考和真實英語交流最有效的方法之一。

影子跟讀法: 閱讀完整分步指南 →

跟讀練習: 3.3k - 通過影片學習英語口語

選擇練習模式

下載應用

推薦影片

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

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

Secrets to Breaking into Private Equity (Insider Tips Revealed!)

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

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

Financial Analyst: Top 3 Interview Questions & Answers

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

Data Structures Explained for Beginners - How I Wish I was Taught

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

I learned 3 languages to C1 with a 30-minute routine, so you can just copy me

10 JavaScript Interview Questions You HAVE TO KNOW

Mastering iOS Development: Mock Interview with Ramiro Neto

關於本課

關鍵詞彙與短語

練習技巧

影片中的語法

什麼是跟讀法？