I Write Code. But I’m Called an Architect. Why?
- Sunil Dutt Jha
- Apr 28
- 3 min read
Updated: Apr 29
My title says Architect. My work says something else.
This is not a skill problem. This is a definition problem.
Why Do I Believe I’m an Architect?
There are four reasons I say so.
1. A tool vendor certified me as an Architect. I’ve been trained on cloud platforms, databases, frameworks.
What this actually means:
I know how to use tools effectively. This is P5 capability.
2. Books and authors said this is architecture. I’ve learned microservices, event-driven design, layered patterns.
What this actually means:
I understand implementation patterns. But patterns are not architecture unless mapped to P1–P4.
3. My GCC leader in Amsterdam or Chicago calls this architecture. The role is defined globally and scaled across delivery centers.
What this actually means:
The label supports delivery structure. It does not define software anatomy.
4. My job designation says “Architect”
It reflects experience, seniority, billing category.
What this actually means:
The title signals position. It does not confirm the existence of architecture.
Want to read more?
Subscribe to architecturerating.com to keep reading this exclusive post.
