Obsidian Interview Vault vs Chrome Side Panel Practice
Almost every serious candidate builds some kind of interview vault—an Obsidian (or similar local markdown) workspace with company research, STAR stories, system-design checklists, “questions to ask,” and links to problems. Beside that sits another habit: Chrome side panel practice—a calm panel open next to the pad while you rehearse narration, freeze recovery, and timed prompts.
Neither is wrong. The useful question is narrower: when does a carefully built Obsidian interview vault beat Chrome side-panel practice—and when does the reverse happen?
This is a workflow comparison, not a feature checklist. Plugins, graph views, and note templates change. What stays stable is the difference between reference material you curated and linked and performance under interview-shaped constraints.
At a glance
| Category | Obsidian-style interview vault | Chrome side panel practice (Luna optional) |
|---|---|---|
| Session shape | Read, link, organize, daily notes | Timer + narration + recovery beside a pad |
| Structure | Markdown notes, backlinks, tags, MOCs | You impose live rules on one prompt at a time |
| Feedback | None until you review yourself or share | Self-postmortem under time; optional peer later |
| Environment fidelity | High for “what I want to remember and connect” | High for “what I will do when the pad is blank” |
| Best for | Story banks, company notes, pre-round checklists, concept maps | Transfer, freeze recovery, audible plans |
| Main tradeoff | Easy to polish the graph instead of performing | No durable knowledge base unless you write one |
What an Obsidian interview vault looks like
A typical well-kept candidate vault:
- You create notes per company or per loop stage (recruiter screen, behavioral, coding, onsite), often linked from a Map of Content.
- You store STAR stories, metrics, and “failure” variants you can reuse, with tags by theme.
- You add checklists: clarify requirements, state complexity, dry-run cases, questions for the interviewer.
- You paste links to problems, design templates, and logistics notes; you may maintain a daily note during the loop.
- The night before, you open a graph or MOC and skim. On game day you hope the right link rises when you need it.
Honest strengths. External memory matters—and local markdown with backlinks is excellent at it. Interviews punish candidates who cannot find their own conflict story or forget the clarifying questions they meant to ask. Obsidian shines for versioning stories, connecting a behavioral theme to a related system-design note, and keeping company research out of chat threads. For multi-week loops across several employers, a vault is often the difference between calm and chaos. Offline access and plain files also beat fragile web tabs for some people.
Honest limits. Reading is not retrieval under pressure. A beautiful graph of “graph algorithms” notes does not make you narrate BFS on a blank pad. Candidates often spend Sunday tuning plugins, CSS snippets, and MOCs and skip the uncomfortable twenty-five minutes of timed code. Vaults also tempt last-minute cramming of walls of markdown you will never say out loud. Link gardening can feel like deep work when it is really avoidance.
When an Obsidian interview vault wins: you need a durable story bank and company research, you juggle multiple loops, you think in linked notes, or your bottleneck is organization and recall of facts you already practiced—not live freeze on the pad.
What Chrome side panel practice looks like
Chrome side-panel practice is the opposite polarity: less archive, more reps.
- Pick one prompt (behavioral or coding) from a short list—not from a fifty-note wiki.
- Open the surface you will actually use (shared doc, CoderPad-style editor, plain notepad) in the browser or beside it.
- Start a timer. Restate out loud. Keep a calm practice side panel beside the workspace if you use one.
- For coding: two-line plan before code, forced freeze once, three dry-run cases.
- For behavioral: deliver once under a hard timebox, cut filler, rewrite the punchline.
- One-sentence postmortem. Optionally jot one durable note back into Obsidian—not a transcript dump.
Optional companion: Luna Interview is a Chrome extension framed as a practice / calm side panel—not a substitute for knowing the material, and never an “undetectable” live cheat. The panel sits beside the pad while you own the answer and the voice track.
Honest strengths. Transfer. Offers go to people who can restart out loud when the editor is empty—not to people with the prettiest graph. Side-panel practice trains attention management: notes nearby without turning the session into open-book theater. Volume is high: three short live blocks beat one evening of rearranging folders. Browser-native practice also matches many real interview surfaces (shared docs, web IDEs).
Honest tradeoffs. Without a vault, you reinvent stories and lose company research. Pure live practice can become random thrashing if you never write down which stories work. A side panel also requires honesty—if you paste full solutions mid-drill, you are not training transfer. If your interviews are mostly desktop-only pads with no Chrome, you still need to practice on that surface; the panel is a practice companion, not the interview itself.
When Chrome side-panel practice wins: your interview is soon, your bottleneck is freeze / silence / weak dry-runs, or your Obsidian vault is already “done” and you are still underperforming in mocks.
Decision table for candidate situations
| Your situation | Prefer Obsidian-style interview vault | Prefer Chrome side panel practice |
|---|---|---|
| Many companies; stories keep colliding | Strong fit—tag, link, and version | Light practice after stories are stable |
| Freeze on blank pad; vault is huge | Maintenance only | Strong fit—timer + narration |
| Stories exist only in your head | Build the vault first | After three stories are written |
| Interview tomorrow; content ready | One-page skim note | Pad-shaped triage + freeze loop |
| Love organizing / graphing more than performing | Cap vault time; schedule live blocks | Primary weekday lane |
| Need a shareable packet for a coach | Export or PDF from notes | Record a live session instead |
| Keep rewriting the same note | Freeze the vault; practice from it | Strong fit—stop polishing |
A fair practical method (try both in one week)
Do not treat the vault as the interview, or the side panel as a knowledge base.
Vault day: Build or trim a one-page skim note: three stories with punchlines, five clarifying questions, two pattern families you will drill. Archive the rest behind a MOC link so it cannot distract you mid-week. Resist new plugins for that day.
Live practice days (next 3–4 sessions): Run prompts from that skim note only. Timer on. Keep a calm practice side panel beside the pad if you use Luna. After each session, allow yourself one durable edit to Obsidian (a better punchline or a missed clarify)—not a full graph rewrite.
Compare: did the vault change what you practiced, or did it only absorb hours that should have been audible? Many candidates keep a lean Obsidian vault for memory and spend most prep minutes in live constraints beside Chrome.
Common mistakes / when NOT to use each
Skip vault-as-progress when you are formatting, linking, or theming to avoid speaking. A two-hundred-note interview wiki with zero timed pads is a common false summit. Also skip dumping entire solution banks into Obsidian and calling that “prep.”
Skip side-panel theater when you have no story bank and no shortlist of patterns. Live drills on random prompts still miss the loop you booked. Also skip any framing that promises stealth tools in a real employer interview—that is the wrong goal and the wrong integrity bar.
For both: notes and AI are for study blocks and postmortems, not for mid-“live” rescue if you are training transfer. The skill is retrieving your structure under time.
Soft close
If your bottleneck is calm practice beside the pad you will actually use—timed prompts, narration, freeze recovery—Luna Interview is a Chrome side panel built for that practice loop, not for cheating or replacing study. Soft trial path: https://lunainterview.xyz/
Use an Obsidian interview vault when organization, story banks, and company research are the bottleneck. Use a Chrome side panel when performance under interview rules is the bottleneck. The offer goes to the candidate who can restart out loud in their editor—not the one with the most nested backlinks.
Rehearse with an AI interview copilot, then browse commonly reported interview questions.