Learning and careers decision

Mockingly.AI

A single skilled developer can reproduce a useful subset (canvas + LLM interviewer + basic scoring) in a few weeks, but matching the curated question bank, tuned scoring, and production polish of the paid product is costly and time-consuming.

Visit website
You pay

Not priced

No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.

You’d pay instead

$100one-off82 h to build

$120/mo6 h/mo upkeep

No published price to break even against.

No open-source build does this yet

Nothing published replaces this one, so a replacement starts from an empty file. Here is what it would have to cover.

What a replacement has to do

  • User picks a real interview question, draws an architecture on an interactive canvas, converses with an AI interviewer that issues follow-ups, then receives an automated readiness score and feedback.

What it still won’t have

  • Large curated question bank and company-specific historical questions
  • Polished prompt engineering and tuned scoring models
  • Priority support, early-access features, and a maintained content library
  • Brand polish and UX refinements of the production product

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

No published price

Mockingly.AI does not publish a price we could read, so there is nothing to compare against. What building costs is below.

Money you would actually spend

Keep paying
—

Subscription price × seats × 12

Build it
—

AI build —APIs + hosting —

Time you would spend

—

—

What you would spend

What we assumed

The verdict above measures whether you could build it. This one is only about money.

Runnable build prompt

Not run yet
Build a minimal AI-backed system-design interview practice app using Next.js for the frontend, Node/Express for the API, Postgres for persistence, and a hosted LLM (OpenAI-compatible) for the interviewer. Core features in scope: (1) an interactive diagram canvas (use an existing JS diagramming library), (2) question bank with tagging and company filters, (3) LLM-driven interviewer that streams follow-up questions and records session transcript, (4) automated post-session analysis that produces a readiness score and bullet feedback, (5) user accounts and Pro subscription via Stripe, (6) session history retrieval. Out of scope: building or training new LLMs, large-scale multi-tenant optimization, and mobile-native apps. Include sensible error handling, logging, and unit/integration tests for API endpoints and analysis logic.
How we checked2 sources · 3/3 runs agreed · evidence score 57

How the score was reached

  • Partly verdict base52
  • 2 cited sources+1
  • 3/3 assessment runs agreed+4
  • Evidence score57

The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.

How scoring works →

Cited sources · 2

Every page the run actually retrieved.

Integrity checks

What held up, and what did not.

✓ 3 independent runs, one answer✓ Citations limited to fetched pages! 1 moat recorded