All resources

What should your recruiting blog
publish in its first four weeks?

If an empty blog feels daunting, start by following your candidates' questions. Here is a first-month plan that introduces your team in four posts, one a week.

Team members planning content together around a table

If you try to introduce every role and every policy from day one, the list of people to interview and details to verify never ends. For the first month, picture a candidate for a single role and plan four posts in the order that person gets to know your company.

Decide on the reader, the message and the owner first.

  • Who will read it? Be specific about the target role and what they already know, for example “an experienced designer encountering our product for the first time.”
  • What should they remember? Choose one message that runs through all four posts, such as “People in different roles solve customer problems together.”
  • Who will see it through? Assign owners and deadlines for interviewing, drafting, fact-checking and publishing. One person can hold several of these roles.

This plan is an example that assumes one post a week. If you're short on capacity, running the same sequence every two weeks works too. The titles below are also made-up examples to help you plan, so replace them with your team's real experiences.

Week 1 · The problem we're solving

“Why does this team exist, and what is it focused on right now?”

Rather than covering the whole company history, start with one problem the team you're hiring for is solving. Once readers know who the team serves and what it does, next week's role interview is easier to follow.

Example title: The customer pain point we look at every day, and our challenge for this year

  1. One specific pain point customers face
  2. The team's role in solving it
  3. What we tried recently and what we learned
  4. The challenges we'll work on together next
What to prepare
A short conversation with the team lead, product screens or work photos you can make public, and your current team introduction materials
Where to link at the end
Link to a related role description or job posting. If there's no posting yet, pointing to the next piece of team content to read works too.

Before publishing: Confirm how far customer names and internal figures can be made public, and read it through to see that the actual work comes across rather than an inflated vision.

Week 2 · A day with a future teammate

“If I join, what will I work on, and with whom?”

Meet a team member who is actually working on the challenge you introduced in week 1. More than a phrase like “a growing team,” something they recently solved and a moment a colleague helped them shows the role concretely.

Example title: From a customer's question to a product improvement: a day in the life of the person in charge

  1. What they own and how their day flows
  2. One problem they recently solved
  3. How they worked with other roles
  4. What they'd like to tell a new colleague
What to prepare
Six to eight interview questions, a conversation of about 40 minutes, and the interviewee's photo and consent to publish
Where to link at the end
Link to the hiring information for the interviewed role and to the week 1 team introduction so readers can explore the context further.

Before publishing: Have the interviewee confirm that editing hasn't changed the meaning of their answers, and check together whether the quotes and photos can be published.

Get the 30 employee interview questions

Week 3 · Culture shown in scenes, not slogans

“How does this team share opinions and make decisions?”

From meetings, feedback or onboarding, pick one and follow a real example. You don't need to explain every policy. It's enough if a single scene shows both the team's principles and what it's still improving.

Example title: Before cutting meetings, the one thing we changed first

  1. The difficulty with the old way
  2. The agreement the team decided to change
  3. A moment it was actually put into practice
  4. What got better and what's still unresolved
What to prepare
Accounts from one or two colleagues who took part, a sample document with sensitive details removed, and a check of how things run today
Where to link at the end
Link to the role interview of a colleague who appears in the post, so readers can go on to see the environment that same person works in.

Before publishing: Don't describe a one-time experiment as an established practice. If it's one team's way of working, state clearly how far it applies.

Week 4 · What candidates want to know before applying

“I'm interested. What should I know before I apply?”

Collect the questions your recruiters get asked again and again. If the first three posts built interest, this one lays out the information candidates need to decide their next step.

Example title: Questions people often ask before applying to our team

  1. The roles we're hiring for now and what we expect
  2. Application materials and the hiring process
  3. How we work and what the first weeks look like
  4. Where to ask more questions, and the link to apply
What to prepare
Recent candidate questions, the latest job postings, and the recruiter's confirmation of the process and working conditions
Where to link at the end
Link to a job posting that is currently open and note the date the information is accurate as of. It also helps to decide who will update the post when hiring closes.

Before publishing: Check whether you can state the process timeline and working conditions definitively. For anything that varies case by case, leave a way to ask the person in charge.

A publishing routine that doesn't start from scratch every week

If you publish on Fridays, try interviews and gathering material on Monday, the draft on Tuesday, review by the interviewee and the owner on Wednesday, and edits and a preview check on Thursday. If you schedule the interviews for all four posts before week 1 begins, you won't have to start from scheduling each time.

In a draft, focus on finding missing facts rather than on perfect sentences. When you ask for a review, state the scope and the deadline: not “Please take a look overall,” but “Could you confirm by Wednesday that this quote and this description of the work are accurate?”

If a review runs late, adjust the schedule. It's better not to fill an empty week with unverified stories or sentences that don't match what the company is really like.

What should you look at after publishing four posts?

In the first month, look for what to write next rather than judging success or failure by a single number. Start by recording the channels and dates each post went out on; you need that to make sense of differences in traffic.

  • Views and traffic: Which channels showed interest in which topics? Don't compare the cumulative views of a post that's been up for a while with one that just went live.
  • Read depth: See how far down people read, and check whether key information sits too far down the post. Take the length of the post into account as well.
  • Link clicks: Did readers go on to related posts or hiring information? Clicking a hiring link and submitting an application are different actions. Completed applications have to be checked separately in your hiring system.
  • New questions: Keep what candidates and colleagues wanted to know more about as topics for next month.

When traffic is low, a handful of visits can swing the ratios dramatically. Instead of jumping to conclusions, adjust the title, the distribution channel and the links between posts one at a time, and write down what you observe.

Turn the first month's plan into your team's document.

Take the weekly briefs together with fields for owners, deadlines, published URLs and a month-end retrospective. Keep only the items you need and fill in your real schedule.

No login needed. Use it right away.

Show the planning sheet text