Working at an early stage startup means your job title describes about sixty per cent of what you'll actually do, and the rest gets decided by whatever broke that morning. I'm writing this as someone who runs engineering recruitment for a scaling SaaS company, but I came to it sideways, after eight years writing code at a London fintech. The startup stint that taught me most about small team working came right in the middle of that move. This is what the work looks like, in the order it tends to arrive.
What a typical day looks like in a small team
The day starts in Slack, not a calendar. There's usually a channel for whatever is on fire (production, a customer, an investor update) and you'll be tagged in at least one before your first coffee has cooled. A request comes in, say a customer can't log in, and there's no ticket queue and no support tier. Someone pastes a screenshot. You check the logs in Datadog or whatever the team happens to use, you find it's an expired certificate, and you fix it. Then you write it up in Notion so the next person doesn't repeat the detective work.
That's the loop. Request, diagnosis, fix, a scrappy bit of documentation. In a bigger company four people would own those steps. Here you own all of them, and the reason is simple: there aren't four people.
By mid-morning you might be in a call with the founder about a hiring plan, because nobody else has written a job spec before. By afternoon you're back in the codebase. Context-switching is the real cost of the day, and it doesn't show up on any timesheet.
Beyond Tick Boxes: Diversity Recruitment Strategies That Actually Transform UK Workplaces
Master the Virtual Hot Seat: 7 Video Interview Techniques Recruiters Don't Tell You
AI Governance Careers Surge in 2026: Why This Role Will Define the Next Decade
The week and the month
Weeks have a loose shape. Monday is planning, often a 30-minute call where priorities get reshuffled because something changed over the weekend. Thursday tends to be when the demo to the wider team happens, which is a polite word for "show what you shipped, warts included". Friday is for the jobs that fell off everyone's list: the onboarding doc nobody wrote, the staging environment that's been quietly broken for a fortnight.
Monthly rhythm comes from money. Board updates, runway conversations, a customer renewal that suddenly makes everything urgent. You'll hear the word "runway" more than you expect. It's a good idea to ask, at interview, how many months of it the company has. Most founders will tell you if you ask plainly.
What I enjoyed, and what drained me
The enjoyable part is speed. You see a problem on Tuesday and the fix is live on Wednesday, with no committee in between. I picked up skills in a few months that would have taken years in a large engineering department: writing job specs, running a first-round interview, talking to customers directly. I'd never done that last one as a developer. It changed how I wrote code.
The draining part crept up on me. Taking on one extra job is a favour. Taking on five is a role nobody hired you for and nobody is paying you for. I found I was doing recruitment coordination, a bit of DevOps and customer support on top of the engineering work I'd been hired to do, and my actual output slipped. Nobody noticed at first, which is the worrying bit.
So I set rules. I kept one protected morning a week with notifications off. I asked, every time a new task landed, what I was dropping to make room for it. That question works. Founders aren't villains; most simply haven't counted the load.
Skills it takes
You need a tolerance for ambiguity more than any particular tool. Written communication matters hugely, because small teams run on short messages and short docs. Being able to say "I don't know yet, I'll find out by Thursday" without panic is underrated. Technical depth still counts, but breadth gets you further early on.
Pay and the trade-offs
Salaries at early stage startups in the UK usually sit below what established tech firms pay, often by a noticeable margin, with equity offered to close the gap. Treat the equity as a lottery ticket rather than income. Ask about the vesting schedule and what the options are actually worth if the company is sold. Ask, too, whether there's a pay review date written down.
Routes in
Most people arrive via a network, a previous colleague, or a founder who spots them. You can browse startup and tech roles on OHUB alongside the usual boards, and video-first applications suit small teams who want to hear how you think. The Gov.uk guidance on employment contracts is worth a read before you sign anything, as startup paperwork can be thin.
Would I do it again? Probably, though with a clearer idea of where my own job ends.