technical-interview-prep
Prepare for coding interviews with DSA patterns, timed practice, and communication coaching.
- License 许可
- MIT
- 最近更新
- 2026-11-07
- Stars
- ★ 0
- Forks
- 1
01 前言 Front Matter
- name
- technical-interview-prep
- category
- career
- description
- Prepare for coding interviews with DSA patterns, timed practice, and communication coaching.
03 SKILL.md 正文
Overview
Technical interviews test a specific performance: solving unfamiliar problems aloud, under time pressure, in a constrained environment. It's a trainable skill with a known curriculum. This skill structures preparation around problem patterns (not problem counts), timed practice, and the think-aloud communication that interviewers actually score.
When to use
-
Preparing for software engineering interview loops
-
Refreshing data structures and algorithms after time away
-
Practicing for specific companies known for hard technical screens
-
Improving speed and accuracy under timed conditions
-
Debugging why you're failing technical rounds
Core concepts
-
-
- Patterns over problems. ~15 patterns cover most interviews: two pointers, sliding window, binary search, BFS/DFS, backtracking, heaps, dynamic programming (core patterns), intervals, tries, graphs (union-find, topological sort). Master the pattern's template and recognition cues, not 500 individual solutions.
-
-
-
- The 45-minute performance. Typical structure: 5 min clarifying, 10 min brute force + optimization discussion, 20 min coding, 10 min testing + follow-ups. Practice the full arc, not just the coding.
-
-
-
- Think aloud, always. Interviewers can't score silent brilliance. Narrate: restate the problem, state assumptions, describe the brute force, identify the optimization, then code. Silence is the most common failure mode.
-
-
-
- Clarify before coding. Ask about input sizes, edge cases, and constraints. "Can the array be empty? Are numbers sorted?" These questions signal seniority and prevent wasted work.
-
-
-
- Test your code out loud. Walk through an example input line by line after coding. Catching your own bug in the dry run impresses; the interviewer catching it doesn't.
-
-
-
- Spaced, timed practice. 1-2 problems daily with a timer beats weekend marathons. Track pattern mastery (can you solve an unseen medium in 25 minutes?) rather than total problems solved.
-
Practical workflow
-
-
- Assess the baseline. One timed medium problem, thinking aloud. Identify: pattern recognition, coding fluency, communication, and time management gaps. Prep targets the weakest link.
-
-
-
- Build the pattern curriculum. Order by ROI: arrays/strings/hashing → two pointers/sliding window → binary search → stacks/queues → trees/BFS/DFS → heaps → graphs → DP. 2-3 problems per pattern: one guided, one solo, one timed.
-
-
-
- Learn each pattern's template. For every pattern: the recognition cues ("sorted array + target" → binary search), the code template, complexity analysis, and 2-3 common twists. Write templates from memory until fluent.
-
-
-
- Practice the full performance. Timed 45-minute sessions: clarify → brute force → optimize → code → test → discuss complexity and follow-ups. Record or pair with a partner for communication feedback.
-
-
-
- Add company-specific prep. Research the target company's style (some emphasize DP, others system design or behavioral weight). Adjust pattern emphasis accordingly.
-
-
-
- Do mock interviews. 2-3 full mocks with another human before the real thing. Nothing else replicates the pressure. Debrief each: where did time go, what would you change?
-
-
-
- Taper before the loop. Light review the day before; sleep matters more than one more problem. Warm up with one easy problem the morning of.
-
Common pitfalls
-
-
- Grinding without patterns. Solving 300 random problems builds familiarity, not mastery. Pattern-based study is 3x more efficient.
-
-
-
- Silent solving. Practicing alone in silence, then freezing when asked to narrate. Always practice aloud — it's a separate skill.
-
-
-
- Jumping to code. Coding before clarifying and discussing approach. Interviewers score the discussion as much as the solution.
-
-
-
- Memorizing solutions. Reciting a known solution collapses on any twist. Understand the pattern deeply enough to derive it.
-
-
-
- Ignoring behavioral rounds. Many candidates ace coding and fail culture/behavioral screens. Split prep time accordingly (see interview-coach).
-
-
-
- No complexity analysis. "What's the time and space complexity?" is asked almost every time. Practice stating Big-O confidently for every solution, including tradeoffs of alternatives.
-
04 同仓库更多 Skills
web-scrape
Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open/fetch fails on JS-heavy pages, or when you need clean markdown/structured extraction from a site. Requires FIRECRAWL_API_KEY.
design-taste-frontend
tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML/CSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, "AI-made", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).