We’ve asked candidates to talk about their product experience, and drill down into projects they’ve worked on and specifically what type of services they’ve created. This will give you a bit of an idea on their role on projects. For example, were they just doing simple mappings from Document A to Document B, or were they involved with complex DB interaction, or Broker stuff. We’ve especially found if a candidate has never written a Java service in wM, they either haven’t been doing many technical things or haven’t been working with the product very long.
From there, you can expand on wM specific things, too. For example, here’s a few questions I like and use:
-
What’s the difference between invoking a service as a Transformer vs. a Flow step? [essentially Pass By Value vs. Pass By Reference]
-
When can’t you use Transformers? [The transformer won’t automatically iterate over a list like a normal map step might]
-
How are the Users defined in wM tied to ACLs? How are ACLs used to control access to services?
-
Have you written any Java services? If yes, tell me about the pipeline interaction within a Java services. What role does the IDataUtil class play?
-
How are TN Processing Rules used?
-
What is a Trigger?
Also, if you are looking for some domain-specific experience, like EDI, you can ask them questions on how they’ve worked with that domain in wM, limitations they found, etc.
A lot of it is just getting a feel for how they talk about these topics - are they honest when they don’t know? Are their answers complete and express good knowledge on the subject?
Jason
#webMethods#webMethods-Archive#If-it-doesn-t-fit-anywhere-else