Careers · Pagelove

R-001	Developer Community Lead	Marketing	Benji	Full-time	Closed	Global	$80,000 – $130,000	developer-community-lead	Own the developer community, create the technical content that earns credibility, and build the systems that help new users succeed.	## About Pagelove Pagelove is web infrastructure for the AI era. We’ve built a DOM-aware server that lets you read and write directly to HTML documents using CSS selectors as HTTP range units. The result: a single HTML file that works as a complete, persistent web application. No database, no API layer, no backend code. Think of us as the next Vercel or Cloudflare. AI tools and developers build on our platform, and we host and serve their apps at scale. We’re seed-stage, well-funded, and working with enterprise design partners including Crew Clothing. Our founding team built and scaled infrastructure at Joyent (Node.js), Google, Equinix, Spotify, and Monzo. We’re a small, flat team. That means your work will have outsized impact from day one. ## Who we are / What we look for in everyone we hire * Get shit done. That doesn’t mean you shout or steamroll people. It means you know what it takes to deliver. You lead and influence, you make trade-offs, and you focus on outcomes. We’re a high-trust organisation. We won’t check your homework unless you ask us to. * Player/coach. We’re a startup. You’re not above anything. No job is too big or too small. We want someone as comfortable setting up a US subsidiary as they are booking a meeting room. * Have an opinion. We’re small and flat. We don’t want people checking with their manager before they speak up. We want your point of view, your challenge, your ideas. Even when they’re uncomfortable. * Breadth of experience. We want people who seek out new challenges and have done so throughout their career. We don’t care which university you went to. We care about what you’ve done and why you did it. * Change makers. You’re not happy with the status quo and you don't believe in the inherent truth of "best practice". You ask why, you give feedback, and if you can, you make the change happen. ## Why this role Pagelove's go-to-market starts with community. Developers validate the product, builders create the first templates, and early adopters generate the social proof that makes enterprises take notice. We need someone who lives in that world and can be our voice within it. This role is the customer-facing heartbeat of Pagelove. You'll own the community, create the content that earns technical credibility, and build the foundations for a world-class user experience. You won't be doing brand strategy or enterprise campaigns. Your job is to make people love building on Pagelove and to make sure they succeed when they do. You'll work hand in hand with the VP Marketing and closely with the founders and engineering team. ## Community - Grow an engaged community of developers and early adopters who believe in what we're building. Discord is the hub, but you'll show up wherever our users are: GitHub, Reddit, Hacker News, X, indie hacker forums. - Be our voice on X, Reddit, Hacker News, and Discord, engaging directly with developers and builders in the places they already spend time. - Run weekly Show & Tell sessions, office hours with the engineering team, and monthly build challenges. Make the community a place people want to come back to. - Nurture relationships with influential builders, open-source contributors, and educators. Build an evangelist programme that gives your best advocates early access and a direct line to the team. - Organise hackathons, partner showcases, and meetups that bring users together around shared curiosity. ## Technical content - Write and commission content that technical people actually want to read: tutorials, deep-dives, architecture comparisons, and build logs. No fluff, no marketing speak. - Collaborate with product and engineering to translate what we're building into clear, compelling narratives for a technical audience. - Own the template gallery as an onboarding funnel. Curate, commission, and promote the starter templates that get new users building within minutes. ## Growth and adoption - Drive the grassroots growth that feeds the funnel. That means making the template flywheel spin (more templates, more discovery, more builders), optimising the preview-to-paid conversion path, and finding creative ways to get Pagelove in front of the right people. - Experiment constantly. Test what content drives signups, which community channels convert, and where the highest-quality users come from. Share what you learn with the VP Marketing so the growth strategy stays grounded in reality. - Track and report on community health metrics: active users, template submissions, engagement, retention, and referral patterns. You're the person who knows whether the community is actually growing or just getting noisier. ## Customer success and support - Build the foundations for a world-class user experience, from first contact through to active use. Create onboarding flows, documentation, and learning resources that help new users succeed fast. - Be the first line of feedback from the field, translating user pain points into product opportunities. You're the voice of the user inside the company. - Establish the systems and rhythms for scalable support: forums, issue tracking, feedback loops. Champion clarity and transparency in every interaction. ## What we're looking for - You're a developer or a technical builder. Not someone who can 'talk to developers' but someone who is one. You write code, you ship side projects, you have opinions about frameworks and architecture. That's non-negotiable. - You already have a presence in the developer community. People know your name from your blog, your tweets, your open-source contributions, your conference talks, or your YouTube channel. We'll look at your profile before we look at your CV. - You've built or grown a community before. You know the difference between a community that looks active and one that actually is. - You're a strong writer. Tutorials, docs, blog posts, tweets. You know that developer audiences can spot filler from a mile away. - You think about growth from the ground up. You've seen what drives organic adoption in developer communities and you know the difference between vanity metrics and real traction. - You're excited about AI-native development. You understand how tools like Claude, Cursor, and Bolt are changing who builds software. - You're energised by early-stage environments. You like building from first principles, not managing playbooks. - You want to help build a company with a culture you're proud to tell others about. ## Location Flexible. We're a distributed team (London, SW England, Vancouver) and work remotely most of the time. We get together regularly in person because we think it matters. ## Employment type Permanent, full-time. ## What we offer - Salary range: $80,000 – $130,000 - Share options - Founding team-level influence on product and community direction - The chance to build the community for a new category of web infrastructure ## Reporting to Benji Portwin, CPO
R-002	Chief of Staff	Operations	James	Full-time	Open	Global	chief-of-staff	Our first ops hire, working directly with the founders across every part of the business. You'll own special projects, keep the wheels turning, and build the operational foundations of a company that's scaling fast. No task too big, no task too small.	£70,000	## About Pagelove Pagelove is web infrastructure for the AI era. We’ve built a DOM-aware server that lets you read and write directly to HTML documents using CSS selectors as HTTP range units. The result: a single HTML file that works as a complete, persistent web application. No database, no API layer, no backend code. Think of us as the next Vercel or Cloudflare. AI tools and developers build on our platform, and we host and serve their apps at scale. We’re seed-stage, well-funded, and looking to grow our customer base. Our founding team built and scaled infrastructure at Joyent (Node.js), Google, Equinix, Spotify, and Monzo. We’re a small, flat team. That means your work will have outsized impact from day one. ## Who we are / What we look for in everyone we hire - Get shit done. That doesn’t mean you shout or steamroll people. It means you know what it takes to deliver. You lead and influence, you make trade-offs, and you focus on outcomes. We’re a high-trust organisation. We won’t check your homework unless you ask us to. - Player/coach. We’re a startup. You’re not above anything. No job is too big or too small. We want someone as comfortable setting up a US subsidiary as they are booking a meeting room. - Have an opinion. We’re small and flat. We don’t want people checking with their manager before they speak up. We want your point of view, your challenge, your ideas. Even when they’re uncomfortable. - Breadth of experience. We want people who seek out new challenges and have done so throughout their career. We don’t care which university you went to. We care about what you’ve done and why you did it. - Change makers. You’re not happy with the status quo and you don't believe in the inherent truth of "best practice". You ask why, you give feedback, and if you can, you make the change happen. ## Why this role We’ve closed our seed round and are scaling from beta to paying customers, building the operational foundations of a company that’s going to grow fast. We need someone who can operate across the full range of what a seed-stage company demands: booking flights for an away day one hour, setting up a US subsidiary the next, and jumping into a product delivery conversation after lunch. The range is the point. You’ll be trusted with high-stakes projects like working with lawyers to get contracts in place, and you’ll also be the person who makes sure the founders’ calendars aren’t a mess. No task is too big or too small. The right person sees that as a feature, not a compromise. This role is the path to Chief of Staff. As the company grows, so does the scope. You’ll report directly to the CEO and work hand in hand with all three founders. ## This role - Special projects. You’ll own and deliver projects that don’t fit neatly into anyone else’s remit. Setting up a US entity. Evaluating and onboarding vendors. Scoping a new market entry. Researching compliance requirements for a new jurisdiction. These are the high-leverage projects that accelerate the company when they get done and hold it back when they don’t. - Founder support. You’ll help manage founder calendars, organise team away days (hotels, flights, venues), coordinate travel, and handle the day-to-day logistics that keep the founders focused on the work that matters most. Tasks of all shapes will fly your way and you’ll catch them. - Delivery and cross-functional support. You’ll work across product, engineering, and marketing to aid delivery and keep things moving. You’ll be the go-to person when something needs coordinating, chasing, or unblocking across the team. - Internal tooling. You’ll build and iterate internal tools using Pagelove’s own technology. Our team kanban, internal dashboards, and operational workflows all run on our platform. You’ll own these and improve them as the team’s needs evolve. - Legal and compliance coordination. You’ll be the operational point of contact for our lawyers, insurers, and advisors. You’ll drive legal workstreams to completion: IP assignments, service agreements, sponsor licence applications, and compliance documentation. - Fundraising operations. You’ll run the operational side of fundraising: data room management, investor updates, due diligence coordination, and cap table maintenance. You’ll sit in on investor conversations and understand how venture capital works from the inside. - Hiring operations. You’ll build and manage our hiring pipelines: job postings, candidate coordination, interview scheduling, and keeping our ATS in shape. As the team grows, you’ll help design the processes that make hiring feel effortless. - Finance and admin. You’ll liaise with our accountants, handle HMRC submissions, Companies House filings, and supplier management. You’ll keep the financial and administrative house in order so the founders don’t have to. ## What we're looking for - Experience across multiple roles in startups or high-growth environments. You’ve worn different hats and that’s what you’re good at. - You’ve owned and delivered operational projects in a product-led organisation. You know the difference between perfect and good enough, and you know when each one matters. - Exceptional organisational skills and follow-through. You close loops without being asked. - Strong written communication. You’ll draft emails to lawyers, investors, and partners on behalf of the founders. Your writing needs to be clear, professional, and warm. - Familiarity with startup mechanics: fundraising, cap tables, option schemes, company admin. You don’t need to be an expert, but you should know what these things are. - Happy to flex your working hours to bridge time zones. We have team members in Vancouver, so if you’re UK-based that means working until 7pm one or two evenings a week. ## Location Flexible. We’re a distributed team (London, SW England, Vancouver) and work remotely most of the time. We get together regularly in person because we think it matters. ## Employment type Permanent, full-time. ## What we offer - Salary: £70,000 - Share options (EMI scheme) - Private healthcare - Pension - Direct access to experienced founders who will invest in your development - The chance to help build a company from the ground up ## Reporting to James Duncan, Co-Founder & CEO
R-003	Founding Software Engineer	Engineering	Sam Johnston	Full-time	Open	Remote	founding-software-engineer		$110,000-$130,000	## About Pagelove Pagelove is web infrastructure for the AI era. We’ve built a DOM-aware server that works at the intersection of HTTP and HTML to let you read and write directly to HTML documents using CSS selectors as HTTP range units. The result: a single HTML file that works as a complete, persistent web application. No database, no API layer, no backend code. Think of us as the next web development and delivery network. AI tools and developers build on our platform, and we host and serve their apps at scale. We’re seed-stage, well-funded, and working with enterprise design partners. Our founding team built and scaled infrastructure at Joyent (Node.js), Google, Equinix, Spotify, and Monzo. We’re a small, flat team. That means your work will have an outsized impact from day one. ## Who we are / What we look for in everyone we hire * Get shit done. That doesn’t mean you shout or steamroll people. It means you know what it takes to deliver. You lead and influence, you make trade-offs, and you focus on outcomes. We’re a high-trust organisation. We won’t check your homework unless you ask us to. * Player/coach. We’re a startup. You’re senior, but you get your hands dirty. No job is too big or too small. We want someone as comfortable presenting at a conference as they are writing the email copy that gets people there. * Have an opinion. We’re small and flat. We don’t want people checking with their manager before they speak up. We want your point of view, your challenge, your ideas. Even when they’re uncomfortable. * Breadth of experience. We want people who seek out new challenges and have done so throughout their career. We don’t care which university you went to. We care about what you’ve done and why you did it. * Change makers. You’re not happy with the status quo and you don’t believe in “best practice.” You ask why, you give feedback, and if you can, you make the change happen. ## Why this role You will be Pagelove’s first non-founder engineer. Everything so far has been built by the founders: our CEO developed the core codebase, while our CTO built the infrastructure around it. We’re using cloud computing today (Azure & AWS) with a view to having our own hardware deployments in datacenters when economics and operational requirements justify it. While production cloud experience is important, expertise in bare metal and network infrastructure is useful but not required. It’s a small team, and an ambitious product. You'd be the first person to work on it who didn't invent it, and it will have rough edges that you’ll need to sand down. The first deliverable will be to work with the founders to develop independent command of the codebase: take on its ownership, its history, the decisions behind it, and to collaborate with them on the future direction. Many of the important design decisions are already made. We scale by using HTTP the way it was meant to be used: layering, caching and proxying, to enable HTML to become the application state rather than something a client just renders at the end. Those are deliberate constraints on the architecture, which makes the work about building well inside them and discovering new ways to exploit them for even more than we currently get. Deep knowledge of HTTP at the protocol level and HTML down to details of the DOM are advantageous. We’re looking for someone who understands why those constraints exist, preserves the leverage they create, and ensures that any change to them is deliberate, evidenced and reflected across the implementation and specifications. You’ll report to our CTO and work across the whole platform, including its design, development, and delivery. Our development loop already runs on agents (primarily under Anthropic’s Claude Code and OpenAI’s ChatGPT/Codex). When they hit something they shouldn't decide alone, they ask, and the answer gets ratified and recorded. The engine that drives it is a Pagelove application that provides a unified interface to both agents and humans. No bespoke integration layer, because the architecture made that free. It's early, the pipeline is thin in places, and the questions about how far agentic AI goes are live across the industry. You'll have substantial influence over how we answer them and lead the day-to-day evolution of our agentic engineering process. As the founding engineer, you also set the standard for what comes next — how we review, how we test, how we improve, and what we expect of the engineers who join after you, above or below you (“Founding” describes when you are joining and the influence you will have; it’s not an executive title or a promise that the organisation will never grow around you.) This is a rare opportunity to set the direction for the future of the Internet, and revisit decisions made before humans and machines were both actively creating and consuming content. ## This role * Architecture stewardship. You’ll guard the things that make the system work: element-granular storage, pure-HTTP boundaries between tiers, one-parse-one-serialize request pipelines, HTML-with-microdata as the data plane, and specs that always match the implementation. You’ll work with the founders to evolve the direction as we scale and learn. * Keeping the contracts true. Our protocol, API, and storage-grammar guides, along with the user and operator docs, are relied upon heavily by both agents and humans. Changes to the API or storage grammar don’t ship without them, in the same PR as the change; if it’s not in the repo, it effectively doesn’t exist. This is paramount to prevent drift with AI agents who start up with a clean slate. * Directing an agentic engineering process. You’ll curate the issue backlog as the agents’ work queue, write designs and acceptance criteria precise enough for an agent to implement unattended, and review higher-risk or longer-lived agent PRs with the skepticism you’d apply to a talented but overconfident junior. When the process itself fails, you’ll evolve the standing instructions, loop prompts, review rubrics, and repo conventions that steer it. You’ll inherit a system that works and make it measurably better. * Quality and test discipline. Test-driven development is house policy here, enforced by automated review: failing test first, hurl tests for every feature, with fuzzing and nightly benchmarks watching the rest. We have thousands of tests, and can’t afford to have humans blocking progress with agents waiting on them. You’ll own that bar and raise it so that issues are identified before they impact production. * Ship and operate. You’ll initially be responsible for continuous integration health, the release path, benchmarks and regression tracking, and the operational story \- deployment, monitoring, and the management console’s host lifecycle. While future hires may be more reliability focused, you’ll own it until you share it with them. * The hard ten percent. Some problems are too subtle, too novel, or too important to delegate, and you’ll take those on personally: distributed-systems correctness on a transactional key-value store (transactions, versionstamps, conflict ranges), CRDT merge semantics, cache coherence and ETag correctness across three tiers, pub/sub invalidation, and the performance profile of the arena and parser hot path. ## What we’re looking for * Deep systems programming experience in production. You’ve worked close to the metal in a large, long-lived codebase: memory management, concurrency, async services, careful error handling, and real performance work \- allocators, arenas, profiling. Rust, C, C++, Zig, Go \- we care that you’ve built and maintained systems at this level, not which language you did it in. Our codebase is Rust, so you’ll either be fluent already or confident you can get there quickly. * Distributed-systems and storage grounding. You’ve worked with transactional key-value stores (FoundationDB is a significant plus), and you understand consistency models and conflict handling. CRDTs or operational transforms ideally. * Fluency in HTTP as a system, not just a transport: caching semantics, ETags and conditional requests, content negotiation, WebDAV, SSE. You should find “off-the-shelf proxies can cache between any two tiers” a design goal worth defending. * Hands-on experience developing with AI coding agents. Not autocomplete — agentic workflows. You’ve written specs and prompts that agents execute against, reviewed machine-authored PRs at volume, and built feedback loops (automated review, evals, CI gates) that keep quality high without reading every line yourself. You have opinions, from experience, about where agents excel and where they quietly fail. * Editorial judgment and strong technical writing. Designs, issue comments, review verdicts, and specs are the primary way you’ll steer both the agents and the codebase. You know when to pull people into a conversation and how to guide them through making a good decision. * The temperament for high autonomy. You can run a platform’s entire engineering process yourself, decide what matters, and be trusted with the keys. * Bonus points for parser or DOM internals (html5ever-class parsing, arena-based trees, CSS selector engines), language implementation experience, WASM/JS bindings, FUSE or filesystem protocols, OIDC/auth flows, or experience designing multi-agent systems and LLM evaluation harnesses. ## What good looks like at six months * You’re regularly making and owning architectural decisions. * Agent throughput is up, and the eval loop catches more before it reaches you. * The system has met and exceeded reliability objectives despite frequent pushes. * Specs and implementation have not drifted. * At least one of the hard ten percent problems is closed and documented.

R-001

Developer Community Lead

Marketing

Benji

Full-time

Closed

## About Pagelove Pagelove is web infrastructure for the AI era. We’ve built a DOM-aware server that lets you read and write directly to HTML documents using CSS selectors as HTTP range units. The result: a single HTML file that works as a complete, persistent web application. No database, no API layer, no backend code. Think of us as the next Vercel or Cloudflare. AI tools and developers build on our platform, and we host and serve their apps at scale. We’re seed-stage, well-funded, and working with enterprise design partners including Crew Clothing. Our founding team built and scaled infrastructure at Joyent (Node.js), Google, Equinix, Spotify, and Monzo. We’re a small, flat team. That means your work will have outsized impact from day one. ## Who we are / What we look for in everyone we hire * Get shit done. That doesn’t mean you shout or steamroll people. It means you know what it takes to deliver. You lead and influence, you make trade-offs, and you focus on outcomes. We’re a high-trust organisation. We won’t check your homework unless you ask us to. * Player/coach. We’re a startup. You’re not above anything. No job is too big or too small. We want someone as comfortable setting up a US subsidiary as they are booking a meeting room. * Have an opinion. We’re small and flat. We don’t want people checking with their manager before they speak up. We want your point of view, your challenge, your ideas. Even when they’re uncomfortable. * Breadth of experience. We want people who seek out new challenges and have done so throughout their career. We don’t care which university you went to. We care about what you’ve done and why you did it. * Change makers. You’re not happy with the status quo and you don't believe in the inherent truth of "best practice". You ask why, you give feedback, and if you can, you make the change happen. ## Why this role Pagelove's go-to-market starts with community. Developers validate the product, builders create the first templates, and early adopters generate the social proof that makes enterprises take notice. We need someone who lives in that world and can be our voice within it. This role is the customer-facing heartbeat of Pagelove. You'll own the community, create the content that earns technical credibility, and build the foundations for a world-class user experience. You won't be doing brand strategy or enterprise campaigns. Your job is to make people love building on Pagelove and to make sure they succeed when they do. You'll work hand in hand with the VP Marketing and closely with the founders and engineering team. ## Community - Grow an engaged community of developers and early adopters who believe in what we're building. Discord is the hub, but you'll show up wherever our users are: GitHub, Reddit, Hacker News, X, indie hacker forums. - Be our voice on X, Reddit, Hacker News, and Discord, engaging directly with developers and builders in the places they already spend time. - Run weekly Show & Tell sessions, office hours with the engineering team, and monthly build challenges. Make the community a place people want to come back to. - Nurture relationships with influential builders, open-source contributors, and educators. Build an evangelist programme that gives your best advocates early access and a direct line to the team. - Organise hackathons, partner showcases, and meetups that bring users together around shared curiosity. ## Technical content - Write and commission content that technical people actually want to read: tutorials, deep-dives, architecture comparisons, and build logs. No fluff, no marketing speak. - Collaborate with product and engineering to translate what we're building into clear, compelling narratives for a technical audience. - Own the template gallery as an onboarding funnel. Curate, commission, and promote the starter templates that get new users building within minutes. ## Growth and adoption - Drive the grassroots growth that feeds the funnel. That means making the template flywheel spin (more templates, more discovery, more builders), optimising the preview-to-paid conversion path, and finding creative ways to get Pagelove in front of the right people. - Experiment constantly. Test what content drives signups, which community channels convert, and where the highest-quality users come from. Share what you learn with the VP Marketing so the growth strategy stays grounded in reality. - Track and report on community health metrics: active users, template submissions, engagement, retention, and referral patterns. You're the person who knows whether the community is actually growing or just getting noisier. ## Customer success and support - Build the foundations for a world-class user experience, from first contact through to active use. Create onboarding flows, documentation, and learning resources that help new users succeed fast. - Be the first line of feedback from the field, translating user pain points into product opportunities. You're the voice of the user inside the company. - Establish the systems and rhythms for scalable support: forums, issue tracking, feedback loops. Champion clarity and transparency in every interaction. ## What we're looking for - You're a developer or a technical builder. Not someone who can 'talk to developers' but someone who is one. You write code, you ship side projects, you have opinions about frameworks and architecture. That's non-negotiable. - You already have a presence in the developer community. People know your name from your blog, your tweets, your open-source contributions, your conference talks, or your YouTube channel. We'll look at your profile before we look at your CV. - You've built or grown a community before. You know the difference between a community that looks active and one that actually is. - You're a strong writer. Tutorials, docs, blog posts, tweets. You know that developer audiences can spot filler from a mile away. - You think about growth from the ground up. You've seen what drives organic adoption in developer communities and you know the difference between vanity metrics and real traction. - You're excited about AI-native development. You understand how tools like Claude, Cursor, and Bolt are changing who builds software. - You're energised by early-stage environments. You like building from first principles, not managing playbooks. - You want to help build a company with a culture you're proud to tell others about. ## Location Flexible. We're a distributed team (London, SW England, Vancouver) and work remotely most of the time. We get together regularly in person because we think it matters. ## Employment type Permanent, full-time. ## What we offer - Salary range: $80,000 – $130,000 - Share options - Founding team-level influence on product and community direction - The chance to build the community for a new category of web infrastructure ## Reporting to Benji Portwin, CPO

R-002

Chief of Staff

Operations

James

Full-time

Open

## About Pagelove Pagelove is web infrastructure for the AI era. We’ve built a DOM-aware server that lets you read and write directly to HTML documents using CSS selectors as HTTP range units. The result: a single HTML file that works as a complete, persistent web application. No database, no API layer, no backend code. Think of us as the next Vercel or Cloudflare. AI tools and developers build on our platform, and we host and serve their apps at scale. We’re seed-stage, well-funded, and looking to grow our customer base. Our founding team built and scaled infrastructure at Joyent (Node.js), Google, Equinix, Spotify, and Monzo. We’re a small, flat team. That means your work will have outsized impact from day one. ## Who we are / What we look for in everyone we hire - Get shit done. That doesn’t mean you shout or steamroll people. It means you know what it takes to deliver. You lead and influence, you make trade-offs, and you focus on outcomes. We’re a high-trust organisation. We won’t check your homework unless you ask us to. - Player/coach. We’re a startup. You’re not above anything. No job is too big or too small. We want someone as comfortable setting up a US subsidiary as they are booking a meeting room. - Have an opinion. We’re small and flat. We don’t want people checking with their manager before they speak up. We want your point of view, your challenge, your ideas. Even when they’re uncomfortable. - Breadth of experience. We want people who seek out new challenges and have done so throughout their career. We don’t care which university you went to. We care about what you’ve done and why you did it. - Change makers. You’re not happy with the status quo and you don't believe in the inherent truth of "best practice". You ask why, you give feedback, and if you can, you make the change happen. ## Why this role We’ve closed our seed round and are scaling from beta to paying customers, building the operational foundations of a company that’s going to grow fast. We need someone who can operate across the full range of what a seed-stage company demands: booking flights for an away day one hour, setting up a US subsidiary the next, and jumping into a product delivery conversation after lunch. The range is the point. You’ll be trusted with high-stakes projects like working with lawyers to get contracts in place, and you’ll also be the person who makes sure the founders’ calendars aren’t a mess. No task is too big or too small. The right person sees that as a feature, not a compromise. This role is the path to Chief of Staff. As the company grows, so does the scope. You’ll report directly to the CEO and work hand in hand with all three founders. ## This role - Special projects. You’ll own and deliver projects that don’t fit neatly into anyone else’s remit. Setting up a US entity. Evaluating and onboarding vendors. Scoping a new market entry. Researching compliance requirements for a new jurisdiction. These are the high-leverage projects that accelerate the company when they get done and hold it back when they don’t. - Founder support. You’ll help manage founder calendars, organise team away days (hotels, flights, venues), coordinate travel, and handle the day-to-day logistics that keep the founders focused on the work that matters most. Tasks of all shapes will fly your way and you’ll catch them. - Delivery and cross-functional support. You’ll work across product, engineering, and marketing to aid delivery and keep things moving. You’ll be the go-to person when something needs coordinating, chasing, or unblocking across the team. - Internal tooling. You’ll build and iterate internal tools using Pagelove’s own technology. Our team kanban, internal dashboards, and operational workflows all run on our platform. You’ll own these and improve them as the team’s needs evolve. - Legal and compliance coordination. You’ll be the operational point of contact for our lawyers, insurers, and advisors. You’ll drive legal workstreams to completion: IP assignments, service agreements, sponsor licence applications, and compliance documentation. - Fundraising operations. You’ll run the operational side of fundraising: data room management, investor updates, due diligence coordination, and cap table maintenance. You’ll sit in on investor conversations and understand how venture capital works from the inside. - Hiring operations. You’ll build and manage our hiring pipelines: job postings, candidate coordination, interview scheduling, and keeping our ATS in shape. As the team grows, you’ll help design the processes that make hiring feel effortless. - Finance and admin. You’ll liaise with our accountants, handle HMRC submissions, Companies House filings, and supplier management. You’ll keep the financial and administrative house in order so the founders don’t have to. ## What we're looking for - Experience across multiple roles in startups or high-growth environments. You’ve worn different hats and that’s what you’re good at. - You’ve owned and delivered operational projects in a product-led organisation. You know the difference between perfect and good enough, and you know when each one matters. - Exceptional organisational skills and follow-through. You close loops without being asked. - Strong written communication. You’ll draft emails to lawyers, investors, and partners on behalf of the founders. Your writing needs to be clear, professional, and warm. - Familiarity with startup mechanics: fundraising, cap tables, option schemes, company admin. You don’t need to be an expert, but you should know what these things are. - Happy to flex your working hours to bridge time zones. We have team members in Vancouver, so if you’re UK-based that means working until 7pm one or two evenings a week. ## Location Flexible. We’re a distributed team (London, SW England, Vancouver) and work remotely most of the time. We get together regularly in person because we think it matters. ## Employment type Permanent, full-time. ## What we offer - Salary: £70,000 - Share options (EMI scheme) - Private healthcare - Pension - Direct access to experienced founders who will invest in your development - The chance to help build a company from the ground up ## Reporting to James Duncan, Co-Founder & CEO

R-003

Founding Software Engineer

Engineering

Sam Johnston

Full-time

Open

## About Pagelove Pagelove is web infrastructure for the AI era. We’ve built a DOM-aware server that works at the intersection of HTTP and HTML to let you read and write directly to HTML documents using CSS selectors as HTTP range units. The result: a single HTML file that works as a complete, persistent web application. No database, no API layer, no backend code. Think of us as the next web development and delivery network. AI tools and developers build on our platform, and we host and serve their apps at scale. We’re seed-stage, well-funded, and working with enterprise design partners. Our founding team built and scaled infrastructure at Joyent (Node.js), Google, Equinix, Spotify, and Monzo. We’re a small, flat team. That means your work will have an outsized impact from day one. ## Who we are / What we look for in everyone we hire * Get shit done. That doesn’t mean you shout or steamroll people. It means you know what it takes to deliver. You lead and influence, you make trade-offs, and you focus on outcomes. We’re a high-trust organisation. We won’t check your homework unless you ask us to. * Player/coach. We’re a startup. You’re senior, but you get your hands dirty. No job is too big or too small. We want someone as comfortable presenting at a conference as they are writing the email copy that gets people there. * Have an opinion. We’re small and flat. We don’t want people checking with their manager before they speak up. We want your point of view, your challenge, your ideas. Even when they’re uncomfortable. * Breadth of experience. We want people who seek out new challenges and have done so throughout their career. We don’t care which university you went to. We care about what you’ve done and why you did it. * Change makers. You’re not happy with the status quo and you don’t believe in “best practice.” You ask why, you give feedback, and if you can, you make the change happen. ## Why this role You will be Pagelove’s first non-founder engineer. Everything so far has been built by the founders: our CEO developed the core codebase, while our CTO built the infrastructure around it. We’re using cloud computing today (Azure & AWS) with a view to having our own hardware deployments in datacenters when economics and operational requirements justify it. While production cloud experience is important, expertise in bare metal and network infrastructure is useful but not required. It’s a small team, and an ambitious product. You'd be the first person to work on it who didn't invent it, and it will have rough edges that you’ll need to sand down. The first deliverable will be to work with the founders to develop independent command of the codebase: take on its ownership, its history, the decisions behind it, and to collaborate with them on the future direction. Many of the important design decisions are already made. We scale by using HTTP the way it was meant to be used: layering, caching and proxying, to enable HTML to become the application state rather than something a client just renders at the end. Those are deliberate constraints on the architecture, which makes the work about building well inside them and discovering new ways to exploit them for even more than we currently get. Deep knowledge of HTTP at the protocol level and HTML down to details of the DOM are advantageous. We’re looking for someone who understands why those constraints exist, preserves the leverage they create, and ensures that any change to them is deliberate, evidenced and reflected across the implementation and specifications. You’ll report to our CTO and work across the whole platform, including its design, development, and delivery. Our development loop already runs on agents (primarily under Anthropic’s Claude Code and OpenAI’s ChatGPT/Codex). When they hit something they shouldn't decide alone, they ask, and the answer gets ratified and recorded. The engine that drives it is a Pagelove application that provides a unified interface to both agents and humans. No bespoke integration layer, because the architecture made that free. It's early, the pipeline is thin in places, and the questions about how far agentic AI goes are live across the industry. You'll have substantial influence over how we answer them and lead the day-to-day evolution of our agentic engineering process. As the founding engineer, you also set the standard for what comes next — how we review, how we test, how we improve, and what we expect of the engineers who join after you, above or below you (“Founding” describes when you are joining and the influence you will have; it’s not an executive title or a promise that the organisation will never grow around you.) This is a rare opportunity to set the direction for the future of the Internet, and revisit decisions made before humans and machines were both actively creating and consuming content. ## This role * Architecture stewardship. You’ll guard the things that make the system work: element-granular storage, pure-HTTP boundaries between tiers, one-parse-one-serialize request pipelines, HTML-with-microdata as the data plane, and specs that always match the implementation. You’ll work with the founders to evolve the direction as we scale and learn. * Keeping the contracts true. Our protocol, API, and storage-grammar guides, along with the user and operator docs, are relied upon heavily by both agents and humans. Changes to the API or storage grammar don’t ship without them, in the same PR as the change; if it’s not in the repo, it effectively doesn’t exist. This is paramount to prevent drift with AI agents who start up with a clean slate. * Directing an agentic engineering process. You’ll curate the issue backlog as the agents’ work queue, write designs and acceptance criteria precise enough for an agent to implement unattended, and review higher-risk or longer-lived agent PRs with the skepticism you’d apply to a talented but overconfident junior. When the process itself fails, you’ll evolve the standing instructions, loop prompts, review rubrics, and repo conventions that steer it. You’ll inherit a system that works and make it measurably better. * Quality and test discipline. Test-driven development is house policy here, enforced by automated review: failing test first, hurl tests for every feature, with fuzzing and nightly benchmarks watching the rest. We have thousands of tests, and can’t afford to have humans blocking progress with agents waiting on them. You’ll own that bar and raise it so that issues are identified before they impact production. * Ship and operate. You’ll initially be responsible for continuous integration health, the release path, benchmarks and regression tracking, and the operational story \- deployment, monitoring, and the management console’s host lifecycle. While future hires may be more reliability focused, you’ll own it until you share it with them. * The hard ten percent. Some problems are too subtle, too novel, or too important to delegate, and you’ll take those on personally: distributed-systems correctness on a transactional key-value store (transactions, versionstamps, conflict ranges), CRDT merge semantics, cache coherence and ETag correctness across three tiers, pub/sub invalidation, and the performance profile of the arena and parser hot path. ## What we’re looking for * Deep systems programming experience in production. You’ve worked close to the metal in a large, long-lived codebase: memory management, concurrency, async services, careful error handling, and real performance work \- allocators, arenas, profiling. Rust, C, C++, Zig, Go \- we care that you’ve built and maintained systems at this level, not which language you did it in. Our codebase is Rust, so you’ll either be fluent already or confident you can get there quickly. * Distributed-systems and storage grounding. You’ve worked with transactional key-value stores (FoundationDB is a significant plus), and you understand consistency models and conflict handling. CRDTs or operational transforms ideally. * Fluency in HTTP as a system, not just a transport: caching semantics, ETags and conditional requests, content negotiation, WebDAV, SSE. You should find “off-the-shelf proxies can cache between any two tiers” a design goal worth defending. * Hands-on experience developing with AI coding agents. Not autocomplete — agentic workflows. You’ve written specs and prompts that agents execute against, reviewed machine-authored PRs at volume, and built feedback loops (automated review, evals, CI gates) that keep quality high without reading every line yourself. You have opinions, from experience, about where agents excel and where they quietly fail. * Editorial judgment and strong technical writing. Designs, issue comments, review verdicts, and specs are the primary way you’ll steer both the agents and the codebase. You know when to pull people into a conversation and how to guide them through making a good decision. * The temperament for high autonomy. You can run a platform’s entire engineering process yourself, decide what matters, and be trusted with the keys. * Bonus points for parser or DOM internals (html5ever-class parsing, arena-based trees, CSS selector engines), language implementation experience, WASM/JS bindings, FUSE or filesystem protocols, OIDC/auth flows, or experience designing multi-agent systems and LLM evaluation harnesses. ## What good looks like at six months * You’re regularly making and owning architectural decisions. * Agent throughput is up, and the eval loop catches more before it reaches you. * The system has met and exceeded reliability objectives despite frequent pushes. * Specs and implementation have not drifted. * At least one of the hard ten percent problems is closed and documented.

Loading role…