1. Start from the real role
Nick reads the hiring manager’s notes, earlier postings and the team context you share, then asks for what is missing: level, location, pay range and what the first months involve.
Give Nick the role, the team and what success looks like, and get a specific job description with must-haves kept separate from nice-to-haves, ready for review.
With Nick, Recruiter
Starts: When you open a role or ask Nick to rewrite an existing posting.
Nick reads the hiring manager’s notes, earlier postings and the team context you share, then asks for what is missing: level, location, pay range and what the first months involve.
The draft describes the actual work, the team and the problems the hire will own. Must-haves stay short and job-related, preferences are labeled as nice-to-haves, and inflated requirements are questioned rather than copied.
You get the draft in Google Docs with open questions marked. Pay, benefits and policy statements come only from details you approve. Once approved, Nick can add it to the Greenhouse job if that access is connected and allowed.
Use this to write or rewrite a posting. Designing a take-home assessment for the same role is a separate job.
Hypothetical finished result
Senior data engineer posting
Hypothetical: a hiring manager’s bullet-point notes for a senior data engineer.
Connect the accounts and actions for your workflow. Start in Artie or add your Artisan to Slack; access stays within your account permissions.
Explore appsOnly the range you approve. Pay, benefits and legal statements are not estimated or invented.
Yes. Share earlier postings or a style guide, and Nick follows their structure and tone.
When you approve it and the connected Greenhouse access allows it. Otherwise you get the final text to post yourself.