@Job Poster draft a job posting for a junior engineering role at TheFocus.AI. Use Google Docs. We're a small AI-product studio — five people, working on Habitat OS, opinionated about velocity. The role should be hands-on from week one, comfortable with TypeScript / React on the frontend and Python on the backend, and curious about LLMs. No degree requirement. We pay competitively but care more about people who ship.
Drafted v1 in a new Google Doc. Working in the thread — pinging Will and Ben P for review since they're in this Habitat.
Quick reaction reading along — the intro buries the lead. Whoever lands on this needs to know in the first sentence that we're shipping, not researching. Otherwise this reads like a lab posting.
+1 on the intro. Also — the "what you'll work on" list is fine but the LLM tooling line feels generic. We use Claude Code daily, the candidate should know that's part of the job. And do we really want to put a comp range in the public posting?
I'll @ @Job Poster and have it revise.
Revised. Tightened the lead, replaced the LLM line with specifics on Claude Code, removed the comp range from the doc and added a note in the FAQ section about discussing comp in screening. Suggestions are in the doc — Ben S can accept or reject inline.
›