The original is a how-to guide about vetting senior Sanity CMS developers. I need to rewrite it as a punchy headline for a mobile feed.

Short summary

When hiring senior Sanity CMS developers, assess two layers: content modeling (schemas, document references, Studio editor UX) and integration (Next.js delivery, image performance, secure previews). Use specific questions about preview workflows, schema design, permissions, and editor experience as your measure of seniority. Red flags include recommending Sanity universally, portfolios of starter templates, inability to articulate editor workflows, and lack of budget/timeline awareness.

• •Seniority in Sanity requires strength in two layers: content modeling (schemas, Studio UX) and integration (delivery, performance)
• •Ask specific technical questions about previews, permissions, schema design—vague answers indicate mid-level capability
• •Red flags: recommends Sanity for everything, portfolio is starter templates, can't explain editor experience, no consulting awareness

Generated with AI, which can make mistakes.