The team

Falconer is building the AI-native knowledge platform for engineering teams

Falconer writes and updates your docs as your code changes, then answers questions with citations, in the editor, in Slack, or in whatever AI tool you already use. We're engineers, researchers, and technical writers from Stripe, Meta, Google, and Uber who spent years watching knowledge rot at scale. Now we're building the fix.

Founders

Dave Nunez

Co-founder & CEO

Dave spent nearly ten years building knowledge infrastructure inside two of the most demanding engineering orgs: Head of Information Platform through Uber's hyper-growth, then five years running docs as a product at Stripe, the docs engineers still hold up as the gold standard. Along the way he saw what broken knowledge costs: decisions re-litigated 18 months after someone had already settled them, new hires taking a full quarter to learn why a service worked the way it did, and strong engineers burning out as human search engines. From inside the world's fastest growing tech companies, Dave saw that current knowledge isn't solely documentation hygiene, but more importantly it decides how fast a team can move. He co-authored Docs for Developers and advised teams at Anthropic, Graphite, and Apollo GraphQL.

Maxi Benedetto

Co-founder & CTO

Maxi led autonomous content generation at Meta, working on AI across Facebook and Instagram, and before that built Uber's real-time dispatch systems. On those teams he watched it happen from the inside: even the sharpest engineers lost hours re-deriving decisions and chasing down context that lived in someone's head or an old thread, slowing down the whole org. He's convinced docs drift is a retrieval-and-grounding problem, not a writing one: the right answer usually exists somewhere, buried under stale and contradictory versions of itself. To him, a good knowledge base is one engineered to get smarter as it ages, encoding what's new, decaying what isn't, and flagging itself when it goes stale.

Why we're building Falconer

Knowledge is power, but only when it's healthy.

Stale, scattered, contradictory, or missing knowledge slows your team and misleads your agents.

We've experienced it on every engineering team we've been on. Docs drifted from the code, people stopped trusting them, and the real knowledge stayed trapped in memory. Those people became bottlenecks.

At Uber and Stripe we fought this by hand for years with better tooling, better search, and deliberate writing culture. It worked, but it took armies of people and constant effort. Then AI made shipping code faster than any team could capture what it knew, and the gap became a chasm. Coding agents made it worse, pulling confidently from context that was already stale.

So we built Falconer to keep engineering knowledge current on its own: writing and updating docs as the code changes, and answering with citations you can trust. When knowledge maintains itself, nobody has to be the bottleneck.

The team

Falconer is built by a lean, talent-dense team founded in 2025 in San Francisco, California.

The team comes from Meta, Stripe, Amazon, Uber, and Bytedance building at these orgs through hyper-growth, when knowledge breaks quick. Alongside them are young builders native to the AI era: top open-source contributors, engineers behind Ironclad's agent, and skilled backend engineers from Amex.

We've worked with knowledge across every scale, from early days to hyper-growth, so we know where it breaks down and the power of highly curated and accessible knowledge.

It's a team full of builders with high agency across every function, from engineering to design to marketing. We hold an unfairly high bar, give everyone principal-level scope, put building above bureaucracy, and expect people to own problems end to end.

How we work

Build something you're proud of

Believing in the mission is table stakes here. Everyone builds toward it, from engineering to marketing to customer experience. Every engineer knows the pain of outdated docs and lost knowledge, so you'll solve a problem every team faces and build tools worth taking pride in.

Autonomy through focus

We know what matters - time to build and think deeply. We cut distractions with simple communication structures and asynchronous work, giving you space to focus and do your best work.

Meaningful collaboration

We garden a writing-first communication culture. This makes live collaboration energizing - not for status updates, but for open-ended conversations that foster creativity and new ideas.

Learn through building

We value impact over rituals. Build, experiment, decide fast, and learn even faster. We reward sound judgment, curiosity, and smart risk-taking. If something isn't delivering value, we fix it.

Build momentum

We look to take smart risks, name our shortcomings, and lean into our strengths, because complacency kills momentum. That extends to your growth: we reward strong performance and fast growth, and if you're not expanding your skills, responsibilities, and impact, we'll say so. You own the plan and the execution.

Open roles

We're a small team building the knowledge layer engineering has needed for a decade: a source of truth that writes itself, stays current as the code changes, and keeps every person and agent grounded in what's actually true.

If that's the kind of problem you want to own, take a look at where we're hiring.

See open roles