Technical Lead (via Dunhill)

Dunhill is helping someone (company unspecified) look for a Technical Lead:

  • [T]o manage an existing software development team building large, high volume solutions using J2EE technologies
  • A SCRUM-Master certification, XP-coach, or other experience with agile methods is necessary, complemented with software engineering knowledge
  • Extensive experience with Java, J2ME, JUnit, Fitnesse, JMS, EJB, Web Services, Web Applications, Hibernate
  • Strong technical and non-technical communication skills: familiarity with presenting and explaining technical concepts to a variety of audiences
  • Experience working with company executives, shareholders, and directors an asset

The Good
There’s not a lot of detail about the technology stack, but what’s there looks good, for the most part.  (I’ll touch on EJB in the next section).

It looks as if they take testing seriously, and agile methods, both of which are positive signs.

The Bad
The base problem is that there’s not a lot of information.  What’s the company?  What do they do?  What’s the project?  Is there an existing team?  Are they any good?  What are the details of technology and process?  What’s the location?  What’s the compensation like?
As far as technology goes, there’s a reference to EJB here.  EJB’s not a technology I’m overjoyed to use, although if it’s EJB 3.0, I could possibly live with it.  I’m not sure if this is legacy code they have in place, or a long-term technology choice.  If they take testing seriously, EJB is a bit of a bear because it tends to require in-container testing, or strategies to mitigate the fact that it’s difficult to test enterprise java beans.

I’m also a little concerned about this phrase: “excellent opportunity for a highly skilled technical person with some management skills to move to the next step.”  That phrase could imply that they’re looking for someone with less experience that they can get at a lower cost.  Or they may just be willing to consider people with more talent than experience, it’s hard to say.

Conclusions
Not much detail here, but what’s here is interesting, for the most part.  You’d need to probe more to form an informed opinion: learn about the company, the project, the team, the location.  Still, if you can get past EJB, it feels like the basics might be sound.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: