Example 1 · Backend engineering · scored 76 · not moved forward
Senior Backend Engineer · 7 yrs Python + Go · Bangalore
What stood out
Strong operational ownership. The on-call rotation fairness framework you built — and the way you described facilitating the customer-facing-outage postmortem — are exactly the signals this role asked for. Your Postgres partitioning migration on a 500M-row table with zero downtime is the kind of evidence most candidates can't produce.
Where we'd want to see more
Distributed-systems judgment came across thinner than the role weighted it (25% of the rubric). Your answers didn't reach into message-queue failure modes, consistency trade-offs, or async coordination — and the role explicitly needs that. Observability was also a notable gap; the JD called it out as a separate dimension, and your résumé didn't surface specific instrumentation work.
Outcome
We're not moving forward this time. If you want to apply again in 6 months with a distributed-systems case study attached, we'd genuinely welcome it — your backend depth is real, the gap is on a specific axis you could address.
Score breakdown: Backend Craft 85 · Operational Ownership 88 · Distributed Systems 58 · Mentorship 78 · Observability 52
Example 2 · Growth marketing · scored 81 · shortlisted
Head of Growth · 5 yrs B2B SaaS · Pune (remote)
What stood out
Operator instincts — your "we cut paid search 40% to fund cold-outbound and acquisition cost dropped 28%" story shows you're not married to a channel. The way you described running an attribution audit before reorganizing the funnel maps to exactly the kind of judgment this role needs.
Where we'd want to see more
Content engine experience is thin. The role weighs content-led growth at 20% of the rubric, and your examples leaned hard on paid + outbound. We'd want to verify in the live round whether content was something you owned or delegated to someone else.
Outcome
We're moving forward. You'll get a Cal.com link from name removed within 24 hours. Briefing the interviewer to spend most of the time probing the content question — the rest of your profile is clearly strong.
Score breakdown: Acquisition Strategy 88 · Paid Performance 85 · Content & SEO 65 · Analytics & Attribution 84 · Founder-mode Operating 84
Example 3 · Product design · scored 64 · not moved forward
Senior Product Designer · 6 yrs · Gurgaon
What stood out
Polished portfolio — the financial dashboard work shows strong information hierarchy and a real point of view on data density. Your case study on the SMB onboarding flow demonstrates you can write about your process clearly, which is rarer than it should be.
Where we'd want to see more
Two specific gaps. First, this role was for a 0→1 environment — your portfolio is heavy on optimization of existing surfaces (50%+ improvements to retention, conversion, etc.). We didn't see early-stage ambiguity work where you defined the problem. Second, the role asks for design-engineering proximity, and you didn't surface examples of pairing with engineers on implementation trade-offs.
Outcome
We're not moving forward. Honest read: your portfolio is genuinely strong for a Series-B+ product team. This particular role needed 0→1 instincts that didn't show up in your evidence. We'd encourage you to apply at growth-stage companies where your strengths are the actual fit.
Score breakdown: Visual & Interaction Craft 82 · Information Architecture 80 · 0→1 Product Sense 38 · Design-Engineering Collaboration 54 · Strategic Storytelling 72
Why we share these
Most hiring tools treat rejected candidates as a cost center. We treat them as the people most likely to recommend you to their friends — if the rejection is honest and specific. The LLM cost to produce a report like the above is around ₹2. The reputational cost of "we'll keep your résumé on file" is much higher.
Three things we will never do:
- Hide the score. The candidate sees the number and the dimensions behind it.
- Generate without evidence. Every claim cites a quote from their own résumé or interview answer.
- Pretend the AI made the call. The "outcome" line says "we're moving forward" or "we're not" — the human signed off.
If you publish a Lucida-scored role, you're committing to this. There's a checkbox in the onboarding flow that asks you to confirm it.