The title covers a wide range of jobs, from pre-sales design to hands-on technical leadership. The common core is ownership of a solution’s shape: its components, its boundaries, its trade-offs and its fit with the wider organisation. This lesson defines the role so you can recognise it in any job description.
Between the problem and the code
The architect takes a business need, works out what system would meet it within the constraints that apply, and produces a design detailed enough to estimate, build and review. Developers own the code; the architect owns the decisions the code depends on.
The three audiences
The business, who need confidence the solution will deliver; the engineers, who need clarity on what to build; and operations and security, who need assurance it can be run and protected. A good design speaks to all three.
Breadth over depth
Enough understanding of applications, data, integration, infrastructure and security to make sound decisions across all of them, and the judgement to know when to bring in a specialist.
Action Step
Portfolio: choose a real or realistic business problem and write a one-page problem statement: who has the problem, what it costs them, what success looks like, and the constraints you already know about.
This course is vendor-independent: it is not affiliated with, endorsed by or accredited by any tool vendor or certification body, names products only for identification, and issues no credential. Verify current documentation before applying anything in production.