When you use tools (for what ever purpose) are you thinking more like an architect (what is the problem and what design will solve the problem) or has that part been done and now you're just getting the job done.

What are the different tools you use in each role?

• patterns
• libraries (things that can be resused)
• implementation code

(when are things strategic and when are they tactical)

from Yale job description
(Develops and analyzes metrics that emphasize performance, sustainability, and usability of tools and platforms)

If your business is to tell or synthesize stories emerged from piles of data (journalists, historians, researchers, politicians, teachers, curators, analysts, etc), we need to think about a contribution ecosystem where sharing your data benefits you and in a way that it's obvious for you to understand (and to explain to your boss!)

Saul Wurman about information architecture:

"I mean architect as in the creating of systemic, structural, and orderly principles to make something work - the thoughtful making of either artifact, or idea, or policy that informs because it is clear."

Nike ad for data person

The ideal candidate will be part developer/programmer, part researcher, part designer, part business analyst. He or she will have demonstrated expert experience with databases, programming in multiple languages, in visual design and with statistics. He or she will have an understanding of the existing open data communities and networks of visual designers and researchers who love data.