[{"data":1,"prerenderedAt":73},["ShallowReactive",2],{"term-g\u002Fghost-engineer":3,"related-g\u002Fghost-engineer":59},{"id":4,"title":5,"acronym":6,"body":7,"category":40,"description":41,"difficulty":42,"extension":43,"letter":44,"meta":45,"navigation":46,"path":47,"related":48,"seo":53,"sitemap":54,"stem":57,"subcategory":6,"__hash__":58},"terms\u002Fterms\u002Fg\u002Fghost-engineer.md","Ghost Engineer",null,{"type":8,"value":9,"toc":33},"minimark",[10,15,19,23,26,30],[11,12,14],"h2",{"id":13},"eli5-the-vibe-check","ELI5 — The Vibe Check",[16,17,18],"p",{},"A ghost engineer is someone on the team whose contributions are mysterious — they're on standups, they get paid, but nobody can point to a line of code they wrote this quarter. In the AI era, it also describes engineers whose only 'work' is pasting Claude's output into a PR and taking credit.",[11,20,22],{"id":21},"real-talk","Real Talk",[16,24,25],{},"Ghost engineer originally described engineers producing near-zero measurable output while remaining employed. The term has expanded to include engineers whose work is primarily AI orchestration — accepting AI-generated code without deep understanding. Both types are hard to detect in remote teams and cause problems when on-call or debugging production incidents.",[11,27,29],{"id":28},"when-youll-hear-this","When You'll Hear This",[16,31,32],{},"\"We had a ghost engineer for 18 months before anyone noticed.\" \u002F \"Half the new hires are ghost engineers — they can't explain their own PRs.\"",{"title":34,"searchDepth":35,"depth":35,"links":36},"",2,[37,38,39],{"id":13,"depth":35,"text":14},{"id":21,"depth":35,"text":22},{"id":28,"depth":35,"text":29},"vibecoding","A ghost engineer is someone on the team whose contributions are mysterious — they're on standups, they get paid, but nobody can point to a line of code the...","beginner","md","g",{},true,"\u002Fterms\u002Fg\u002Fghost-engineer",[49,50,51,52],"Vibe Coding","10x Developer","Impostor Syndrome","Code Review",{"title":5,"description":41},{"changefreq":55,"priority":56},"weekly",0.7,"terms\u002Fg\u002Fghost-engineer","ul0d24LV62pefa1yG5fMXP_j_nJTi7CFg3or8Kw4XoE",[60,63,67,70],{"title":50,"path":61,"acronym":6,"category":40,"difficulty":42,"description":62},"\u002Fterms\u002F1\u002F10x-developer","Legend says some developers are 10x more productive than average.",{"title":52,"path":64,"acronym":6,"category":65,"difficulty":42,"description":66},"\u002Fterms\u002Fc\u002Fcode-review","general","A code review is when another developer reads your code before it gets merged, looking for bugs, bad practices, or anything confusing.",{"title":51,"path":68,"acronym":6,"category":65,"difficulty":42,"description":69},"\u002Fterms\u002Fi\u002Fimpostor-syndrome","Impostor syndrome is when every developer feels like a fraud who's about to be exposed. 'They're going to find out I have no idea what I'm doing.' Spoiler:",{"title":49,"path":71,"acronym":6,"category":40,"difficulty":42,"description":72},"\u002Fterms\u002Fv\u002Fvibe-coding","Vibe coding is writing software by vibes — you describe what you want to an AI, it writes the code, and you just... vibe.",1776518283763]