Why this grade
This listing scored 45/100, which is a D. It lost the most ground on pay transparency.
- Freshness 15 / 15 How recently it was posted. Older postings are likelier to be filled or abandoned.
- Description depth 14 / 20 How much the posting actually says about the work, measured in characters of real text.
- Remote clarity 8 / 15 Whether "remote" means anywhere, or is quietly restricted to one country.
- Corroboration 5 / 10 Whether more than one source carries this listing.
- Role specificity 3 / 10 Whether the listing is tagged well enough to tell what the role actually is.
- Pay transparency 0 / 25 A published salary range, worth more than any other single factor because it is what a candidate cannot find out without applying.
Every figure above is arithmetic over the posting itself — its salary field, its text, its age, its tags and how many sources carry it. How the grades work →
This listing does not state a salary
$163k – $275k
That is the middle half of what comparable roles paid on this board over the last 90 days — 28 listings that did publish a figure, median $178k. It is not this employer's offer, and we have no idea what they pay. It is only what the rest of the market advertised.
hn-hiring
Workday's in-house creative team already uses AI every day. We built our own agent platform (Creative AI Studio) and now need a hands-on technologist to keep it running well and build what comes next.
Half the work is building: new role-specific agents, plus integrations and automations over APIs and MCP servers that move work from request to brief to production to review with fewer manual handoffs. The other half is making shipped tools work for people: supporting users, improving agents through PRs, and teaching designers and writers to get real value from them. You'll also be our technical filter on AI vendors, looking past the demo to the architecture, security, data handling, and pricing.
You'd be a good fit if you:
- Have shipped AI agents or agentic workflows that real users depend on (Claude Code, Cursor, etc.)
- Are at home in a repo: branches, PRs, code review, release hygiene
- Understand APIs, auth, webhooks, and MCP, and can map data flows before you build
- Can teach a room of non-technical creatives without jargon
Not a fit if you want to build but not support or teach, or you'd rather research AI than ship it.
To apply, email [email protected] with your resume and links or write-ups for one or two things you've built. For each one, tell me what problem it solved, how it works, and what you'd change now. I'm the hiring manager and read every one.
Where this listing came from
- 02 Oct 2026 Hacker News first sighting
Seen on 1 board over 0 days.