Call notes from a first conversation. Anonymised, shared with consent.
This call was with someone about twenty, just off an internship, holding a full-time offer that starts in a few months. The company is a D2C startup roughly eighteen months old, under ten people, a mix of full-time and contract. The role is positioned loosely as Founder's Office, which in practice means generalist.
The company runs across finance and compliance, operations and assembly pilots, and cross-border manufacturing between China and the US. High founder involvement, long hours, scope that moves.
What he thought was wrong
He described it as confusing and unstable. Work switches between finance, operations, marketing and research without warning. Projects get started, paused, or scrapped. He's handed tasks he has no experience with, then asked to follow up with people two decades his senior. Founder expectations shift mid-way through. The boundary between work and everything else is unclear.
Underneath that sat the real worry: that he wasn't building expertise, that being spread thin would cost him depth, that he had no authority when dealing with senior external stakeholders, and that committing three years to this might be a mistake.
What I asked
Before treating it as a problem, I wanted to know whether it was a mismatch. Are you uncomfortable with uncertainty, or just new to it? Do you expect projects to ship? Are you optimising for learning or for stability right now, and do you want depth immediately or exposure first?
Then I set one expectation explicitly, because nobody had: plenty of projects at an early-stage company will never see daylight. That doesn't make the work wasted, and treating every scrapped project as a personal failure will exhaust him by month four.
What became clear
The role was behaving exactly like a Founder's Office role at an early-stage company. Task switching wasn't accidental; it's structural. Authority in that seat is positional rather than age-based, so the twenty-year-old chasing a forty-year-old vendor is normal, not a glitch. Friction with founders is close to guaranteed in a role that sits that close to them. Work-life balance in this setup gets negotiated through behaviour, not contract.
None of that is dysfunction. It's early-stage reality meeting first-job expectations, and the collision is loud the first time.
The real problem
Not skill, not intelligence, not effort. Framing.
He was reading the role through corporate career logic: linear growth, predictable scope progression, specialisation on a schedule. What the role actually demands is comfort with abandoned work, authority built on respect rather than title, emotional regulation when a founder contradicts himself, and patience with the fact that clarity about specialisation arrives late.
Without that shift, the role will keep feeling destabilising even when it's working correctly.
What I told him
Generalist roles optimise for exposure. Depth comes later, by choice, once you know what you want depth in. Managing people more senior than you is normal here, because the authority comes from the mandate. Founders will contradict themselves, and that's decision-making under uncertainty rather than a personal failing.
Work-life balance in a role like this is about responsiveness, not constant labour. Unblocking someone in four minutes at 9pm is a different thing from working sixteen hours, and treating them as the same thing is how people talk themselves out of jobs they could have handled.
The last point was the one that mattered: this role only makes sense if learning is the primary goal. If stability is the priority right now, this is the wrong phase of company to join.
How it ended
No decision on the call. What shifted was the framing.
Not "something is wrong with this role," but "this role demands a mindset I need to consciously opt into."
Early in a career, that distinction is worth more than the job title.