How to Quit Your Developer Job the Right Way
Leaving a job is a skill too. Here's how to resign professionally, transition smoothly, and keep relationships intact.
Leaving a job is a skill too. Here's how to resign professionally, transition smoothly, and keep relationships intact.
Quitting a job is one of the most important career moves you'll make. Done right, it sets you up for success at your next role and preserves relationships that will benefit you throughout your career. Done poorly, it can burn bridges and damage your professional reputation.
Two weeks is the standard minimum, but four weeks is better if you're in the middle of an important project or have significant knowledge to transfer. Check your employment contract for any specific notice requirements.
Document your work, create handoff notes, and offer to train your replacement. Your colleagues will appreciate the consideration, and your manager will remember your professionalism when you need a reference later.
Keep it positive and professional. Thank your teammates, mention specific things you learned, and share your contact information. Avoid negativity about the company or individuals — even if your experience wasn't perfect.
Never burn bridges. The tech industry is small, and you'll cross paths with former colleagues throughout your career. Leaving well positions you for future opportunities and maintains your professional network.
Developer Advocate
Jordan is a developer advocate at DevPass. He writes about open source, developer experience, and career growth.
Join our newsletter for the latest insights on developer hiring, career growth, and building in public.
No spam. Unsubscribe anytime.