Resigning as a Prompt Engineer means walking away from models you've tuned, prompts you've optimized, and a stack that probably only you fully understand. You're not just leaving a job—you're abandoning context windows, custom embeddings, and the institutional knowledge of what works when GPT-4 gets weird at 3 AM.

Open-door vs closed-door resignations

Prompt engineering is a young field. You'll likely cross paths with former colleagues at conferences, on Discord servers, or when your new employer integrates with your old one's API. An open-door resignation signals you'd return if the conditions were right—useful if you're leaving for learning opportunities but respect the team. A closed-door resignation is a clean break, appropriate when the role has become misaligned or you're pivoting hard into research, infrastructure, or a completely different domain. A counter-offer-aware letter addresses the moment your manager asks what it would take to keep you, laying groundwork without burning bridges.

Template 1 — Open-door (signaling you'd return)

[Your Name]
[Your Address]
[City, State ZIP]
[Your Email]
[Your Phone]
[Date]

[Manager's Name]
[Title]
[Company Name]
[Company Address]

Dear [Manager's Name],

I'm writing to formally resign from my position as Prompt Engineer at [Company Name], effective [Last Day, typically two weeks from today].

This was not an easy decision. I've learned an enormous amount here—from building our first few-shot classification pipelines to scaling our RAG system to production. The opportunity to work directly with [specific model or project] has shaped how I think about language models.

I've accepted a role that will let me focus more deeply on [specific area: safety research / multimodal prompting / fine-tuning at scale], but I have tremendous respect for the work we're doing here. If circumstances align in the future, I'd be excited to explore working together again.

Over the next two weeks, I'll document all active prompts, evaluation benchmarks, and edge cases in our [Notion / Confluence / internal wiki]. I'll also make myself available for questions after my departure if the next engineer hits a wall.

Thank you for the trust you placed in me when this role was still being defined. I'm proud of what we built.

Best regards,
[Your Name]

Template 2 — Closed-door (clean break)

[Your Name]
[Your Email]
[Date]

[Manager's Name]
[Company Name]

Dear [Manager's Name],

I am resigning from my position as Prompt Engineer at [Company Name], effective [Last Day].

I appreciate the opportunity to work on [specific project or model], and I've valued collaborating with the team on [mention one concrete achievement: "reducing hallucination rates in customer-facing outputs" or "launching the first production prompt chain"].

I will spend the next two weeks ensuring a smooth transition. I'll complete documentation for all active projects, including prompt templates, system instructions, temperature/top-p configurations, and known failure modes. I'll also hand over access to any external tools, API keys, or evaluation datasets I've been managing.

Please let me know how I can best support the handover process.

Sincerely,
[Your Name]

Template 3 — Counter-offer-aware

[Your Name]
[Your Email]
[Date]

[Manager's Name]
[Title]
[Company Name]

Dear [Manager's Name],

I'm writing to resign from my role as Prompt Engineer at [Company Name], with my last day being [Last Day].

I've accepted another offer, but I want to be transparent: the decision came down to [specific factor: access to larger model budgets / opportunity to work on alignment research / ability to publish findings / equity structure]. I'm sharing this not to invite a counter-offer, but because I respect you and want to be direct about what drove the decision.

I'm grateful for the autonomy you gave me to experiment with [specific technique or project], and for your support when [mention a specific moment: "our first production prompt failed spectacularly" or "we had to rebuild the entire evaluation pipeline"].

Over the next two weeks, I'll create a transition document covering:

  • All active prompt templates and versioning history
  • Model configuration settings and why we chose them
  • Known edge cases and mitigation strategies
  • Contact info for external vendors or API support

I'll also block time for pairing sessions with [name of person taking over], if that's helpful.

If you'd like to discuss what might have changed the calculus, I'm open to that conversation—but I want to be clear that I've already committed to the new role and signed an offer letter.

Thank you for everything.

Best,
[Your Name]

Industry handover notes for Prompt Engineers

  • Prompt versioning history: Leave a Git repo or tagged document set showing which prompts worked, which failed, and why. Include A/B test results if you ran them.
  • Model quirks and workarounds: Document temperature/top-p sweet spots, which models handle multi-turn context better, and any undocumented API behavior you've discovered.
  • Evaluation benchmarks: Share your test suites, golden datasets, and the thresholds you used to decide when a prompt was production-ready.
  • Access credentials: Hand over API keys, fine-tuning dashboards, and any third-party tools (LangChain, Weights & Biases, logging platforms).
  • Failure mode catalog: List the edge cases that break your prompts—unusual user inputs, encoding issues, or adversarial examples—so the next person doesn't rediscover them the hard way.

The exit interview — what to say, what to skip; whether honesty actually changes anything

Exit interviews for Prompt Engineers often come from HR, not your direct manager, and they're trying to understand whether the company is losing talent for fixable reasons. If you're leaving because you weren't given access to newer models, or because leadership didn't understand the difference between prompt engineering and data labeling, it's worth mentioning—it might influence how they hire or resource the next person.

What to skip: grievances about specific people, complaints that sound like you didn't understand the business constraints, or rants about how "nobody gets LLMs here." If you burned out because you were asked to do excuses to leave work early three times a week to cover production incidents, frame it as a resourcing issue, not a personal failure.

Does honesty change anything? Sometimes. If you're the third Prompt Engineer to leave in six months citing the same issue—model budget, lack of research time, being treated as a cost center—that data might reach someone who can fix it. But if you're the first or only one, expect polite nodding and no follow-up.

Be specific. "I needed more experimentation budget" is better than "I felt undervalued." If you can quantify what would have kept you—weekly research hours, access to GPT-4 fine-tuning, or a clear path to publishing—say so. The company may not act on it, but at least you've left a trail for the next engineer.

Stop scrolling job boards. Sorce shows you matches; you swipe; we apply. 40 free a day.

Related: Medical Assistant resignation letter, Medical Coder resignation letter, Prompt Engineer cover letter, Prompt Engineer resume, Sales Representative resignation letter