About
Full stack engineer. Currently helping to bring retirement benefits to more Americans at…
Experience
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Education
Other similar profiles
Explore more posts
-
Paul Gasser
Here’s the resume mistake I see most often with experienced developers - and why it hurts more as you get senior. You get promoted. Your scope increases. But your resume still lists everything you did five roles ago. Bug fixes. CRUD APIs. Unit tests. The result? Your resume looks flat. Hiring managers don’t see growth - they see someone doing mid-level work for 10 years. What strong candidates do differently (and interviewers notice immediately): As you advance, your resume should shed work - not accumulate it. • Early roles: Tactical wins (4–6 bullets) - show you learned the craft • Mid roles: Less execution, more ownership (5–7 bullets) • Senior/current roles: Only high-impact work - architecture, trade-offs, scaling, mentoring (4–5 bullets) Example progression: 2018–2020 “Implemented REST APIs, wrote unit tests, fixed bugs” 2021–2023 “Designed microservices platform, optimized legacy integrations” 2024–Present “Architected modernization pipeline replacing 1M+ lines of legacy code, reducing deployment risk by 70%” By ruthlessly cutting what you no longer do, you make growth obvious in seconds. That’s what hiring managers are scanning for. Curious - do you trim older responsibilities as you advance, or keep everything “just in case”? #SoftwareEngineering #FullStack #Modernization #TechCareers #HiringClarity
-
Jason Gorman
I'd like to see a Venn diagram of developers who "just want to write code" and developers who hate being told what code to write. Hang on. I think I found one... Oh, wait. My mistake. That's a Venn diagram of developers who think unit testing is a waste of time and developers who push code that doesn't even compile. Easy to get those two mixed up.
2 Comments
Explore top content on LinkedIn
Find curated posts and insights for relevant topics all in one place.
View top content