Resume and Project Packaging: STAR, README, Architecture Diagrams, a Demo Video, an English Resume
Use the STAR method to turn three repos into resume highlights, round out each with a README and an architecture diagram, record a demo video, and produce an English resume.
Today's Goals
- Turn at least 3 project experiences into resume bullets using the STAR method
- Round out each of three repos with a README that includes an architecture diagram
- Produce an English resume ready to submit directly
Yesterday (D26) you assembled the structure for answering a system-design question โ five minutes clarifying, three estimating, eight sketching, fifteen going deep, five on trade-offs. That question sits in the middle-to-late part of an interview process, and whether you reach it depends on something earlier: the interviewer has to believe from your resume that this person really built something. Today turns three repositories into something they will want to open.
Plain-Language Walkthrough
One insulated flask, two product pages
Search an online store for an insulated flask and two listings come back. The first is titled "stainless steel insulated flask" and the second "keeps above 65C for 6 hours, one-handed lid, 316 food-grade steel." The two flasks may have come off the same line, and the second sells for twice as much and holds readers who click through noticeably longer.
The difference is not the flask, it is whether the page gives numbers that can be checked. "Stainless steel" is a category and says nothing, because every competitor can write it; "keeps above 65C for 6 hours" is a promise that a thermometer at home can disprove, and it persuades precisely because it can be disproved.
A resume is your own product page, and a recruiter's patience while screening is as short as while shopping. "Responsible for developing the agent service" is the stainless-steel flask; "cut wasted generation after a client disconnect from 103 fragments to 6" is the 65C for six hours. A page with no numbers loses the reader in two seconds โ not because they think you cannot do it, but because they have no way to tell you from another thirty resumes saying "responsible for developing X."
The STAR method is about exactly this. It splits an experience into four parts: Situation, Task, Action, Result. Many people treat STAR as a framework for spoken interview answers, and it belongs on the resume first โ every bullet takes the same sentence pattern:
Under (constraint), in order to (goal), I (specific technical action), improving
(metric) from X to Y.Most people can fill the first three blanks and always stall on that Y. And that is exactly the formula's discipline: without a Y, do not write this bullet, write one that can be quantified instead. Better a resume with three hard quantified bullets than eight saying "responsible for," "participated in," and "optimized." Compare the same thing written two ways:
weak: Responsible for developing the agent service's streaming endpoint, optimizing
resource usage.
strong: So the server stops burning tokens the instant a user closes the page, I moved
the disconnect signal from the request object's close event to listening on the
response object, using writableEnded to distinguish a normal finish; the
streaming fragments the server generated in one session fell from 103 to 6,
cutting about 94% of wasted generation.
(Measured locally on one machine in offline mock mode, with the client
disconnecting deliberately after reading 5 fragments.)In the weak one, "optimized resource usage" is self-assessment and the interviewer can only choose to believe it or not; in the strong one, 103 and 6 are facts, and a follow-up only makes it sturdier โ asked how you measured it, you say the self-check script counted how many fragments the server generated; asked why it was 103 before, you say the wrong object was being listened to, so a close fired once the request body was read, was misjudged as a normal request, and generation ran to the end. Surviving a follow-up is a quantified bullet's real value, not looking good.
That parenthetical about measurement conditions is not modesty, it is this chapter's most important thing.
So the formula's difficulty was never phrasing, it is whether you have that Y in hand. The good news is that you do: every lab's self-check output over the past three weeks printed numbers you can use directly, and at the time you read them only as "it works" rather than as resume material.
Interview questions
Walk me through a technical project of yours using the STAR framework.่ฏท็จ STAR ๆณๅ่ฎฒไธไธชไฝ ๅ่ฟ็ๆๆฏ้กน็ฎใ
Common in ChinaCommon overseasBasic#behavioral#star#resume๐ Unlock this chapter to see the answer keys.
Tell me about the most challenging project you have worked on. What made it hard?่ฎฒ่ฎฒไฝ ๅ่ฟ็ๆๆๆๆ็ไธไธช้กน็ฎ๏ผ้พๅจๅช้๏ผ
Common in ChinaCommon overseasDeep dive#behavioral#project-storytelling๐ Unlock this chapter to see the answer keys.
Suppose I open one of your GitHub projects โ what should a good README show me?ๆไปฌ็นๅผไบไฝ GitHub ไธ็้กน็ฎ๏ผไฝ ่งๅพไธไปฝๅฅฝ็ README ๅบ่ฏฅ่ฎฉๆ็ๅฐไปไน๏ผ
Common in ChinaCommon overseasIntermediate#behavioral#documentation#portfolio๐ Unlock this chapter to see the answer keys.
Have you applied overseas? How does an English tech resume differ from a Chinese one?ไฝ ๆ่ฟๆตทๅคๅฒไฝๅ๏ผ่ฑๆ็ฎๅๅไธญๆ็ฎๅๅจๅๆณไธๆไปไนไธๅ๏ผ
Common in ChinaCommon overseasBasic#behavioral#resume#global-market๐ Unlock this chapter to see the answer keys.
