How Can I Rework My Developer CV for a Junior Linux IT Support Role?

Your current CV will probably make the transition look unclear because it presents you as a specialist software developer. For this application, create a targeted version that leads with Linux, troubleshooting, scripting, networking, Git, debugging, automation, and user-focused problem solving.

Describe situations where you used Linux tools, logs, ADB, command-line utilities, environment configuration, or scripts to diagnose and fix issues. Put the Google IT Support certificate under a relevant certifications section, and consider studying toward an entry-level Linux certification such as LFCA or LFCS if you want to demonstrate commitment. Keep the development experience, but reduce the space given to frameworks that have little connection to the job.

Treat the application as a career-pivot CV rather than trying to use one document for every role. Add a short summary explaining that you are a software developer moving into Linux and internal IT support, with hands-on experience diagnosing technical problems and learning new systems quickly.

Create a skills section that mirrors the job requirements, but only include items you can discuss confidently: Linux administration basics, Bash or Python scripting, networking fundamentals, Git, hardware and software troubleshooting, logs, permissions, databases, and automation. You can also use an AI tool to compare your CV with the job description and identify missing keywords, but verify every suggested claim yourself. The position sounds closer to help desk and junior systems support than advanced Linux engineering, so showing a practical, service-oriented mindset may matter more than obtaining another credential immediately.

Rewrite the bullet points around problems solved and outcomes rather than listing technologies. For example, instead of saying you built a maintainable frontend with React and TypeScript, explain what operational problem it addressed, how you diagnosed issues, and what improved afterward.

Your strongest evidence may be the crash debugging, ADB and logcat work, release troubleshooting, database exposure, Git usage, and any experience configuring development environments. Quantify results wherever possible: time saved, crashes eliminated, users supported, deployment failures reduced, or work automated. Employers will care more about your troubleshooting process and measurable impact than a long list of buzzwords.