I’ve been contacted about a job as an “XML Architect.” The location is good, but I don’t know what the heck an XML Architect is or does. Any pointers?
XML:
As an architect, you would be responsible for designing how to store and transport data using XML.
Do you normally consider taking jobs about which you know nothing? What if this were murder contracting, or something like that? Still interested in pointers?
I do that all the time. How else would I learn new stuff. Although I know about XML which I have been using for years. As a tool in other tasks. I just thought there should be more to an actual job - and especially one with such a fine sounding title - than deciding how to structure an XML file.
Corporate IT folks love to attach “Architect” to the title of many jobs. Sometimes it actually has some meaning (like if people had to go through you to confirm that their use of XML conforms to the company “architecture”), but I wouldn’t bet my lungs on it.
All I would infer from that job title is that it requires knowledge of XML.
Like George Costanza, they always wanted to be Architects.
I like your attitude. I’d hire you! 
Depending on the details, there may be a lot more to it. Complying with public standards, writing *correct *XSDs for the complicated stuff the tools don’t handle, etc. Or becoming the mother hen for an existing set of 2,387 poorly-designed existing schemas.
Or, like others have said, its just a fancy name for a database analyst using a clunky data base “language”.
What is an XML Architect?
Overpaid. Take the job.