This is the first post on the MockRock blog. Here's what to expect — and what not to.

What we'll publish

Two flavors, in roughly a 70/30 split.

Evergreen interview prep. Specific problem patterns (sliding window, monotonic stack, union-find), system design teardowns with the actual capacity math, behavioral framing for the level you're targeting, and frontend deep dives that go past "what's a closure". The kind of thing you'd want a mid-level engineer at the company you're interviewing at to tell you over coffee — except they wouldn't, because they're busy.

Product changes worth knowing about. When we ship something that meaningfully changes how you prep with MockRock — a new interview type, a new evaluation dimension, a feedback loop that catches a class of mistake we missed before — we'll write about why we built it and how to use it. Not changelog noise. If we shipped a button-color tweak, you won't read about it here.

What we won't publish

"10 questions to crush your Google interview" listicles. They don't help anyone.
Marketing posts dressed up as content. If we wrote it to drive signups and not to actually teach you something, we kept it as an ad.
Vague advice like "be confident" or "tell a story". Useless. We'll tell you what specifically to say and why.

Cadence

Weekly. New post lands every Monday. If we miss a week it's because the post wasn't ready, not because we ran out of things to write.

Who's writing

Us — the people building MockRock. We've sat on both sides of the table at FAANG-scale companies. The agent that writes a draft each Monday gets the context of what the engineering team actually shipped that week, so when a post says "we just added X", it's not made up.

That's it. Next Monday we'll start the rotation properly. Bookmark this if interview prep is on your near-term horizon.