100 Job Strategies
100 Job Strategies · 8 of 100
Shadow Work
Spend four weeks doing the job nobody hired you for. Then show them.
In short
Shadow work means picking a company, doing the actual work of the role publicly for a few weeks, and publishing the output. It is the most reliable way for a fresher with no experience to beat a fresher with a degree, because it replaces the question of whether you could do the job with evidence that you already have.
The situation
Two graduates apply for the same marketing role.
The first has a good degree, a tidy resume, and a cover letter explaining that they are passionate about brand storytelling.
The second sends a link. For the past month they have published a weekly teardown of the company's competitors' ad campaigns — what each was trying to do, what worked, what they would change. Eleven posts. Some of them have comments from people in the industry.
The hiring manager has to imagine whether the first person can do the job. They can simply read whether the second one can.
Why this works
Every entry-level hiring decision is a bet made with almost no information. Degrees are weak signals because everyone applying has one. Internships are better but heavily gated by who you already knew. Cover letters are unverifiable by construction.
Shadow work removes the bet. Instead of describing capability, you produce a body of work that demonstrates it — and crucially, you do it in public, on a schedule, so it also proves the thing employers worry about most in juniors: whether you will actually keep going when nobody is checking.
The consistency is doing as much work as the quality. Anyone can produce one good piece. Four weeks of shipped output shows persistence, self-direction and the ability to work without a manager — the exact traits that make a junior hire low-risk.
It also inverts the power dynamic in a way that compounds. Published work gets found. People in the industry comment on it, share it, and occasionally hire directly from it. You stop being one of 300 applicants competing for attention and become a person with a visible track record that arrives before your application does.
The final advantage is that it works when nothing else is available to you. No network, no referrals, no experience, no permission required. You do not need anyone to say yes before you start.
How to run it
- 1
Pick the actual work, not a proxy
Not a course, not a certificate, not a tutorial project. If the job is writing ad copy, write ad copy. If it is analysing data, analyse real public data. The output must be the same kind of artefact the job produces.
- 2
Choose a narrow, repeatable format
One teardown a week. One dashboard a week. One rewritten landing page a week. A repeatable format is what makes four weeks sustainable and makes the body of work look deliberate.
- 3
Work on real companies, publicly
Use real products, real campaigns, real public datasets. Invented case studies are visibly invented and carry a fraction of the weight.
- 4
Publish where it can be found
A simple site, a public repository, a professional network, a newsletter — anywhere with a stable link. If it cannot be linked in one line, it does not function as evidence.
- 5
Ship on a schedule for at least four weeks
The cadence is the proof. Four consecutive weeks of published work says more about your reliability than any reference, and two or three pieces is not yet a pattern.
- 6
Send the link, not the resume
When you apply or reach out, lead with the body of work. The resume becomes supporting material rather than the thing being judged.
What to say
When it does not work
- Publishing three pieces and stopping. The cadence is the entire signal. An abandoned series is worse than none, because it demonstrates precisely the thing employers fear about junior hires.
- Choosing something adjacent to the job instead of the job. A design certificate is not design work. A course project is not an analysis. If it does not look like the artefact the role produces, it does not transfer.
- Publicly criticising the company you are applying to. Analysing their competitors is smart; publishing a harsh critique of the hiring manager's own work is a gamble that usually loses. Keep the tone constructive throughout.
- Perfectionism preventing publication. A good piece published weekly beats an excellent piece published never. The whole mechanism depends on shipping.
- Using confidential or scraped-private data. Stick to genuinely public sources. Building your portfolio on data you should not have is disqualifying rather than impressive.
Nobody has to give you permission to start doing the job. Do it in public for a month and the evidence argues for you before you ever speak.
Questions
How is this different from a portfolio project?
A portfolio project is usually one polished artefact built once, often from a tutorial, and frequently invented. Shadow work is a series produced on a schedule against real companies or real public data, which demonstrates two additional things a single project cannot: that you can direct your own work without a brief, and that you keep going when nobody is checking. For junior hiring, those two signals are frequently more decisive than the quality of any individual piece.
Four weeks feels like a lot of unpaid work. Is it worth it?
It is a real cost and worth weighing honestly. The case for it is that most entry-level applications cost you time and produce nothing reusable, whereas shadow work compounds: the same body of work supports every application you make afterwards, gets found independently, and frequently opens conversations that never came from applying. If you are sending dozens of applications into silence, redirecting some of that time into visible output usually has a better return than sending more of them.
What if my field does not have publishable output?
Most do, though the artefact differs. Operations and logistics can publish process breakdowns and efficiency analyses of public systems. Finance can publish analyses of public filings. HR can publish teardowns of public job postings and hiring processes. Teaching can publish explanations and materials. The test is not whether you can share company work — you cannot — but whether you can produce the same kind of thinking against publicly available subject matter.
Should I tell the company I did this specifically for them?
Frame it as work you did because the subject interested you, which should also be true. Presenting a body of public work as though it were produced solely to impress one employer makes it look transactional and slightly diminishes it. The stronger framing is that you have been doing this work anyway, it happens to be exactly what the role involves, and they are welcome to read it as a work sample.
More from 100 Job Strategies
- Backfill Sniping
- The Funding Lag
- The Unsolicited Audit
- The Vendor Side Door
- Repost Archaeology
- Ex-Employee Networks