Work at Byte

We need the person who makes Byte feel like it came from inside student culture, not like a company arrived to market at it.

Your first job is not reach. It is density.

You will find the forty people who shape a campus before trying to reach four thousand: the society presidents, student founders, editors, creators, athletes, organisers and people everyone else seems to know. You will build real relationships with them, then create the stories, experiences and referral loops that make Byte spread naturally through a university.

At this stage, brand, community, content, growth, partnerships and press are not separate departments. They are all different ways of answering the same question: why should someone care about Byte, and why should they tell someone else?

You will shape Byte’s voice, our London launch, the first campus playbook and the world around the product. That includes the content people share, the communities we become part of and the first Byte Chapters: small, well-curated experiences that make the brand exist in real life, not just on a feed.

You need to be able to think at the level of culture and still write the caption, make the call, host the dinner and fix the landing page.

We do not care whether your last title was Head of Marketing. We care whether you have:

• Built or grown something people genuinely chose to care about.
• Exceptional taste, and the ability to explain your judgement.
• A strong, distinctive writing voice.
• A real understanding of young people without reducing them to “Gen Z.”
• The instinct to earn attention rather than immediately buying it.
• Enough range to move from strategy to execution without waiting for a team beneath you.

You may have built a brand, community, publication, event series, social account, product or something that does not fit neatly into any of those categories. The title matters far less than the evidence.

Compensation: Equity + Competitive Salary + Benefits

Byte is not a chatbot with a student-themed system prompt.

It needs to understand someone over time, reason across messages, calendars, email, screenshots and live campus context, use tools, take real actions, coordinate with another person’s Byte and know when to be proactive and when to leave someone alone.

It also needs to do all of that without being invasive, brittle, slow or confidently wrong.

That is the work.

You will work directly with our CTO on the systems beneath the product: agent orchestration, memory, retrieval, tool use, planning, permissions, evaluation, observability and the reliability layer that turns a clever demonstration into something people trust with their actual lives.

We are hiring two engineers and expect their strengths to be complementary. One may go deeper on agent architecture, memory and evaluation. The other may be stronger across applied AI, backend systems, integrations and shipping user-facing product. Both need to be excellent software engineers with strong product judgement.

We do not screen for pedigree or an arbitrary number of years. We screen for evidence.

We want to see that you have:

• Built an AI system that did more than generate text and was used by real people.
• Dealt seriously with non-determinism, tool failures, state, permissions, latency, cost and bad model behaviour.
• Designed a real method for evaluating quality rather than relying on a few successful manual tests.
• Strong software engineering fundamentals outside of LLMs.
• The honesty and technical depth to explain where your system broke, not only where it worked.
• Enough product judgement to understand that a technically correct answer can still create a terrible experience.

A polished demo is useful. What happens after the demo is what we care about.

Compensation: Competitive Salary + Benefits

Byte is being built across 2 places. The founders think quickly, the product changes quickly, and that becomes expensive when nobody turns decisions into clarity.

Your job is to make sure what we mean, what engineering understands and what users eventually receive are the same thing.

You will sit close to the founders and engineering team. You will turn product conversations into clear briefs, keep decisions and dependencies visible, surface unanswered questions before they become a week of rework and make sure everyone understands what “done” actually means.

You will also test what gets built. Not only whether it technically works, but whether it feels like Byte.

This is junior in tenure, not in responsibility. You will not spend your days taking meeting notes or filling in somebody else’s templates. People will depend on you to bring order to fast-moving work without slowing it down.

We care less about whether you have already worked as a PM and more about whether you have shown real ownership somewhere before.

Maybe you ran a society, built a side project, launched a publication, coordinated a large event or held together a team that would otherwise have fallen apart. We want to see something where people relied on you and you made the mess understandable.

You are likely to be good at this if you:

• Write with unusual clarity.
• Notice the important question everyone else has skipped.
• Are extremely organised without becoming obsessed with process.
• Understand technology well enough to have honest conversations with engineers.
• Can hold the wider product vision while following the smallest details.
• Take responsibility without needing to be constantly managed.

Compensation: Competitive Salary + Benefits

Byte will work with student information and work with institutions that rightly ask difficult questions about privacy, security and risk.

We want the foundations done before they become a blocker.

We need someone who has taken an early-stage SaaS, ideally, a Fintech or EdTech company from we know this matters to genuinely procurement-ready. Someone who understands how universities assess vendors and who has already done the detailed work required to get through those assessments.

You will work directly with the founders and engineering team to map our data, identify gaps, establish the right controls and documentation and build a practical route through GDPR, FERPA requirements for future US deployment, SOC 2 or ISO 27001 readiness, HECVAT and university procurement.

The work may include data maps, DPIAs, data processing agreements, retention and deletion policies, access controls, subprocessor reviews, incident response, security documentation and procurement packs.

We do not need a hundred-page roadmap that leaves us with a hundred more questions.

We need someone who can tell us what is essential now, what can wait, what engineering needs to change and then help us get the work done properly.

We need to see

• At least two comparable SaaS or EdTech engagements.
• A clear explanation of what you personally delivered.
• Concrete outcomes, not simply “advised on compliance.”
• References from founders or teams you worked with.
• The ability to work practically with engineers, rather than treating compliance as a separate legal exercise.