Need to hire someone

[barrydidit]

Well it's got me stumped.

[mudskipper]

Out of interest, do they actually need to know this stuff for the role? I stumbled my way through my technical interview for current gig dragging rusty stuff up from the darkest recesses of my brain and forgetting terminology and I've not done anything that remotely needs it in the gig - just basic crud + webforms stuff.

[mudskipper]

Well it's got me stumped.

You're for the chop then.

[EternalOptimist]

No.



It's a generic Tree<X>, the type parameter may differ between input and output, so may the structure.

if the leaf on one tree is in a different place to the leaf on the other tree, and the leaves are not unique,

you would have to use some sort of fuzzy logic or best fit.

I done it before for addresses and postcodes and phone numbers, in a de-dupe for a bank

[DimPrawn]

Core Skills:



Technical interview question #1:

You have a tree data structure that you need process, doing something different with each leaf in turn, and collating the results into another parallel tree. How would you go about that?

.

Have you tried this man?

Bob Shawadiwadi | LinkedIn

He does all codes.

No wonder you can't hire anyone, your questions are absurd.

[mudskipper]

http://www.ccs.neu.edu/home/riccardo...ransformer.pdf

Do you allow your interviewees to google? I think ability to google is #1 skill given that you're unlikely to be an expert in everything you need to ever know.

[doodab]

Out of interest, do they actually need to know this stuff for the role? I stumbled my way through my technical interview for current gig dragging rusty stuff up from the darkest recesses of my brain and forgetting terminology and I've not done anything that remotely needs it in the gig - just basic crud + webforms stuff.

They'll need good analysis and problem solving skills and CS background knowledge i.e. data structures, design patterns and so on.

[d000hg]

How enterprisey would you like it And how big are the trees?

[wonderboy]

What is the size of the tree, what are the time/memory constraints?

If it is small, recursively traverse it. If the nodes are typed then you'll probably want to use polymorphism to decide how to process the node. You can build the other tree as you go.

If it is large, avoid the recursion and manually keep track of how you go.

Another question: does how you traverse the tree matter?

You probably have in mind the visitor pattern for processing the nodes, but this pattern might over-complicate things.

If I wanted to crowbar a pattern into this example, if you needed to perform multiple processing steps per node, I might use the chain of responsibility pattern.

For a telephone interview question this is tough. Based on the core skills you mention, I find it very unlikely such a question would correspond to anything the candidate would need to do on the job (I hazard a guess that the "tree" is an XML document - if so there will be a library to help with this).

I think this question would eliminate a lot of good developers from your selection process.

[eek]

I think this question would eliminate a lot of good developers from your selection process.

I think its more a look at me aren't I clever question to which my response would be see ya don't want to work anywhere near ya.