RecruitLingo

Help me work out whether this candidate's technical background genuinely transfers to the role I'm hiring for. WHAT THE ROLE USES: {{languages, frameworks, infrastructure, scale, domain}} WHAT THE CANDIDATE HAS DONE: {{paste the relevant resume sections — stack, projects, scale, years on each}} HOW MUCH RAMP-UP THE TEAM CAN REALISTICALLY ABSORB: {{e.g. "they need to ship in month one" / "we can invest a quarter"}} Tell me: 1. Which parts of this background transfer almost directly, and why. 2. Which parts look similar on paper but are genuinely different in practice — the traps where a recruiter assumes equivalence and an engineer doesn't. 3. What they'd have to learn, and a realistic ramp estimate for each, assuming a competent engineer. 4. Whether the gap is about a tool, which is learnable, or about a way of working — scale, domain, testing culture, operating in production — which is much slower to acquire. 5. Two questions that would tell me quickly whether the transfer is real, and what a convincing answer sounds like. 6. How to make the case to a sceptical hiring manager, in three sentences, honestly stating the risk rather than talking around it. If the honest answer is that this doesn't transfer, say so plainly.