A few months ago I wrote about a really uncomfortable experience inside my own company:
I applied internally to grow as a developer and ended up being called “overqualified” and even “unable to code” — without anyone ever seeing me write a single line.
If you haven't read that story yet, here it is:
👉 Am I really overqualified… or just uncomfortable for others?
That post generated more reactions than I expected.
Some people related to the story, others shared their own toxic experiences and career doubts.
This is the 6-month update.
Same company, new role
I’m still in the same company, but now I work as a Junior IT Engineer instead of a Test Engineer Jr.
On paper it might look like a small change, but for me it was a big shift:
- I’m closer to infrastructure and support instead of just testing.
- I help people solve real problems every day.
- I get to touch networking, printers, servers, databases and internal tools.
- I still code small scripts and tools whenever I can.
Most importantly: I feel less like a threat and more like someone who actually adds value.
What my day as an IT Jr looks like
Some examples of what I handle now:
- Troubleshooting printers (including industrial label printers) and drivers.
- Managing IP reservations and DHCP entries when new devices appear on the network.
- Helping users with Windows issues, performance problems and basic automations.
- Using tools like DBeaver and SQL queries to support other areas that need data.
- Checking connectivity, VPN problems, and general “why is this not working?” tickets.
It’s not glamorous. There’s no “big framework” or fancy buzzwords.
But it’s real work that keeps a factory moving. Every ticket is an opportunity to learn something new.
My “POS-lite” side project
Even though my daily job is more IT-focused, I didn’t want to lose the dev side of me.
So I’m building a personal project: a Point of Sale (POS) system.
The idea is to use it in small businesses and gyms (and to keep learning modern tools):
Stack:
- Backend: Java + Spring Boot
- Frontend: React
- Database: MySQL / PostgreSQL
- Other pieces: Docker, Git, GitHub, CI/CD
- Future ideas: barcode scanner integration, product packs, stock alerts, and deployment on the cloud
I’ve been working on features like:
- Creating and editing products
- Handling stock and packs of products
- Scanning codes to add items quickly
- Basic reporting
This project helps me stay up to date with clean architecture, REST APIs, error handling, Git flow, and deployments.
Inside the company I may be “IT Jr”, but outside I’m still pushing myself as a developer.
What I’ve learned in these months
Looking back, here are a few lessons that stayed with me:
- Being called “overqualified” or “too much” usually says more about the environment than about you.
- You can be in the wrong team inside the right company.
- It’s possible to pivot internally to a role where your curiosity is seen as an asset, not a threat.
- Side projects can keep your motivation and skills alive, even when your day job is not perfect.
What’s next
I’m currently focusing on:
- Growing in my IT Jr role, understanding more about infrastructure and operations.
- Improving my English to open more international opportunities.
- Pushing my POS-lite project forward and polishing it enough to use as a real portfolio piece.
If you read my first article and felt something similar, this is for you:
You are not “too much”. You might just be in a place that doesn’t know what to do with everything you bring.
Thanks for reading — and if you have any advice, experience or questions, I’d love to read your comments.
Top comments (0)