General interest - join our team!
Description
Introducing Kepler
The Problem
High-stakes industries are falling behind on AI adoption. Models keep getting smarter, but they still don't know a firm's own data, its definitions, or how its people work, and they can't show where an answer came from. When one wrong number can cost millions, that means checking everything by hand. The fix isn't a better model. It's enterprise intelligence: AI built on what a firm already knows, with every output traceable, every calculation auditable, and every answer reproducible.
What Kepler Is
Kepler is a verifiable, auditable agentic harness: the infrastructure layer between AI models and a firm's own data that makes every output reliable and traceable. The model is a replaceable component. The harness is the product.
In Kepler's architecture, the LLM orchestrates - it decides what data to gather, what to compute, how to structure the output. But every actual data point, every extracted value, every calculation flows through deterministic code pipelines. The LLM never touches the data itself. That means every value carries provenance metadata back to its exact source, every computation is auditable and reproducible, and verification loops cross-check outputs before users ever see them.
We started in finance because the stakes are highest and the tolerance for error is zero. Our engineers deploy on each firm's own data, build an ontology of how it works, and turn its workflows into code, so analysts can build models, research filings, and work across their own documents without double-checking every number. Every number traces back to its source, every time.
But the architecture (the firm's own ontology, deterministic computation, provenance) applies anywhere a wrong answer is expensive: chemicals, legal, healthcare. Models are commoditizing fast. The layer that connects them to each firm's own knowledge is what's missing, and the market is massive.
The Team
The founding team spent a combined 40+ years at Palantir building the type of large-scale data infrastructure that Kepler requires. Our founding engineers led Foundry's core systems - Ontology, Fusion, Workshop, FoundryML, created Palantir's first AI platform and scaled data products at Meta to 1B+ users.
We’ve paired this deep technical foundation with a repeat founder profile. Our CEO built and scaled a data company to $15M ARR before successfully selling it. He then became Citadel's first Head of Business Engineering, experiencing first hand the problems we are now solving. We have a team who’ve been on both sides: building systems like this at massive scale and selling them to the buyers who need it most.
We’re backed by investors who built the modern AI and data stacks, plus the builders of iconic commercial businesses. This includes founders of OpenAI, Meta AI Research, MotherDuck, dbt Labs and Square as well as PebbleBed, Company Ventures and Mantis VC firms.
Our Technical Stack
Backend: Rust - agent orchestration, data extraction, computation pipelines.
Frontend: TypeScript, React - the analyst workspace and verification interfaces.
Data: PostgreSQL, plus direct integrations with official data sources.
Infra: AWS.
AI: Model-agnostic by design. We currently use Claude and GPT. The model is the replaceable part.
Mentorship & Growth
You'll be directly mentored by engineers who built Palantir's core systems. Expect:
Weekly 1:1s with senior engineers who've built systems at Palantir and Meta scale.
Deep architectural reviews and guidance on system design.
Clear growth path toward technical leadership and system ownership.
Learn by building production systems that power real financial research.
Working at Kepler
Our Benefits
100% covered top-of-the-line medical, dental, and vision insurance for employees and their families. HSA maxed by the company to the IRS limit.
Automatic coverage for life, AD&D, and disability insurance.
Daily lunch in office.
Unlimited PTO policy.
Development environment budget - latest MacBook Pro, multiple monitors, ergonomic setup, and any development tools you need.
"Build anything" budget - dedicated funding for whatever tools, libraries, datasets, or infrastructure you need to solve technical challenges, no questions asked.
Learning budget - attend any conference, course, or program that makes you better at what we're building.
Our Operating Principles
Trust as the Default: People do their best work when confidence is mutual. We show our work, keep our promises, and flag risks before they bite. Trust isn't an aspiration - it's the baseline.
Forward-Deployed with Product DNA: We own customer outcomes while building a product company. We don't win if they don't win.
Extreme Ownership: If you notice a problem, you own it by making sure it doesn’t fall through the cracks. Authority comes from initiative, not job titles. Once you step up, you're accountable for the outcome.
Production-First Engineering: We design for critical workloads from day one. Durable execution, blue/green deploys, automated rollbacks, continuous delivery with end-to-end observability.
Communicate with Intent: Great work disappears without great communication. We push information to the people who need it, when they need it. Silence is never the safe choice.
Earn it Every Day: Your work speaks for itself. We create an environment where the best idea wins, the strongest work gets recognized, and everyone is held to the same high standard.
Keep Raising the Bar: Great teams compound. Every hire raises the bar, every win gets named, every person gets the tools and runway to grow.
Kepler is an Equal Opportunity Employer and prohibits discrimination and harassment of any kind. We are committed to the principle of equal employment opportunity for all employees and to providing employees with a work environment free of discrimination and harassment.
Skills
As published by ashby · 4 questions · 2 written answers
Basics
Name, Email, Resume
Short answers (1)
- If you selected other, please explain how you heard about Kepler below: optional
Pick from a list (1)
- How did you hear about Kepler?
Written answers (2)
- If you were to join Kepler, what specific role or function would you aim to contribute to in the next 12–18 months? Why?
- What type of work would you be least excited about doing if you were to join Kepler? Why? Be specific.
Sign in to read and join the discussion.