What Are You Going To Do With Your Life

Actually Figuring Out What To Do Next

I spent three years trying to reverse-engineer a decision-making framework for career direction. It didn't work. I collected books, watched interviews, did personality tests, made spreadsheets with weighted criteria. The only thing it gave me was a lot of tabs open and a deeper sense that everyone else seemed to have gotten something I hadn't. The answer isn't a method. It's a process of elimination that takes longer than you want it to.

What Are You Going To Do With Your Life

This question is poorly designed. It asks for a permanent answer to a temporary state. When someone asks it at twenty-two, they're asking you to predict the next forty years. When someone asks it at thirty-eight, they're usually asking because something broke. The question itself is the problem, not your inability to answer it convincingly. I learned this the hard way after a friend asked me this at a dinner party and I tried to give a polished five-year plan answer. I'd been between roles for eleven months. The plan was imaginary. The question deserved an honest one, but neither of us knew how to have that conversation in a room full of people who had been doing the same performance for years.

The Actual Mechanics

Here's what works, and it's unglamorous. You run small experiments. Not grand life pivots. Small ones. Two-week stints where you actually do the thing you're curious about, not the idea of the thing. Most people confuse the aesthetic of a career with the daily reality of it. They want to be a filmmaker, which means renting equipment and saying they're working on a project. They don't want to be sitting in a parking lot at 2 AM waiting for the light to change so they can get the shot. I found this out trying to break into data engineering. I thought I wanted the work. Then I spent a month actually doing it, and the work was mostly debugging connection strings and arguing with product managers about schema changes. Neither of those things appeared in the job description. I stayed anyway, because the debugging became interesting once I stopped expecting it not to happen. The trick is running enough experiments that your preferences emerge from actual experience rather than from other people's descriptions. Most of us form career opinions based on trailers. We never see the actual movie.

One Edge Case That Surprised Me

There's a specific failure mode I hit where the experiment itself contaminates the data. I was exploring whether I'd enjoy technical writing. I wrote three articles, submitted them, got rejected by two publications and accepted by one. The acceptance felt like validation. It wasn't. I was accepted because the topic was trending, not because I enjoyed the work. I spent the next six weeks drafting follow-ups and felt nothing. The signal was noise. The workaround was tracking my energy, not my outcomes. After each writing session, I logged how drained or energized I felt, not whether the piece got published. The pattern was clear within two weeks. I prefer explaining systems to other engineers. I don't prefer crafting narratives for general audiences. The jobs overlap. The work is different. My rejections had been misleading me about what I actually wanted.

Common Pitfalls

The biggest one is treating your twenties like a preparation phase. They're not. They're the actual thing. Every year you spend "getting ready" is a year you're not running experiments. I watched a colleague do this for five years, stacking certifications and side projects, convinced he was building toward something. He was just building a resume. When he finally landed the role he thought he wanted, he quit in six months because the preparation had become the identity. Another pitfall is the assumption that clarity precedes action. It doesn't. Action produces clarity. You don't figure out what you want by thinking harder. You figure it out by doing things and noticing which ones leave you feeling neutral rather than resentful. There's also the comparison trap, which is just another word for consuming other people's highlight reels and treating them as baseline data. Social media has made this worse. You see someone post about their dream job and assume they've solved the problem. They haven't. They've solved a different problem: presenting a solution that looks clean. Their actual week probably involves things they'd never post about.

What Actually Moves the Needle

Talk to people who are doing the work, not the work as they describe it. Ask them what their Tuesday looks like. Ask about the last time they wanted to quit. Ask what they wish they'd known before they started. The answers are never what you expect, and that's the point. You're collecting ground truth, not inspiration. Keep a decision journal. Write down what you think you want, why, and what evidence would change your mind. Review it every three months. You'll be surprised how often your actual behavior diverges from your stated preferences, and how often the divergence points toward something useful. I started doing this after a mentor pointed out that I was applying for senior roles at companies where I'd have been the most junior person in the room. The journal showed the pattern. I kept optimizing for title instead of learning velocity. The title was a proxy I'd mistaken for the thing itself. Fixing that single confusion changed my trajectory more than any course or book ever did.

The Hard Part

You have to be willing to look silly. Most people won't admit they're figuring it out as they go, so if you say it plainly, you'll feel like the only one. You're not. The people who seem sure are usually just better at hiding the uncertainty. A lot of them are also wrong about their own trajectory and just haven't hit the correction yet. There's also the financial reality. Running experiments costs money, and not everyone has the runway. If you're already working, the lowest-friction path is finding adjacent tasks within your current role that let you sample different work without quitting. I transitioned from support to engineering by volunteering for the migration scripts nobody wanted. It was unpaid, barely relevant to my actual job, and it gave me six months of real experience that let me apply elsewhere with something concrete to show.

When This Approach Fails

It fails when you need immediate income and can't afford to sample. In that case, you optimize for options, not passion. Take the job that keeps the lights on but leaves you mental capacity to experiment on the side. The trap is letting the survival job consume all your time and energy until there's nothing left for anything else. Set a hard boundary, even if it's just one evening per week where you do something unrelated to making money. It also fails when your environment doesn't allow experimentation. If you're caring for family, working multiple jobs, or in a location with limited opportunities, the framework shifts. You optimize for small, high-signal actions instead of broad exploration. A single conversation with someone in a different field is worth more than another self-assessment quiz. One informational interview beats ten hours of research because it gives you data you couldn't generate alone.

A Note on Timeframes

Give yourself permission to take longer than you think you should. The pressure to have it figured out by thirty is cultural, not practical. People change careers at forty, fifty, sixty. Some of them do it successfully. The ones who don't usually failed because they rushed into the first plausible option rather than continuing to explore. I'm past the age where I expected to have answers. That's not resignation. It's efficiency. I stopped wasting cycles on pretense and started spending them on actual experimentation. The results improved immediately because the input improved. Less performance, more signal.

What I Actually Tell People Now

Stop trying to answer the big question. Answer smaller ones. What kind of work makes you lose track of time? What kind of work drains you even when it's interesting? Who do you enjoy working with, and what does that tell you about the environments you need? What problems do you notice yourself solving for free? These questions have answers. The big one doesn't, because it's not a real question. It's a placeholder for a bunch of smaller questions that haven't been asked yet. Once you start asking the smaller ones, the big one answers itself through accumulation rather than revelation. I used to dread the question. Now I recognize it for what it is: a prompt to check in, update the journal, and run one more experiment. Not dramatic. Not final. Just the next step.