Win a copy of Micro Frontends in Action this week in the Server-Side JavaScript and NodeJS forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Bear Bibeault
  • Junilu Lacar
Sheriffs:
  • Jeanne Boyarsky
  • Tim Cooke
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • salvin francis
  • Frits Walraven
Bartenders:
  • Scott Selikoff
  • Piet Souris
  • Carey Brown

Average age for entry-level java architects

 
Ranch Hand
Posts: 31
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi ranchers,

Do you know what's the average age (in your country) for a starting java architect?

Am I correct in my impression that java architects are usually in their 30's and up?
 
Ranch Hand
Posts: 1855
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I would agree with you.
 
author and jackaroo
Posts: 12199
280
Mac IntelliJ IDE Firefox Browser Oracle C++ Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I wouldn't say that this is always going to be true, but I would expect it in most cases. If someone gets out of college around 22, then spends 2 - 3 years as a junior developer, developer, senior developer, .... This should put them around 30 before they have enough experience to be an architect.

Of course there are people who have the skills to rise more rapidly. And there are candidates who join companies where every employee is "senior engineer" or higher :roll: so there can be cases where people can become architects earlier.

But if I were interviewing at a company, and got introduced to the company's architect who is only 25, then I would insist on me interviewing them before taking the job so I can be convinced that I will be working for someone I can trust to do their job.

Hmmm. This is sounding more like "Jobs Discussion" than anything related to the SCEA exam or assignment. So I have moved this topic to the Jobs Discussion forum. SCEA aspirants who would like to add their comments can follow the link at the top of the page to the new location of this topic.

Regards

Andrew
 
Rancher
Posts: 4686
7
Mac OS X VI Editor Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I think its more experience than age, but its hard to have ten years of serious professional experience without being in your 30s.

I tend to believe, IMHO, etc., that the term "architect" for systems is overused. There is not much "architecture" in implementing a LAMP stack, even when its really a LAMJava stack.

There are tens of millions of "center hall colonial" houses in the US, they share a common archtecture. Changing the color, or moving the kitchen does not change the architecture.

The key to being a good architect is to have professional experience with many large systems, some of which fail. You learn from both the successful and failing projects.
 
Saloon Keeper
Posts: 22520
151
Android Eclipse IDE Tomcat Server Redhat Java Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
At a certain very large local employer, "developer" has come to mean "offshore programmer" and "architect" means "onshore programmer". And 2-5 years experience is considered optimal, since beyond that costs more money.

 
Pat Farrell
Rancher
Posts: 4686
7
Mac OS X VI Editor Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Originally posted by Tim Holloway:
At a certain very large local employer, "developer" has come to mean "offshore programmer" and "architect" means "onshore programmer".



Man, I wish I could know who those pointy haired bosses are, so I could stay at least one city away from them.

This is, however, an example of how 'architect' has become nearly meaningless in current IT. It should mean great picture design, or design to scale to Facebook size. But it doesn't.
 
Author
Posts: 3448
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
It is to do with experience with diffrent systems, knowledge, type of company etc. ARchitects need to have wider experience and good understanding in the following key areas:

-- Design concepts
-- Design Patterns
-- Best Practices
-- Software devlopement process
-- Scalability
-- Concurenc
-- Performance & Memory issues
-- Transaction Management
-- Security
-- Exception handling
-- Emerging technologies/frameworks & paradigms
-- Software development process
-- Communication and written skills

Only experience and pro-active learning can bring all these.
 
That's my roommate. He's kinda weird, but he always pays his half of the rent. And he gave me this tiny ad:
the value of filler advertising in 2020
https://coderanch.com/t/730886/filler-advertising
reply
    Bookmark Topic Watch Topic
  • New Topic