There are defined Architect roles when you work at large companies where the division of labor requires more specific roles.

Like others have said, the focus should be on the bigger picture of the overall system(s) and how they inter-relate.

As you move around in your career, look for roles where you have more say in how the system is designed in the beginning. Take on more responsibility in how different modules/components interact.

Also read up on design patterns - including the book Patterns of Enterprise Application Architecture by Martin Fowler (and read his blog/site too).

Much of architecture is focusing on the parts of the system that have high risk and making them less risky, usually these are the parts where the systems interact with each other.