I've recently been laid off due to company restructuring and have started reworking my resume to target positions in Platform Engineering and Developer Experience. I'm wondering if there are any glaring issues or "red flags" I should address. One thing I'm definitely planning to revise is the service discovery bullet point, as it doesn't reflect the true impact of my work and I want to keep the resume concise, ideally to one page. I've been fortunate to receive interview calls and recruiter outreach, but most offers are below my desired compensation of $200k+ for remote roles, which would be a significant pay cut compared to my previous position. I've also started revisiting LeetCode, though I'm hesitant to apply for FAANG opportunities just yet. Any advice would be greatly appreciated!
1 Answer
Honestly, it might be tough to land Developer Experience roles with the current content of your resume. Labeling it as platform engineering seems a bit overreaching since it mostly focuses on infrastructure and CI/CD. It doesn't clearly show if you've built any tools that help developers solve common issues with Kubernetes, like implementation of distributed logging or tools that simplify onboarding new applications. A strong emphasis on what you've genuinely contributed to developer needs could really enhance your profile!
I totally agree with you. After I focused on my resume to showcase my contributions to an Internal Developer Portal, it opened up more opportunities for me. Many Developer Experience roles want a software engineer who understands platform work, not just compliance-heavy tasks without clear project outcomes.