We are small, and we hire slowly on purpose.
Everything the Forum publishes carries our name on it, so every person who joins changes what we are able to stand behind. Three roles are open. If none of them is you but you think we are missing something, write anyway and say what.
Small team, published work, your name on it
Nothing here is ghost-written for someone more senior.
San Francisco · Chennai
Three things worth knowing before you apply
We would rather you self-select out now than find this out in month two.
The work is published
What you produce goes out under the Forum's name with a date on it, and people argue with it in public. That is the job, not a side effect of it.
Small means broad
Nobody here does one narrow thing. You will own work end to end, and you will do parts of it that are not in your title.
We check things
The whole institution rests on being careful. If a number cannot be traced to its source, we do not print it, and that standard applies to everyone's work.
Three roles, two cities
Click a role to read the full description. Everything we can tell you is in there, including what the work actually involves on a normal day.
You will be the person who finds out whether a claim is true. A vendor says a named enterprise is running its product. You take that claim apart, write to the organization named in it, and record what came back. Much of what we publish begins at your desk, and the determinations carry the Forum's name because you did the work properly.
What you will do
- Capture vendor customer claims from published material and structure them for the register
- Write to the enterprises named in those claims and run the correspondence through to an answer
- Record determinations accurately, including the unanswered ones and the ones that did not hold up
- Build the category and industry views that sit on top of the register, with every number traceable
- Draft sections of our published editions and defend what you wrote when someone disagrees
What we are looking for
- Two to five years in research, analysis, journalism, consulting or an equivalent evidence-heavy role
- Genuinely careful with detail. The job is mostly about not getting things slightly wrong
- Writes clean English and can explain a finding to someone who did not do the research
- Comfortable writing to senior people at large enterprises and following up without being a nuisance
- Interested in enterprise software and AI adoption. You do not need to be technical
Useful, not required
- Experience inside a large enterprise, so you know how these decisions actually get made
- A working knowledge of SQL or spreadsheets good enough to interrogate a dataset yourself
We run workshops, events and briefings, and almost none of it is captured well. This role fixes that. You will turn rooms full of senior people into things worth watching, and turn our published research into video that does not look like every other B2B channel.
What you will do
- Edit long-form session recordings into clean, watchable pieces and short cuts for social
- Cut explainer and research videos from our published editions, with motion graphics where they help
- Hold the visual standard across everything we put out, working to our brand and typeface
- Handle the practical end too: audio clean-up, subtitles, versioning, delivery formats
- Shoot on location at events in Chennai and occasionally elsewhere
What we are looking for
- Two to four years editing professionally, with a reel we can watch
- Strong on Premiere Pro or Final Cut, and comfortable in After Effects for titles and simple motion
- A real eye for typography and pacing. Our material is restrained and the video has to match
- Can take a two-hour recording and find the fifteen minutes that matter
- Reliable with deadlines, because events do not move
Useful, not required
- Comfortable on a camera and with location audio
- Some design or thumbnail work beyond the edit itself
The register is the Forum's core product and it needs to be properly built. You will own the platform that holds every record, every determination and every published view, and the public surfaces that people reach them through. Small team, so you will touch the whole stack.
What you will do
- Build and maintain the register platform and the public index, front end and back end
- Work in React and TypeScript on the front, with Node and Postgres behind it
- Design the data model carefully. Records carry dates, versions and lapse rules, and getting that wrong is expensive
- Build the internal tools the research team uses every day, and make them fast
- Own deployment, performance and uptime. There is nobody else to hand it to
What we are looking for
- Three to six years building production web applications end to end
- Strong React and TypeScript. You have shipped and maintained something real, not just started things
- Comfortable with Node, REST or similar APIs, and relational data modelling in Postgres
- Writes code that another person can pick up, because in a small team they will have to
- Sensible about scope. The useful version this month beats the perfect version next quarter
Useful, not required
- Experience with search, filtering and large tables rendered quickly in the browser
- Any exposure to publishing systems, data pipelines or document generation
Four things, and we will not pretend there are twenty
We are a small firm. These are real and they are the whole list.
Your name on the work
Research and editions carry bylines. Nothing you make here disappears into somebody else's credit.
Flexible hours, real ones
We work across two time zones, so the day bends. Deadlines are firm, attendance is not.
Health cover
Medical cover for you and your immediate family, in both locations.
A budget to learn
An annual allowance for courses, books, conferences or tools. You choose what, we do not audit it.
Compensation is at market for the role and the city, and we will tell you the range in the first conversation rather than asking what you currently earn.
Four steps, two weeks, no unpaid work
If we are going to say no, we would rather do it quickly than keep you waiting.
You write to us
CV plus the one thing each role asks for. We read everything and we reply either way.
A conversation
Forty-five minutes on what you have done and what the role actually is. We tell you the pay range here.
A working session
Ninety minutes on a real problem, with us, in the room or on a call. Paid if it runs longer.
A decision
A conversation with the founder, then an answer. We do not leave offers hanging.
Write to us anyway
If you can see something the Forum should be doing and is not, that is a more interesting letter than an application to a role we already wrote. Tell us what you would do and why you are the person to do it.
Read what you would be working on
The register, the editions and the method are all public. The best preparation for applying here is to disagree with something we published.