JAVA SOFTWARE DEVELOPER

[daves1130]

JAVA SOFTWARE DEVELOPER

AVA SOFTWARE DEVELOPER

Location: TORONTO, ON
Salary: 70K to 90K
Contact Email: (e-mail address removed)
Skills and qualifications:

B.Sc. in Computer Science or Electrical Engineering

Expert level Java knowledge (incl. SWT, Swing)

Familiarity with Eclipse architecture and experience with Eclipse
plug-in development, PDE

Good knowledge of XML (incl. XML Schema, Namespaces) and XML Web
Services (SOAP, WSDL, UDDI)

Extensive experience with GUI design, hands on knowledge of UI
usability engineering

J2ME and J2EE experience

Experience with graphical editing and modeling frameworks

Sound knowledge of software architectures, OOA/OOD, design patterns

Sound knowledge of software engineering practices

Experience with UML and Software Modeling tools (TogetherJ, Rational
Rose)

Must have:

5 years - Java
3-5 years - J2ME (Micro Edition)
3-5 years - Eclipse Architecture
3-5 years - Eclipse PDE (Plug in Development)
3-5 years - XML
3-5 years - J2EE
3-5 years - UML
3-5 years - Graphical User Interface (GUI)

 

[Roedy Green]

3-5 years - Eclipse PDE (Plug in Development)

When did the first Eclipse plug in hit the streets?

 

[Chris Smith]

When did the first Eclipse plug in hit the streets?

Eclipse was released in November of 2001. Development began within IBM
in January of 2000. The core idea behind Eclipse is "everything is a
plugin", so I'm guessing that plugins started getting written within, at
most, a few weeks after development started. The PDE as a set of tools,
though, probably didn't exist for some time following the start of
development.

So an ex-IBM employee who was part of the core team that wrote Eclipse
could conceivably have nearly six years of experience writing plugins,
and maybe about five years with PDE. Someone who has never worked for
IBM could have four years experience with plugins and the PDE, if they
were somehow able to start working with Eclipse at the moment of release
and sustain the work for all four years since. Realistically, business
concerns would have delayed any external company's decision to embrace
Eclipse to that point by at least six months and probably more, so a
real three years of experience would be a phenomenal find.

--
www.designacourse.com
The Easiest Way To Train Anyone... Anywhere.

Chris Smith - Lead Software Developer/Technical Trainer
MindIQ Corporation

 

[Thomas Hawtin]

So an ex-IBM employee who was part of the core team that wrote Eclipse
could conceivably have nearly six years of experience writing plugins,
and maybe about five years with PDE. Someone who has never worked for
IBM could have four years experience with plugins and the PDE, if they
were somehow able to start working with Eclipse at the moment of release
and sustain the work for all four years since. Realistically, business
concerns would have delayed any external company's decision to embrace
Eclipse to that point by at least six months and probably more, so a
real three years of experience would be a phenomenal find.

I have seen a job requirement that I would have been the only person on
the planet to satisfy if only I had kept up doing the same thing month
after month. Of course, I wasn't interviewed.

Tom Hawtin

 

[Roedy Green]

I have seen a job requirement that I would have been the only person on
the planet to satisfy if only I had kept up doing the same thing month
after month. Of course, I wasn't interviewed.

In my earlier years, when employers courted employees, my goal was to
make sure I did something new in each job I had never tried before. I
would think about what I wanted to learn next then go looking for
someone who wanted that done.

It seems now, they want you to know everything up front. How boring!