How to apply for Content Lead

About White Circle

White Circle builds the safety, reliability, and optimization layer for AI systems. It has raised $70M in total funding, processes over 100 million API calls monthly, and fine-tunes its own LLMs. The team is small and focused, so your work ships to production quickly and influences how AI safety is built.

About the role

As Content Lead, you own White Circle's content vision and editorial direction end-to-end: find the story, define the angle, write it, publish it, and make sure it reaches the right technical audience. You turn complex AI safety topics into clear, compelling stories that build trust, shape the company's voice, and drive product adoption. You also turn customer conversations into case studies, customer stories, and reference materials.

A typical day

A typical day might involve interviewing a customer about how they use White Circle, drafting a long-form piece on an AI safety topic, and working with the team to publish and distribute it. You would also review incoming content ideas and decide which stories to pursue next. The exact rhythm depends on the team, so ask about their publishing cadence and review process in interviews.

Who White Circle is looking for

• Can explain AI safety, policies, and LLM evaluation in plain language for technical readers.
• Has a portfolio of long-form content published on platforms like Medium or Substack, ideally about AI, infrastructure, or developer tools.
• Is comfortable owning the full content process: interviewing customers, finding angles, writing, publishing, and distribution.
• Can work independently in a small remote team and ship content quickly without heavy process.

Tips for this application

• Include 2-3 links to long-form pieces you wrote about AI, safety, or developer tools. Show you can make complex topics clear.
• Write a short pitch for one content piece White Circle should publish. Pick a specific AI safety topic and explain the angle and audience.
• Reference White Circle's product details: policies as natural-language rules, automated testing and enforcement, and 100M+ monthly API calls.
• Explain how you would turn customer conversations into case studies and reference materials, since that is a listed responsibility.
• If you have published on Medium or Substack, link your profile. White Circle explicitly mentions those platforms.

What to cover in your cover letter

['Your experience writing long-form technical content for AI or developer audiences, with links to samples.', 'How you approach editorial direction: finding stories, defining angles, and measuring whether content reaches the right technical audience.', "A concrete idea for a content series or case study that would build trust with White Circle's customers.", 'Why you want to work on AI safety content specifically, not just content in general.']

Research before applying

• Read White Circle's website and any published content to understand their current voice and topics.
• Look up their Series A announcement and investor list to understand their positioning in AI safety.
• Research what 'policies' mean in their product: natural-language rules that define what an AI model should and shouldn't do.
• Find and read content from competitors in AI safety and LLM evaluation to see what White Circle's content needs to stand apart from.

Likely interview topics

Based on the job description, expect questions about:

• How would you explain White Circle's policy-based approach to AI safety to a technical buyer who has never heard of the company?
• Walk us through how you would turn a customer conversation into a published case study, from interview to distribution.
• What is your process for finding and validating story angles in a fast-moving technical field?
• How do you measure whether long-form content is reaching and influencing the right technical audience?
• Give an example of a complex AI or infrastructure topic you made clear for a non-expert reader. What choices did you make?

Common mistakes to avoid

• Submitting generic writing samples that are not about AI, safety, or developer tools.
• Pitching content ideas that are too broad or marketing-heavy instead of specific, technical, and useful.
• Ignoring the customer-story part of the role and focusing only on blog posts or social media.