Skip to content

In short

AWS is required most often, in 13 of 32 principal software architect roles at tech companies whose requirements we read in the 90 days to Nov 21, 2026, then Distributed Systems (12) and AI (9). Among roles that state years, 20 of 25 ask for at least 10 years. We counted 32 roles, each at a different employer.

AWS
13 of 32
Required most often, of the roles we could read
10+ years
20 of 25
Of roles stating years
Remote roles
27 of 32
Of the roles we could read for it

What the postings ask for

Out of the 32 roles whose requirements we could read, of 32 in all. Too few to show shares, so we show counts.

Required
SkillRoles asking
AWS
13 of 32
Distributed Systems
12 of 32
AI
9 of 32
Cybersecurity
9 of 32
Azure
8 of 32
CI/CD
8 of 32
Cloud Architecture
8 of 32
Observability
8 of 32
Python
8 of 32
Infrastructure as Code
7 of 32

Does your resume show these? Review my resume

Preferred
SkillRoles asking
Kubernetes
7 of 32
AWS
5 of 32
AI
4 of 32
Azure
4 of 32
Machine Learning
4 of 32
Terraform
4 of 32
Cloud Security
3 of 32
Cybersecurity
3 of 32
Data Infrastructure
3 of 32
LLMs
3 of 32

Experience

Asked most often: 10+ years, 20 of 25.

Of the 25 roles that state years

Under 5 years
0 of 25
5–7 years
1 of 25
8–9 years
4 of 25
10+ years
20 of 25

Degree

2 of 32 require a degree, and 8 more accept experience instead.

Of the 32 roles we could read for it

Required
2 of 32
Required, or experience instead
8 of 32
Preferred
3 of 32
Not mentioned
19 of 32

Pay and remote work

Of the 32 roles we could read for it

Roles stating pay
13 of 32
Remote roles
27 of 32

Questions about principal software architect roles

Companies with the most software architect roles

Have a principal software architect posting in mind?

Paste the posting and your resume to see each requirement checked. No account needed.

No posting yet? Review your resume instead

Check a principal software architect posting

How we count: 32 roles in the 90 days to Nov 21, 2026, each role counted once however many boards post it. Methodology

Something wrong here?