Your guide to (successfully!) using projects in your marketing hiring
In today's job market, it can be difficult for companies to assess their perfect marketing candidate. Title inflation, mass layoffs at blue chip companies, and a period of easy growth have made it more difficult to accurately assess candidates' skills and experience
One approach you can use to assess fit is to incorporate a project – sometimes called a thought exercise, prompt, etc – into your hiring process. But mention such an ask to any candidate for a senior marketing role, and you’ll get complaints ranging from projects just being free work, reinforcing biases, or a waste of time for both the company and the candidate.
In this article, I'll share my experience based on both giving and receiving, projects as part of the hiring process to outline:
Let's get started!
What are the benefits of incorporating a project?
The addition of a project to the standard interview process allows you to evaluate and compare candidates' abilities on a common task – and not just on what candidates say they’ve done in past jobs.?
Building a project into your hiring helps:
To make sure you achieve these benefits, you have to carefully plan the project you are going to give candidates.? You can’t treat this as an afterthought that you spring on candidates late in the process.? I’ll talk about this more in the best practices section below, but I believe you get the most value out of a project when you approach it as a vehicle for a conversation, and not as having "right" or "wrong" answers.? If you don’t position the project as a conversation, I can guarantee candidates will feel like you’re asking them to do free work.
When candidates are concerned about doing "free work"
Including a project in your hiring process can be a great opportunity for employers and candidates to assess each other. They can also be a quick way to alienate candidates and damage your employer brand if you're not careful.
Here are my best practices for making sure all parties feel comfortable and informed:
I know some employers provide some form of compensation for completing projects – ranging from cash payments to Starbucks cards. I haven't found the need to compensate candidates if you set appropriate expectations and frame the project appropriately.
(And, of course, if you do want candidates to do actual work, why not compensate them for their time?? If the candidates are as good as you think they are, you could get some valuable work done and they’ll feel good about the value exchange.)
Best practices for framing a hiring project
Developing an effective scenario for a marketing project is as much art as science. Having incorporated projects into my hiring for more than a decade, here are some of my best practices:
1. Provide the candidates with a written creative brief – If you can't articulate the project and expectations in a short 1-2 page brief, the task either hasn't been defined enough or the project is too complex for a hiring project. Revise and refine your brief to the point that you'd be comfortable turning it over to an agency or freelancer to execute a paid project.
I never send candidates 30-page slide decks or volumes of background docs. Slides are meant to be presented, and candidates can lose too many details included in the talk track. Sending TOO many background docs can make it feel like you are having the candidates do free work.
领英推荐
My project briefs include:
2. Avoid specific initiatives your company is working on today – While the project needs to be relevant, don't give candidates work they feel you would benefit from directly. Instead, tailor your projects to broader or hypothetical initiatives. For example, how would you structure a demand gen program to drive leads in a new segment? How would you evaluate the effectiveness of our current email campaigns? How would you develop a product launch strategy with a particular focus on sales enablement?
That said, I don't believe in giving people completely made-up scenarios such as launching a new line of taco trucks or selling real estate on Mars. While candidates can roll with these wacky scenarios, I find that the interviewing team has difficulty connecting with the scenario and the quality of the resulting conversation suffers.
3. Avoid projects that require access to specific tools/platforms or proprietary data – If your project requires either tools or data, be prepared to provide those to the candidate. But again, if you start loading the candidate with real-world data and tools, it's going to feel like free work, so be judicious about what you provide.
4. Give enough time, but not too much – I generally give candidates 7-10 days to make sure they have enough time to balance other priorities and feel like they can do good work.? I don’t want to provide too much time, otherwise, they’ll spend too much time trying to make it “perfect” and stress out.? Remember: you've been communicating that the project is coming, so it shouldn't be a surprise, and your brief should be focused enough that the candidate doesn't feel like they have to spend hours spinning their wheels on what to do.
5. Prep your interview panel on expectations and their role – It's as important to prep your internal team on what to expect from the project, as it is to prep the candidate. I like to have candidates presented to a panel of people from sales, product, marketing, etc and it's my responsibility to make sure those interviewers know why they're involved.
I want the interviewers to understand they need to be an active participant in the conversation, and that they should suspend disbelief in any candidate recommendations "we've tried before." Instead, the focus should be on the candidate’s recommendations and the thinking that went into them.
6. Don't expect the final files from the candidate – A surefire way to look like you've been angling for free work is to demand the candidate to send their final assets. Don't undermine your prep work on making this a valuable moment by requiring candidates to give you their work. Unless you're paying them, they own their IP and can decide if they want to share this with you or not.
7. Provide feedback – This should be a given, but it’s surprising how many hiring managers don’t provide feedback on the project itself.? If you ask candidates to work on your project, you have to commit to giving them feedback – in addition to any feedback on the discussion. No one wants to put the effort into a project, and not get feedback on how their ideas landed. If you ask for a project, you owe it to the candidate to give them feedback.
Incorporating project-based interviewing into your hiring
Now that I've shared how and why you should use projects in your hiring, I will admit: I hate receiving these tasks myself.
As a senior marketer, I'm not alone. I recently polled a community of CMOs about projects they had been given and received a flood of horror stories.
Let's be clear: they didn't disagree with the potential value of projects, but many had disastrous experiences and therefore did not feel like they should be used for senior hires.
Digging into their experiences, the common thread from the negative experiences was that the projects weren’t designed or overseen by a marketer.
When you’re hiring for your top marketer, the development of an interview project is often written by whoever thinks they know marketing – a CEO, CRO, or even a board member. The challenge is these folks have experienced marketing but through the lens of their own operational experience.? This can lead to violating the best practices we just discussed for hiring projects.??
How do you reduce the possibility of running a project when hiring your senior-most marketer?
Projects can be incredibly valuable; you just have to invest the time and effort into making it a valuable experience. I believe incorporating these best practices in your projects will enable qualified candidates to show off what they can do, without making it feel like you're abusing them.
Best of luck with your hiring.
CEO | Accelerating Growth & Unlocking Innovation for Corporate Leaders & Private Equity by Recruiting Forward-Thinking Sales, Marketing, eCommerce, Tech, AI, Accounting/Finance & Ops - Full-time/Fractional/Interim
4 个月Great insight and advice on the marketing project interview - you’re a wealth of knowledge Scott Brown!
Director, Digital Marketing @ Laivly - AI for CX
1 年Great read. Thanks for writing this. This is a relevant topic for me right now. I've been asked to do a couple of these. That's ok to demonstrate the knowledge and expertise, however we should not be solving business?problems?within?a recruitment process. Full stop. A 4-6 hour blueprint or marketing plan should be valued as such. Example: How about I come into your office for 1-2 days and I work on it. If you like it, hire me. If you don't pay me for the time. This is different?from a technical assessment. I've seen companies run off with your brain juice. Thanks for the help schmuck. ??
I connect execs with “whispered” roles ... former GTM Exec at 4 unicorns
1 年Terrific article Scott. One other value I find in a project is hearing the candidate convey strategic thoughts to an exec audience. If the role requires talking about metrics in these types on environments, bringing cross functional teams along strategically …. Projects are valuable. Personally If the role isn’t director+ I question projects but for senior roles it feels critical
I also think it's important to be mindful of the time commitment you asking from the candidate and for you to fully understand that you've properly scoped out that time commitment you've outlined. I recently had an interview where they asked me to do a project. In the brief, it stated that they believed it would only take 3-4 hours. When I saw the list of deliverables, it seemed impossible for it to only take 3-4 hours. I conferred with other trusted peers and they also agreed that the project would be at a scale of larger than just 3-4 hours. In the end, it took me two days to complete. I had the same peers review my work and they said it was good, solid work. I presented my work and in the end, they went with another candidate. It was deflating. It could very well be that the other candidate presented stronger material, but what was deflating was the effort I had put in and was given really high-level feedback as to why they went with another candidate. To the article's point, I felt like I had just given them free work of which they will use some elements. It was a lesson to me that if the project that a company assigns a candidate seems overly demanding, it's probably a strong indicator that the company is not a fit.
Risking life and limb for the cause of aligning revenue teams at 6sense.
1 年You probably didn’t include this because it should go without saying: if you include a project, you have to discuss the project! I had a company assign a project, I did it, and then not a single conversation about it during the interview process. Made me feel like I wasted a lot of my own time. That experience aside, I am a fan of incorporating a project or presentation in the interview process.