Employer Brand
Field Notes
My personal approach to building, running and measuring employer brand work.
A collection of methods, questions, tools and lessons shaped by 15 years of work across marketing, communications, talent attraction and employer branding.
Not a universal framework. Just the way I have learned to approach the work.
Employer Brand is not one campaign. It is a system of decisions, experiences and signals.
11 topics. One connected way of working.
A more complete picture.
Starting With the Business Problem
Before channels, I need to understand what actually needs to change.
Understanding the Talent Market
Research before assumptions.
Finding the Employer Story
From evidence to EVP and proof.
Designing the Candidate Experience
A consistent experience from awareness to onboarding — and beyond.
Building the Talent Brand Ecosystem
Career site, channels, community, CRM and discovery working together.
Turning Strategy Into Activation
From strategy to campaigns, content, events and channels.
Building With Employees
Advocacy, storytelling and recruiter enablement.
Working Across Teams
Collaboration, influence and shared ownership.
Keeping Projects Moving
Scope, owners, budgets, risks and delivery.
Taking Employer Brand Into New Markets
Same employer. Different talent realities.
Measuring What Matters
Connecting attention to actual hiring outcomes.
Before activity, I want clarity.
I try not to start with “we need a campaign.” I start with the business and hiring problem, because the same brief can require very different solutions.
How I approach it
Problem → evidence → scope → outcome
I separate the symptom from the problem. Low applications may be an awareness issue, a weak proposition, a channel issue, a conversion issue — or simply the wrong target audience.
My working tool
One page with: business context, hiring priority, target segment, evidence, hypothesis, constraints, desired behaviour change, KPI and decision owner.
If I cannot describe the problem without naming a channel, I probably have not framed it yet.
Questions I ask
- What are we trying to change?
- Why now?
- Which talent segment matters most?
- Where in the funnel is the real friction?
- What evidence do we already have?
- What will be different if this works?
From my experience
When “more promotion” was not the whole answer
In technical hiring projects, I have seen teams ask for more traffic while the real issue sat deeper in the message, audience fit or conversion path. My work increasingly moved upstream: clarify the hiring problem first, then choose the marketing response.
I spend more time agreeing on the problem, decision owner and success criteria before production starts. It feels slower for one meeting — and saves time later.
Research before assumptions.
A talent market is not just a list of competitors. I want to understand what candidates repeatedly see, what they value, what they distrust and where an employer can still sound different.
How I approach it
Four layers of talent intelligence
I combine job ads, career pages, employer reviews, social content, search behaviour, candidate feedback and my own surveys when possible. The goal is not “research completed”; the goal is a decision.
My working tool
A matrix that captures repeated words, proof points, benefits, hiring intensity, content patterns, channel behaviour and candidate questions.
What is market standard, what is overused, what is credible, and where there may be room to differentiate.
Questions I ask
- Who are we truly competing with for this talent?
- What promises are candidates hearing everywhere?
- Which claims have proof?
- What are people complaining about?
- Which needs differ by seniority or market?
- What decision will this research change?
From my experience
Original research became a working habit
I have run candidate surveys with 200+ responses and built independent market studies on employer positioning and candidate communications. Research now sits before creative ideation in my process, not after it.
I would validate qualitative patterns earlier with candidates or employees instead of relying too long on desk research. Public data shows what employers say; people tell you what they actually believe.
I do not start EVP work with a slogan. I start with evidence.
For me, a useful EVP sits where employee reality, candidate relevance and business truth overlap — and every promise needs proof.
How I approach it
My EVP path
I have often worked with employer messages and EVP activation. This framework formalises how I approach the full development question: evidence first, promise second, activation last.
My working tool
Candidate need · Employee truth · Business relevance · Competitor territory · Employer promise · Reasons to believe · Audience variation · Risk / overclaim check.
A strong EVP is not what sounds attractive. It is what the right people recognise as true.
Questions I ask
- What can we actually prove?
- What matters to the talent we need?
- What do employees describe without prompting?
- What are competitors already claiming?
- Where is the gap between promise and reality?
- How should one EVP flex by audience?
From my experience
Turning real technical culture into candidate language
My employer brand work has repeatedly required translating engineering reality into messages candidates can understand — without replacing substance with generic culture language. That discipline is the foundation of this EVP approach.
I would involve employees and recruiters in validation earlier. A positioning can look elegant in a deck and still fail when recruiters cannot use it or employees do not recognise themselves in it.
The employer promise is tested after the ad.
Candidate experience is where employer branding becomes behaviour. Every message, wait, interview, rejection and handover can strengthen or break the promise.
How I approach it
The journey I map
At each point I look at candidate question, emotion, friction, employer action, owner and metric. I pay special attention to the moments where silence or inconsistency changes how the whole brand feels.
My working tool
Touchpoint · Candidate question · Expected feeling · Actual friction · Employer response · Owner · SLA · Metric · Recovery action.
The Life After NO explores one specific part of the journey: what rejection communication does to future candidate interest.
Questions I ask
- Where does the promise become an experience?
- What does the candidate not know right now?
- Which waits create unnecessary anxiety?
- Where do teams hand the candidate over?
- How do we close the loop after rejection?
- What should we learn from candidate feedback?
From my experience
Communication is part of the brand
My work around recruitment funnels and candidate communications led me to a simple conclusion: campaigns cannot compensate for a poor post-click experience. I now look at attraction and candidate experience as one connected system.
I would define candidate communication standards and ownership at the beginning of a hiring campaign, not treat them as a recruiting-only layer that starts after marketing has done its job.
I think in connected touchpoints, not isolated channels.
A candidate may meet the employer through search, LinkedIn, an employee, a job page, an event, a review site or an AI answer. The experience should still feel connected.
How I approach it
Owned, earned, paid — plus nurture
My strongest hands-on experience has been in campaigns, communities, landing flows, UTM attribution and recruitment-funnel analytics. I use this ecosystem model to connect those strengths with career-site, CRM and nurture decisions.
My working tool
For every touchpoint: role, audience, content, owner, next action, data captured, KPI and handoff. It makes gaps visible — especially the “what happens next?” moments.
No suitable vacancy should not automatically mean the relationship ends.
Questions I ask
- Where do candidates discover us?
- Where do they verify what we say?
- What happens if no role fits today?
- Which channels collect useful signals?
- Where do we lose attribution?
- Can candidates find us through search and AI?
From my experience
From click to ATS, not just reach
I have built recruitment marketing flows where UTM structure, analytics and ATS stages connect promotion to applications, interviews, offers and hires. The next step is treating the full digital ecosystem with the same discipline.
I would involve the career site and CRM layer earlier in campaign planning. If a campaign creates demand but the ecosystem cannot capture or nurture it, some of the value disappears.
A channel is a choice, not a strategy.
This is the part of employer branding where I have spent much of my hands-on time: turning a hiring or reputation problem into a message, format, channel mix and measurable launch.
How I approach it
Problem → audience → message → format → channel → learning
I work across paid promotion, technical communities, events, social content, special projects and partnerships. I try to make the channel earn its place in the plan.
My working tool
Objective · audience · insight · proposition · channel role · creative format · CTA · attribution · cost assumption · KPI · stop / scale rule.
Every asset should have one job in the candidate journey.
Questions I ask
- Why this channel for this audience?
- What behaviour do we want next?
- What will make the message credible?
- What do we test first?
- How do we know quality, not only volume?
- What would make us stop spending?
From my experience
Performance + creative, not either/or
I have run tech talent campaigns across Telegram, social, content partnerships, events and employer-brand special projects. In one campaign, a better message/channel fit contributed to a 7× CTR improvement. In community work, coordinated promotion helped add 1,000+ relevant followers.
I would document the hypothesis behind each activation more consistently. Good execution tells you what happened; a clear hypothesis helps you understand why.
Employees are evidence, not advertising inventory.
The most credible employer stories usually come from people doing the work. My role is to make participation easier without turning employees into scripted corporate channels.
How I approach it
Advocacy needs choice, support and proof
I separate employee advocacy from employee content production. Advocacy is voluntary distribution and voice; storytelling is the content system; recruiter enablement turns the same proof into candidate conversations.
My working tools
Ambassador selection · content prompts · guardrails · support model · content calendar · EVP proof library · audience talking points · common objections · reusable assets.
Give people tools, not scripts.
Questions I ask
- Who already wants to tell the story?
- What can only an employee credibly say?
- How much support is actually useful?
- What should recruiters be able to prove?
- How do we avoid forced advocacy?
- What signals tell us the programme has value?
From my experience
Technical people make the brand real
Many of my strongest employer-brand projects have depended on engineers, speakers, experts and community contributors. The lesson is consistent: the brand becomes stronger when the expert stays recognisably themselves.
I would build advocacy as an operating programme earlier — with clear participation paths, reusable prompts and measurement — instead of relying mainly on individual content opportunities.
Employer Brand rarely owns everything it needs.
Cross-functional work is not just “good communication.” It is the ability to align different goals, make ownership visible and keep decisions moving without formal authority over every team.
How I approach it
Shared outcome, clear roles
I try to understand both sides of every collaboration: what I need from the stakeholder, and what outcome they need from the project.
My working tool
Stakeholder · desired outcome · contribution · decision rights · dependency · cadence · risk · escalation path.
Alignment is not everyone agreeing with every idea. It is everyone knowing what is being decided, by whom, and why.
Questions I ask
- Who owns the final decision?
- Who can block delivery?
- What does success mean to each team?
- Which input is needed, and when?
- Where are priorities in conflict?
- What needs to be documented?
From my experience
Working through a large recruiting organisation
My projects have required coordination across recruiting, HR, design, analytics, procurement, legal, vendors and leadership. I have also helped standardise marketing and tracking processes for a broad HR stakeholder group, where influence mattered more than formal authority.
I would define decision rights earlier on complex projects. Many “communication problems” are actually ownership problems in disguise.
A good idea is not yet a project.
For me, project ownership means turning an idea into scope, workstreams, owners, milestones, budget, risks, decisions and a measurable finish — then learning from what happened.
How I approach it
My project spine
I also define vendor deliverables, acceptance criteria, decision points, prioritisation rules and what I need to report upward when status changes.
My working tools
Goal · scope / out of scope · workstreams · owner · milestone · budget · resource · dependency · risk · vendor · decision point · KPI.
Green: on track. Yellow: risk needs action. Red: decision or scope change required.
Questions I ask
- What is in and out of scope?
- What can delay the critical path?
- Where is the budget most sensitive?
- What does the vendor need to deliver?
- What gets deprioritised if capacity changes?
- What decision does leadership need from me?
From my experience
Delivery under constraints — and learning from misses
One technical event campaign had a target of 80 registrations, eight production days and no media budget; it delivered 91 registrations and 64 attendees. In another partner-led project, late inputs, broken tracking and weak reporting taught me to formalise pre-launch checks, owners, acceptance criteria and measurement requirements much earlier.
I escalate risks earlier and with a recommendation, not only a status. “This may slip” is useful; “this may slip because X, and I recommend Y” is project leadership.
Global consistency does not require identical execution.
When the talent market changes, I keep the employer truth stable and re-check relevance, proof, competition, channels and cultural context.
How I approach it
Global core → local relevance
I do not treat localisation as translation. I look for what should stay globally consistent and what needs a different emphasis to make sense in the local talent context.
My working tool
Market · talent segment · competitor context · candidate need · strongest EVP pillar · local proof · message adaptation · channel behaviour · risk / sensitivity · KPI.
I have used Cyprus and other European talent markets in independent research to test and refine this way of thinking.
Questions I ask
- What does this audience already know about us?
- Which needs are local vs universal?
- What proof travels well?
- Which phrases lose meaning in translation?
- Who are the real local talent competitors?
- What should we test before scaling?
From my experience
Researching before claiming
My international work currently leans most heavily on market research, content and talent-attraction analysis rather than end-to-end ownership of a global employer-brand programme. This framework is how I structure the problem responsibly instead of assuming one market behaves like another.
I would build local validation into the plan from day one: local recruiters, employees and candidates should challenge the assumptions before a global team invests in scale.
I try not to measure activity when I can measure change.
Reach matters. Applications matter. But the strongest measurement system connects attention, consideration, candidate behaviour, quality, hiring and experience — and shows which decision the data should change.
How I approach it
My measurement ladder
I connect channel metrics to recruiting-funnel metrics where the data allows it: source, campaign, application, interview, offer, accepted offer, hire and cost. For broader employer brand work, I add preference, associations, sentiment and candidate feedback.
My working tool
Awareness: reach, search, direct traffic. Consideration: engagement, career-site behaviour, brand association. Intent: job views, apply starts. Quality: qualified applications, interview conversion. Hiring: offers, acceptance, hires. Experience: candidate feedback, re-entry.
Questions I ask
- What decision will this metric support?
- Can we follow the signal further down the funnel?
- Are we measuring volume or quality?
- What is the baseline?
- Who needs this report and at what level?
- What would make us change the plan?
From my experience
Attribution all the way to hiring stages
My recruitment-marketing work has included structured UTM tracking and funnel reporting from traffic and applications through interviews, offers and hires, plus cost metrics. I have also designed dashboard requirements intended to make weekly optimisation possible, not just monthly reporting.
I would pair performance data with brand-health and candidate-perception measures earlier. Funnel data explains behaviour; perception data helps explain why that behaviour exists.
“Better talent decisions start with better questions.”The work continues. And so do the notes.
Olesia Botsieva
Employer Brand · Recruitment Marketing · Talent Attraction
I work at the intersection of marketing and hiring: talent audiences, employer positioning, recruitment campaigns, research, analytics and cross-functional projects. These Field Notes are not a universal method. They are the working principles I have built, tested, questioned and refined over years of practice — including the lessons that came from things that did not go perfectly.
Useful work is never really “finished.” It gets sharper.