Portfolio and writing
Build logs, characterization reports, reproduction write-ups, one-page memos, a poster, a personal site. Engineers who can write a clear page get promoted, and a resume cannot show judgment where a write-up can.
You are skimming: the title, the first figure, and the short version. Switch to Read in the header for the full page, or Deep to open every deep dive.
A resume says “designed an eight-channel EEG amplifier.” A build log shows the schematic, the noise floor with its bandwidth, the mistake that cost a week, and the sentence that says what you would do differently. Professors and recruiters read the second kind of thing, and almost no student produces it. The portfolio is the compound interest of this whole site: every project produces a document, and the documents accumulate into the thing that gets you hired.
The five documents
The build log. Every project. The template is in the build logs section: what I set out to do, what I did, what went wrong, what I measured, what I would change, what surprised me. Photos of failures. Written the week the project ends, while the failures are fresh.
The characterization report. Every instrument. One page, numbers with units and conditions, a plot per number. The Phase 2 page has the template.
The reproduction write-up. Every paper you reproduce. Their number, your number, the gap, and why. The Phase 3 page.
The one-page memo. For anything you want someone to decide: a proposal to a lab, a request for equipment, a recommendation to a team. State the decision needed in the first line, the reasoning in three paragraphs, the ask at the end. Engineers who can do this get put in front of people who decide things.
The poster. By junior year, at least one. Big figures, few words, a title that states the result. Practice presenting it in two minutes and in ten.
The site
Put all of it on a personal website: a page per project, a page for the characterization reports, a page for the reproductions, and a short about page with your spine and what you want to work on. A static site generator (this site is Astro; Hugo and Jekyll are fine) and a free host. Own the domain. Link it in every email to every professor and every application. When a recruiter searches your name, this is what they should find.
Keep other people’s data off it. Recordings from friends stay in the protocol’s storage, not on the web.
Writing well, the short version
Lead with the result. One idea per sentence. Numbers with units. Say what went wrong. Cut every adjective that is doing the work a number should do. Read it aloud once. The about page describes the voice this site uses; it works for your write-ups too, and the field-notes register (first person, honest, specific) is exactly right for a build log.
Talks
The NeurotechX club meeting, the lab meeting, the undergraduate symposium. Ten minutes on what you built, with the failures included. Every talk you give makes the next one easier and puts your name in a room.
- Set up the personal site this month, with one build log on it.
- After every project, the build log within a week.
- After every instrument, the characterization report.
- Practice the one-page memo the first time you need something from a lab.
- Junior year: a poster and a talk.