Loading…

Spike

Freelancing

Content Writer Role at Spike

Spike is hiring a Content Writer.

  • Role: Contractor, Immediate joining
  • Contract period: 3 months
  • Scope of work for 3 months: 45 Top-of-the-funnel (TOFU) blogs
  • Total compensation for 3 months: INR 70,000 - 1,00,000 (negotiable)
  • Read the JD here

Content Brief for the Assignment

Basic Details:

  • Topic: Incident vs. Bug: Understanding the Key Differences
  • Primary keyword: Incident vs. Bug
  • Goal: To educate the target audience on the differences between an incident and a bug with examples
  • Content Type: Blog post
  • Content category: Top of the funnel
  • Intent: Informational
  • Target audience: DevOps engineers and Site Reliability Engineers (SREs)
  • Tone: Professional yet approachable

Do’s

  • Conduct basic SERP analysis:
    • Study the AI overview and Google Feature Snippet for the primary keyword.
    • Study the “People Also Ask” and “People Also Search for” sections. If possible, use some of those questions as FAQs in the blog.
    • Study top-ranking blog posts. Observe the format, word count, H2s & H3s, what was covered, and what could be better. List down the content gaps and fill them in the blog.
  • Include apt examples and analogies where possible. Plus, make sure they are relevant to our target audience.
  • Include relevant stats if you find any (optional)
  • Provide meta title, meta description, blog excerpt, and blog title
  • Include the primary keyword in the meta title, meta description, blog excerpt, blog title, and introduction.
  • Add relevant internal links
  • Leave 2-3 placeholders in the blog post for anecdotes or customer stories where possible. Check out this blog post for reference: https://spike.sh/blog/oncall-schedules-everything-you-need-to-know/

Don’ts

  • Avoid overly technical jargon
  • Avoid keyword stuffing

Writing Guidelines (Feel free to feed this to your AI)

  1. Write short, plain‑language points that feel human, not templated
  2. Skip bold headings, bracketed citations, and rigid numbering
  3. Keep sentences under 20 words when possible
  4. Avoid the words: Ensure, Enhance, Leverage, Utilize (plus avoid all their variations)
  5. Use as few dependent clauses as you can—break long thoughts into two sentences instead
  6. Favor everyday verbs (“use,” “test,” “measure”) over abstract nouns (“utilization,” “implementation”)
  7. Tone: not too professional and not too casual; no emojis
  8. When you list items, use simple dashes or bullets
  9. Each paragraph should not be more than 3 lines
  10. Avoid excessive present continuous tense (ing words)
  11. Bold the important words, phrases, or sentences. However, don't overdo this.
  12. Primary keyword: <insert your primary keyword here>
  13. Target Audience: <insert your target audience here>

Some useful links:

Submission Guidelines:

  • Share a link to Google Docs or Notion
  • Make sure you provide the access



✨ Important note

  • Contribute to open source projects hosted by brands
  • The open source projects are meant for the portfolio building purpose, not necessarily for hiring purpose
  • On approval, your submission will be displayed on your portfolio