Full‑time Software Architect: Roles, Responsibilities, Rights, and Evaluation

In the tech community, the term "architect" is often overused, yet many still struggle to define the role; this article, authored by a member of Alibaba International Technology, explores what an architect truly does and how to approach the position when assigned.

1. Two Types of Architects

Many engineers with five or more years of experience have informally taken on architectural duties while still acting as developers or PMs – these are "part‑time architects" who handle design and implementation within small teams. In contrast, a "full‑time architect" does not manage specific business systems but is responsible for all systems, requiring broader oversight, early project control, and coordination across larger teams and problem domains.

2. Responsibilities of a Full‑time Architect

Microsoft classifies architects into Enterprise Architect (EA), Infrastructure Architect (IA), Technology‑Specific Architect (TSA), and Solution Architect (SA). At Alibaba, a full‑time architect typically focuses on IA and TSA, with four key duties:

Global Technical Planning : Create a clear, comprehensive blueprint that defines what exists, what is missing, and future directions, requiring deep technical breadth, strong communication with business, and long‑term vision.

Unified Methods, Standards, and Mechanisms : Provide not only the blueprint but also the processes, standards, and governance needed to ensure orderly execution and clear responsibility distribution.

Complete Foundational Construction : Supply a robust set of foundational tools and platforms (the "weaponry") that enable teams to work efficiently, ranging from basic libraries to large‑scale infrastructure.

Implementation‑Oriented Planning : Ensure that plans are actionable and not merely theoretical PPT diagrams; the architect must drive real delivery and avoid becoming a “paper architect”.

3. Rights of a Full‑time Architect

Effective execution requires authority to coordinate resources, define boundaries, and influence organizational structure. While some argue that only senior leaders can wield such power, the ideal is a balance where the architect can both lead technically and remain connected to the team.

4. Assessment of a Full‑time Architect

Evaluation aligns with the four responsibilities:

Technical Planning : Qualitative assessment of completeness, foresight, and guidance value.

Methods, Standards, Mechanisms : Measurable outputs such as documented processes and compliance.

Foundational Construction : Review of the completeness and quality of shared platforms.

Implementation : Simple binary check – does the plan get delivered with the expected quality?

5. Practical Implementation Ideas

To build an effective architecture function, the article suggests establishing an "architecture language" (business domain models, component diagrams, deployment diagrams) and creating a "recognition body" where technical expertise, knowledge sharing, and domain organization form a cohesive team. The architect should always act as a service provider to team members, fostering a culture where the architecture empowers developers.

Overall, the piece emphasizes that architecture is about turning abstract ideas into concrete, scalable systems, and that the success of a full‑time architect hinges on strategic planning, governance, solid foundations, and relentless focus on delivery.