Overall, unemployment is low. The pool of job seekers seems skewed toward older engineers who may not be perceived to meet the rigorous requirements set by some potential employers. That disparity aside, it's a pretty good time to be an engineer.

It's also a good time for reflection. Even in the best of times, there's room for improvement in the profession as a whole and in the way each engineer plays his or her own role.

Industrywide, a handful of associations function as the mouthpiece for engineers and engineering issues. Such organizations speak for the profession at a time when government legislation is encroaching on the working life of the individual engineer. Well-heeled business organizations seem intent on lobbying loudly for any legislation that lets them roll back employees' benefits, eliminate workers or replace them for lower-cost labor. While information technology workers represent only a small portion of the EEs and programmers of America, the differences between an engineer and a network administrator are pretty fine for congressmen who rarely stop to think that somebody actually has to design the gear that keeps them in touch with the lobbyists.

Despite the obvious need for associations that speak for the engineer, enrollment in such groups isn't keeping pace with growth among the professional ranks. It's hard to tell whether the laggard enrollment stems from apathy, confusion about the distinct roles of the various organizations, or fragmentation of the membership rolls.

Whether or not engineers think they need to participate in formal organizations, most take active parts in the continual review and redefinition of their industry roles. Projects wrap up increasingly quickly these days, letting engineers continually start anew, either with the same employer or a new one. With the fresh start comes the opportunity to change the way things are done and to improve oneself, perhaps by attending classes on career or technical topics. Those who don't move forward stand a good chance of being passed by.

Amid the debate on the severity of the high-tech employee shortage and the impact of H1-B is the question of whether engineering and programming careers are unnecessarily short. What separates older engineers and programmers who are thriving from those who say they can't find a job? It's a sticky subject, particularly for those advising the next generation on career choices.

That brings me to a final point: Are the changes that swept engineering schools over the past decade yielding graduates who are better prepared for the working world? Has the broader coursework made for real improvements at the workplace?

Which of the above career issues are you following, and what others challenge you? Drop me a note at tcostlow@cmp.com.