Actor Engineer

An actor takes one source and makes it look like every other source. That is the whole job description, and it is harder than it sounds — the interesting work is in the gap between what a site returns and what a contract promises.

What you would work on

• New actors, from a first exploratory fetch to a shipped, vector-gated release.
• Keeping existing ones alive as their sources change underneath them.
• The normalisation layer, where a source’s idea of a date becomes ours.
• Deciding when a source’s quirk deserves a contract change and when it does not.

What we look for

• You have written scrapers that outlived their first month.
• You are unbothered by reading minified JavaScript to find where the data actually comes from.
• You would rather ship a narrow actor that is right than a general one that is usually right.

Practicalities

You will be on a light rotation for the actors you own. Sources break at inconvenient times; we try to make that rare rather than heroic.