Job Advert: Linked Data Developer

== Linked Data Developer ==

Our platform development group is responsible for making sure that the
Talis Platform is the premier environment for developing and delivering
great Semantic Web applications. We need your help to convert and
generate Linked Data sets for use by these and other applications.

We're looking for people who:

* use their code to communicate their ideas clearly
* are experts in scripting and automating data conversions
* have been involved in open source or community projects
* can devise new strategies for processing data at scale
* never forget about scalability, performance and security
* prefer to develop test first
* are proficient at modeling data in RDF
* have an opinion on httpRange-14
* aren't afraid to ask questions
* like to say "let's try it" and "we can do that"
* understand how to balance perfection with reality
* are as happy to lead as to follow
* know when to reuse and when to start afresh
* can tell us about something new they learned this year

== How to apply ==

Take a look at the problems below and select two to answer. Please send
us your C.V and an application letter telling us about yourself and
including your answers to careers@talis.com. Talis is based in
Birmingham, UK but this role is amenable to remote working so we
welcome non-UK applicants.

1. Describe how you would model the cast list of a movie as Linked
Data. How would your approach cope if one cast member wanted higher
billing on movie posters? Discuss the trade-offs involved in modeling
lists and collections in RDF paying particular attention to how the
data can be optimized for wide reuse.

2. Give an example of how you have automated long running processes in
the past and some of the issues you encountered. What strategies would
you adopt for coping with failures in the process and its environment?

3. Discuss your approach to producing Linked Data in domains that have
no pre-existing consensus on the model or vocabulary. How would you
ensure the data is immediately usable by as many interested parties as
possible while retaining the ability to evolve the model? Additionally,
how would you then build consensus in the community around the chosen
model?