🚨 “Overqualified” – 6-month update from inside the same company
A few months ago I shared a very personal story here: 
I applied internally to grow as a developer and ended up being called “overqualified” and even “unable to code” — without anyone seeing me write a single line.
That article got more attention than I expected. 
Many people related to the situation and shared their own experiences with toxic environments and career transitions.
Today I published a follow-up post where I explain:
<ul>
<li>How I moved to a new role as Junior IT Engineer in the same company.</li>
<li>What my day-to-day looks like now (printers, DHCP, support, internal tools).</li>
<li>The POS-lite side project I’m building with Java + Spring Boot + React.</li>
<li>What I’ve learned in these months about labels like “overqualified” and finding a better fit.</li>
</ul>
👉 Read the full update on <a href="http://dev.to" target="_blank" rel="noopener nofollow">dev.to</a>: 
<a href="https://dev.to/guadalupe182/from-overqualified-to-it-jr-6-month-update-on-my-career-pivot-webdev-career-programming-3lkk" target="_blank" rel="noopener nofollow">From “Overqualified” to IT Jr: 6-month update on my career pivot</a>
#webdev #career #programming #productivity

Guadalupe Rosas

A developer shares a 6-month follow-up after being labeled 'overqualified' during an internal application. They transitioned to a Junior IT Engineer role at the same company, now handling IT support tasks like printers, DHCP, and internal tools. They're also building a POS-lite side project using Java, Spring Boot, and React. The post reflects on lessons learned about workplace labels and finding a better professional fit.