How to Test a Career Before Changing: A 30-Day Plan

What does testing a career actually involve?

Testing a career means doing the real work in small, reversible doses before you spend money or hand in your notice. A proper test has three parts: conversations with people doing the job right now, one piece of paid work that someone actually cared about, and one unpaid project you finish end to end. Reading job ads isn't testing. Neither is a weekend of tutorials. You're after contact with the parts of the job nobody advertises — the admin, the third round of revisions, the client who changes their mind on a Friday afternoon — because that's what you'd be living with, not the highlight reel.

Before you start, write your hypothesis in one sentence and make it falsifiable. Not "I think I'd like UX" but "I believe I'd enjoy turning messy user feedback into wireframes, and someone would pay me for it within a month." A vague hypothesis gives you a vague answer, and a vague answer keeps you stuck for another year. Pin down the specific role, the specific task you think you'd enjoy, and the specific proof that would change your mind. Then design 30 days that either produce that proof or don't.

The whole thing runs alongside your current job. Thirty days is deliberately short — long enough to hit a real deadline and a real setback, short enough that you can't drift. Budget roughly 25 to 35 hours across the month: a few evenings a week plus two weekend blocks. If you can't carve that out, that's data too. A pivot needs more than 30 hours eventually, and it's better to learn about your capacity now than three weeks into a course you've already paid for.

Why run a 30-day test instead of paying for a bootcamp first?

Because a bootcamp answers a question you haven't asked yet. Full-time tuition in 2026 averages roughly $13,000 to $14,000 for about 14 weeks, with programs running from free up to $20,000-plus — and none of that money tells you whether you enjoy the daily work. It tells you whether you can pass a course. Those are different questions, and people conflate them constantly. Training is excellent at closing a skills gap you've already confirmed you want to close. It's a terrible instrument for discovering what you like.

Sequence matters more than intensity here. Evidence first, tuition second. Once you've done a paid gig and a real project, you'll know exactly which gap is blocking you — and it's often narrower than a full program. Plenty of people find they need three specific skills, not fourteen weeks of curriculum, which is the honest case for career change without going back to school. Others discover the opposite: the gap is genuinely deep and structured teaching is the fastest route. Both are good outcomes. You just want to find out for $0 rather than $13,000.

Employer-built job simulations are a useful warm-up before any of this. They're free, self-paced, and typically take one to six hours, and they show you the actual tasks a role involves at a large company. Treat them as a preview rather than proof — nobody depended on your output, and no one paid for it. They're the cheapest possible way to rule out a direction before you spend a single evening chasing a client.

How do you set up three practitioner calls in week one?

Send fifteen short, specific messages on day one and you'll get three calls by day seven. Aim at people one or two years ahead of you, not directors — they remember the switch, they're less guarded, and their inbox is quieter. Your message should name the person's actual work, state your situation in one line, and ask for twenty minutes. Something like: "I saw you moved from teaching into instructional design in 2023. I'm weighing the same move and testing it properly before I commit. Could I ask you six questions for twenty minutes?" Warm introductions convert best; former colleagues and alumni groups are the obvious first place to look.

Then ask the questions people avoid. "How did you get into this?" is flattering and nearly useless — everyone tells a tidy story in hindsight. Ask instead: walk me through last Tuesday, hour by hour. What did your worst week this year look like? Who pays for this work in this city, and what's the realistic entry band? What makes you not hire someone with my background? What part of the job did you expect to hate and don't, and the reverse? Write the answers down the same day, in their words.

Three calls is the minimum because one enthusiast will oversell the field and one burnt-out person will torch it. The third breaks the tie. Look for what shows up in all three descriptions — that's the job. The bits that appear only once are usually about a specific employer, not the career. And listen hard to the worst-week answers. Deciding whether a career change is right for you is mostly a question of whether you can tolerate its low points, not whether you'd enjoy its best day.

How do you land one paid freelance gig while you're still employed?

Charge a small fee for a tightly scoped piece of work and deliver it in under two weeks. The money isn't the point — being paid changes the psychology on both sides. A paying client gives you a deadline, honest feedback, and the right to say your work wasn't good enough. Free work rarely does. Start close to home: a small business you already buy from, a colleague's side venture, a nonprofit with a tiny budget, a friend's employer. Warm leads beat marketplace bidding when you have no track record and 30 days on the clock.

Scope it down until it's almost embarrassingly small. One landing page, not a website. One dashboard answering one question, not an analytics function. One onboarding email sequence, not a lifecycle strategy. Small scope is what makes a stranger say yes to an unproven person, and it's what lets you actually finish while holding down a full-time job. Price it low but never at zero — $150 to $400 is plenty for a first gig. Then deliver on time and ask one question afterwards: would you hire me again for this?

Two practical warnings. Check your employment contract before you invoice anyone; plenty of them restrict outside work or anything touching your employer's market, and you don't want to test a new career by losing the current one. And remember what this gig does and doesn't prove — it shows you can produce the output and that someone values it, but freelance client work feels different from the same role in-house, where you'd have meetings, stakeholders and a roadmap. Your practitioner calls fill in that gap.

What does a volunteer project prove that a paid gig can't?

A volunteer project tests whether you'll finish the work when nothing forces you to. That's the single most useful signal in the whole 30 days. Money and a client's expectations can carry you through a task you secretly hate; an unpaid project can't. If you're still opening the file at 9pm in week three with no invoice waiting at the end, you've learned something no aptitude quiz will tell you. And if you quietly abandon it, that's not a character flaw — it's your test working exactly as designed, at a cost of zero dollars.

Pick something with a real recipient and a hard end point. A community group's newsletter migration, a local charity's donor data cleanup, a small open-source fix, a sports club's booking spreadsheet rebuilt properly. Set the scope and the delivery date in writing on day one, cap it at 10 to 15 hours, and tell the person you're doing it for. A deadline you announced to someone else behaves very differently from one you kept in your head.

Guard against the classic trap here. Unpaid work expands to fill whatever space you give it, and a grateful organisation will happily hand you three more jobs. One deliverable, one date, then stop. You're gathering evidence, not adopting a second employer. The artifact you walk away with — a finished thing plus someone willing to vouch for it — is what makes a career-change CV credible later on.

What should you actually measure during the 30 days?

Track four things after every session, in one line: hours worked, your energy on a 1-to-5 scale when you stopped, the specific task you avoided, and the skill gap that just showed up. Two minutes a night. By day 30 you'll have a log that beats memory, because memory rewrites itself around whatever you already wanted to believe. People talk themselves into pivots on the strength of one good Saturday and out of them on the strength of one bad Tuesday.

Score your energy afterwards, not before — anticipation and experience are different measurements, and only one of them predicts how you'll feel two years in. The avoidance column is the one to watch. If the same task keeps getting pushed to tomorrow, look hard at it, because it's usually the job's core, not a side detail. Someone testing a move into data work who avoids talking to stakeholders every single time isn't in the wrong career; they're in the wrong version of it.

Keep a fifth line for vocabulary. Every time a practitioner or client uses a term you had to look up, write it down. That list becomes your keyword bank for job ads, your reading plan, and later your CV. Thirty days of real work leaves you speaking the field's language, which is the thing that separates career changers who get callbacks from ones who sound like tourists.

What are the go/no-go criteria on day 30?

Decide the criteria on day one, in writing, and don't renegotiate them on day 30. You go if you delivered the paid gig and the client would rehire you, you finished the volunteer project, all three practitioners described a worst week you could genuinely live with, your energy scores averaged above 3, and you can name ten employers or clients within reach who pay for this work. Miss two or more and it's a no — or at least a not-yet.

Half the value of this exercise is having a rule you set before you were emotionally invested. On day 30 you'll be tired and either infatuated with the new field or sick of it, and neither state is a good place to make a decision worth years of your life. So write the scorecard first, print it, and score it honestly. If you find yourself arguing with your own criteria, that argument is itself the answer.

Add one financial check that people skip. Map a realistic path back to your current income and put a number of months on it. If the arithmetic only works when every assumption breaks your way — you land a role in eight weeks, at the top of the entry band, with no gap in between — it's not a plan, it's a hope. A test that comes back "yes, and it'll cost me 18 months of reduced income" is still a yes. You just get to prepare for it.

What if the test comes back no — or almost?

A no costs you about 30 hours and zero tuition, which makes it the cheapest good outcome available. You've eliminated one option with real evidence instead of carrying it around as a fantasy for another three years. Write down exactly which criterion failed and why, then keep the log — six months from now you'll be tempted to reopen the same idea, and your own notes are the fastest way to settle it.

More often the result is "almost." You liked the craft and hated the client management, or the work was right but the setting was wrong. That's a signal to rerun the 30 days with one variable changed, not to scrap the whole direction. Someone who enjoys building reports but dreads chasing clients should test the same skill in-house instead of freelance. Change one thing, run it again, keep the same scorecard. Two or three cycles of this beats a year of speculation.

Here's the opinion I'll defend: the people who get stuck aren't the ones who fail the test, they're the ones who never define what failure looks like. An unfalsifiable career dream can't be tested, so it never dies and never happens. Give yours a fair, specific, 30-day chance to prove itself — and let it lose if it loses.

How do you turn 30 days of evidence into a CV that gets callbacks?

Put the new-field evidence above your employment history, not buried at the bottom. Career changers usually have proof by this point — a paid client, a finished project, the field's vocabulary — and then hide it under twelve years of unrelated job titles that a recruiter reads first and stops at. A "Selected projects" block near the top, with two or three entries written as problem, action and measurable result, does the repositioning work that a personal statement never manages on its own.

Write those entries the way the target field writes them, using the exact wording from real job ads you've collected. Keep your old roles, but rewrite the bullets to surface transferable skills — budget owned, people managed, processes fixed, decisions made — instead of duties that only made sense inside your former industry. Then add one honest line explaining the pivot; a single sentence about why you moved and what you've already delivered beats a defensive paragraph. If you're rebuilding from scratch, an AI CV builder will keep the structure ATS-friendly while you focus on the content.

Before you send it anywhere, check how the document reads to a machine and to a stranger skimming for six seconds. Applicant tracking systems parse your file into fields, and career-change CVs get mangled more than most because the relevant experience sits in unusual sections. Running the draft through a free CV analysis shows you the missing keywords from your new field, the sections that parse badly, and where your evidence still isn't obvious. Fix those, then start applying — with 30 days of proof behind you rather than an expectation and a hope.

Frequently asked questions