File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Average age for entry-level java architects

 
J Vallejo
Ranch Hand
Posts: 31
  • 0
  • 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?
 
Darya Akbari
Ranch Hand
Posts: 1855
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I would agree with you.
 
Andrew Monkhouse
author and jackaroo
Marshal Commander
Pie
Posts: 11833
181
C++ Firefox Browser IntelliJ IDE Java Mac Oracle
  • 0
  • 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
 
Pat Farrell
Rancher
Posts: 4660
5
Linux Mac OS X VI Editor
  • 0
  • 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.
 
Tim Holloway
Saloon Keeper
Pie
Posts: 17639
39
Android Eclipse IDE Linux
  • 0
  • 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: 4660
5
Linux Mac OS X VI Editor
  • 0
  • 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.
 
arulk pillai
Author
Ranch Hand
Posts: 3380
  • 0
  • 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.
 
I agree. Here's the link: http://aspose.com/file-tools
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic