At a Glance
- Tasks: Join us in building cutting-edge AI solutions and tackle complex research challenges.
- Company: Innovative AI company at the forefront of enterprise technology.
- Benefits: Competitive salary, private healthcare, wellness perks, and vibrant team culture.
- Other info: Access to a unique builder community and exciting networking opportunities.
- Why this job: Be part of a founding team shaping the future of AI with real impact.
- Qualifications: Experience in knowledge graphs, Rust, Python, and a passion for AI problem-solving.
The predicted salary is between 60000 - 80000 £ per year.
What we're building: Frontier models now score above 170 on IQ tests. Reasoning is no longer the constraint on enterprise AI. Context is. The context layer sits between an enterprise's siloed data and the agents that need to act on it. Stuff the context window and you trade quality for cost and latency. Use naive RAG and retrieval breaks the moment the question gets interesting. Stand up a vanilla knowledge graph and you hit the harder problem underneath: someone has to design the ontology, and at enterprise scale (hundreds of thousands of files, hundreds of gigabytes) no human can.
This is what gates almost every enterprise AI deployment we've seen. 60x solves it. We've built AI Brain, a knowledge graph platform engineered backwards from the agentic retrieval problem. The thesis is dynamic ontology generation: the graph schema isn't authored by a user, it's generated by a multi-agent ingestion pipeline from the business logic of the data itself, and continuously enriched with secondary and tertiary derivatives. Pre-digested analysis lives in the graph so retrieval is a lookup, not a reasoning loop.
We operate a Palantir model for workflows. Platform sits at the centre. Forward-deployed engineers wrap it around enterprise workflows we've already templated. Customisations get retained as IP and feed back into the platform. Same flywheel shape as Palantir, different domain. We work with enterprises across multiple sectors, and a growing list of global consultancies are evaluating us against their internal GPT deployments. In the last two weeks we shipped a redesigned ingestion pipeline, primary entity extraction with auto-enrichment, and an end-to-end demo across 500 companies. That pace is the default.
This is a founding role. The parts of the platform you'll work on are the parts that decide whether the thesis holds.
The role: You'll work on the research-grade core of AI Brain alongside the CTO (exited robotics founder) and the senior engineering team. The open problems on the desk:
- Dynamic ontology generation: The graph schema is generated, not authored. Structure emerges from the business logic of the data, with analytical insight pre-computed and stored rather than recomputed on every query.
- Primary entity consolidation: When a single real-world entity (a company, a person, a product) appears across hundreds of documents under different names, the graph has to recognise it as one thing.
- Our own temporal graph database (Rust): Existing graph stores don't carry the temporal model we need, so we're building our own in Rust.
- Benchmark and white paper: Existing large-context retrieval benchmarks are saturated. We need a new one.
- Frontier work we’ll explore soon: Open ideas from research conversations.
You'll also contribute to hiring, technical input on client engagements where it matters, and white paper authorship.
Our stack: Agents: LangGraph with Pydantic-typed state, Claude via Vertex AI, Gemini for fast tagging. Graph and data: Postgres plus Apache AGE today, with a Rust temporal graph database in active development as the long-term replacement. Backend: FastAPI, Python 3.12, Pydantic everywhere. Frontend: Next.js (App Router), TypeScript, Tailwind, shadcn, Vercel. Infra: GCP across compute, storage, model serving, and key management. Tooling: pnpm, Husky commit hooks (lint, format, typecheck, test, agentic check), Linear, Claude Code as a daily driver.
We're opinionated about code quality and we use AI coding agents hard. Founding-team velocity assumes it.
What we're looking for: Depth in at least one of: knowledge graphs and GraphRAG, retrieval systems, agent orchestration, or large-scale data ingestion. A track record of taking research papers or first-principles thinking through to working production systems. Rust experience. Strong Python, and enough TypeScript to ship product surface where it matters. The instinct to read someone else's PR, see three things to improve, and write the comment kindly. Taste. Excitement about this problem space, not AI in the abstract.
You don't need a PhD. You do need to operate at that level on the problems we care about.
Beyond the role: The community. 60x sits at the centre of Unicorn Mafia, the invite-only builder community we run. Day one, you're in. Events are free. International trips are paid for. We hand-pick who sits in the office to keep talent density high. The lifestyle: We look after the team and we socialise together. Private healthcare and a wider wellness benefits package. Sauna and cold plunge sessions for recovery and team time. Team socials, dinners, off-sites, and the overflow from UM events.
Research Engineer (Design) in London employer: 60x
Contact Detail:
60x Recruiting Team
StudySmarter Expert Advice 🤫
We think this is how you could land Research Engineer (Design) in London
✨Tip Number 1
Network like a pro! Get out there and connect with people in the industry. Attend meetups, conferences, or even online webinars. You never know who might have a lead on your dream job or can introduce you to someone who does.
✨Tip Number 2
Show off your skills! Create a portfolio or GitHub repository showcasing your projects and contributions. This is your chance to demonstrate your expertise in knowledge graphs, dynamic ontology generation, or whatever floats your boat. Make it easy for potential employers to see what you can do!
✨Tip Number 3
Don’t just apply blindly! Tailor your approach for each company. Research their projects and challenges, then highlight how your skills can help solve their specific problems. This shows you're genuinely interested and not just sending out cookie-cutter applications.
✨Tip Number 4
Leverage our website! Apply directly through StudySmarter’s platform for a better chance of getting noticed. We’re all about connecting talent with opportunities, so make sure you’re in the right place at the right time!
We think you need these skills to ace Research Engineer (Design) in London
Some tips for your application 🫡
Tailor Your Application: Make sure to customise your application to reflect how your skills and experiences align with the role of Research Engineer. Highlight your expertise in knowledge graphs, dynamic ontology generation, or any relevant projects you've worked on that showcase your problem-solving abilities.
Show Your Passion: We want to see your excitement about the specific challenges we face at 60x. Share your thoughts on the context layer and why you’re keen to work on dynamic ontology generation or temporal data systems. Let your enthusiasm shine through!
Be Clear and Concise: When writing your application, keep it straightforward. Use clear language and avoid jargon unless it's relevant. We appreciate a well-structured application that gets straight to the point while still showcasing your personality.
Apply Through Our Website: Don’t forget to submit your application through our website! It’s the best way for us to receive your details and ensures you’re considered for the role. Plus, it shows you’re serious about joining our team!
How to prepare for a job interview at 60x
✨Know Your Stuff
Make sure you understand the core concepts of dynamic ontology generation and knowledge graphs. Brush up on your Rust and Python skills, as well as any relevant experience with retrieval systems. Being able to discuss your past projects and how they relate to the role will show that you're not just a good fit, but also genuinely interested.
✨Prepare for Technical Questions
Expect to dive deep into technical discussions during the interview. Prepare to explain your thought process behind solving complex problems, especially those related to entity consolidation and temporal data systems. Practising coding challenges in Rust and Python can help you feel more confident when tackling these questions.
✨Show Your Passion
This role is all about excitement for the problem space, so be ready to share why you're passionate about AI, knowledge graphs, and the context layer. Discuss any relevant research papers you've read or projects you've worked on that align with their mission. Your enthusiasm can set you apart from other candidates.
✨Ask Insightful Questions
Interviews are a two-way street, so come prepared with thoughtful questions about the company's vision, the team dynamics, and the specific challenges they face. This not only shows your interest but also helps you gauge if this is the right environment for you. Asking about their approach to code quality and collaboration can also give you valuable insights.