Software Engineer Career Change Resume (Bootcamp or Self-Taught)

For an entry-level developer, a hiring manager usually wants answers to three questions. Can this person actually write and ship code? Can they work with other people and take feedback? Will they stay and keep learning? Your resume has to answer all three, and most of the answer to the first one comes from your projects, not your old job titles. Your previous career helps with the second and third. Someone who spent six years as a pharmacy technician, a warehouse supervisor, or a teacher has already shown up on time, handled pressure, and worked with difficult people. That is worth including, but it belongs below the technical proof, not above it. Avoid apologizing on paper. Phrases like "aspiring developer" or "looking for an opportunity to break into tech" tell the reader you are not one yet. If you have built and deployed applications, you are a junior developer who is new to the profession. Write like one.

For most career changers, the best order is: header, short summary, technical skills, projects, work experience, education and training. This is a combination layout. It leads with what is most relevant and still shows a normal work history, so it won't look like you are hiding something. In the header, include your name, city and state, phone, a professional email, your GitHub profile, and a portfolio link if you have one. Make sure those links work and that the first things a visitor sees on GitHub are your best two or three projects, each with a README that explains what the project does and how to run it. A recruiter who clicks through to an empty or messy profile will assume the resume overstated your skills. Keep it to one page unless you have a long, relevant history. Most career changers can do this by trimming old job bullets that have nothing to do with the new role. If your education section is just a bootcamp, it takes only a few lines.

Your summary should be two or three sentences: what you are, what you build with, and one thing from your past career that carries over. For example: "Full-stack developer with a 12-week software engineering bootcamp certificate and four deployed projects built with JavaScript, React, Node.js, and PostgreSQL. Six years of experience in logistics coordination, with a habit of documenting processes and fixing problems at the source. Looking for a junior developer role on a team that values code review and mentoring." It names real technologies, mentions the training once, and ties the old career to the new one without a long explanation. Skip adjectives like "passionate" and "motivated." For skills, group them so they are easy to scan: Languages (JavaScript, Python, SQL), Frameworks and Libraries (React, Express, Flask), Tools (Git, GitHub, Docker, Postman), Databases (PostgreSQL, MongoDB). Match the wording to the job posting where it is true for you. If a posting asks for "REST APIs" and you have built them, say "REST APIs," not just "backend development." Only list what you could discuss in an interview. If you did one tutorial in Docker, it is better left off or labeled honestly than listed beside languages you use daily. Some people split the list into "Proficient" and "Familiar" to be clear about the difference.

Projects are your experience section in everything but name, so give each one real space. For each, list the project name, a one-line description, the technologies, and a link to the live site or code. Then write two to four bullets covering what you built, the problems you solved, and any results you can state truthfully. Weak: "Built a to-do app using React." Stronger: "Built a task-tracking web app with React and Node.js that lets users create accounts, set due dates, and receive email reminders; deployed on Render with a PostgreSQL database." More bullet examples, with the numbers replaced by your own real ones: - Designed a REST API with 12 endpoints and wrote automated tests with Jest covering the main user flows. - Fixed a bug that caused duplicate orders when users double-clicked submit, by adding server-side validation. - Collaborated with three bootcamp teammates in two-week sprints, using Git branches and pull requests to review each other's code. Team projects are especially valuable because they show you can work in a shared codebase. Say what your part was. Avoid listing five tutorial clones that look the same as everyone else's. One or two projects that solve a real problem, even a small one for a friend, a local business, or your old workplace, will stand out more than a long list of copies. If you can say "used by 15 people at my former job" and it is true, say it.

Keep your previous jobs, with real titles and dates. Gaps look worse than an unrelated job. But rewrite the bullets so they show skills a software team uses: working with data, finding root causes, writing documentation, handling technical tools, training others, and meeting deadlines. Cut duties that have no connection to the new job. Before: "Responsible for scheduling and inventory at a distribution center." After: "Tracked inventory for 3,000+ items in spreadsheets and a warehouse system, wrote a macro that cut weekly reconciliation from four hours to one, and trained eight new hires on the process." Other examples: a teacher can write about breaking complex ideas into steps and adapting to feedback. A retail manager can write about handling customer-reported problems and working with a team to resolve them. If you used any technical tools at work, such as SQL queries, Excel formulas, or internal software, put those first. If you worked at a company in an industry you now want to target, such as healthcare, finance, or logistics, say so in your summary. Companies in those fields often value developers who understand how the business works.

Put your training in an Education or Training section. For a bootcamp, list the program name, the school, the dates, and a line or two about the curriculum and capstone, for example: "Full-Stack Software Engineering Program, 800 hours. Built and deployed three full-stack applications; final project completed with a team of four." If you also have a degree in another field, list it below and keep it short. Don't hide the degree, even if it is unrelated. If you are self-taught, don't leave a blank where education would go. Create a section called "Self-Directed Training" or include the courses within projects. List specific courses or certificates, such as an online computer science course, and what you built after. Say "Self-taught" once, and then let the projects prove it. See the certifications guide for how to list individual certificates. Common mistakes to avoid: claiming more experience than you have, listing every technology you have ever touched, burying projects on page two, using a cute or vague job title for yourself, and sending the same resume to every posting. Change the summary and skills order to match each job, and make sure the technologies in the posting that you really know appear in your resume. If you have a pile of old resumes, project notes, course certificates, and performance reviews, aNewJob can build your resume from those documents through a short interview, so you don't have to start from scratch.