
Forward Deployed Engineer
Posted 17 days ago
The role in short
Embed with customers to prototype, evaluate, and deploy verifiable AI workflows and integrations using formal methods and LLMs.
Company
Pramaana Labs is a frontier AI lab building the verification layer for AI. We turn complex human knowledge, including tax codes, legal rules, clinical guidelines and security protocols, into formal representations that support reasoning people can inspect and check. Our architecture pairs models trained to formalize and reason with a symbolic world model encoded in Lean 4. Founded in 2025 and headquartered in Palo Alto, Pramaana brings together researchers and formal methods experts from Google, DeepMind, and Glean.
The Role
The hardest questions in AI emerge when systems meet messy reality. Can ambiguous, exception-filled rules be formalized faithfully? Can we distinguish what is proved from what is assumed, and make the results reliable enough to use? As a Forward Deployed Engineer, you'll work where applied research, software engineering and customer problems meet. Alongside Pramaana engineers and researchers, you'll prototype and evaluate verifiable AI workflows, build tools and integrations, and help take promising systems into production. You'll investigate failures and turn lessons from the field into improvements to our research, models and core technology. We're looking for engineers who think from first principles, learn fast and care deeply about making AI reasoning verifiable. You don't need years of enterprise deployment experience. You'll have strong technical guidance while owning your work and handling real customer challenges with maturity.
What You'll Do
Understand the real technical problem. Work with customers and domain experts to turn source material, rules, exceptions and constraints into clear requirements and success criteria.
Prototype verifiable AI workflows. Experiment with model-based formalization, symbolic reasoning and proof checking on challenging real-world inputs. Find out what works and where it breaks.
Build rigorous evaluations. Create representative examples, edge cases and benchmarks to measure rule fidelity, correctness, coverage and robustness. Reproduce failures and investigate them carefully.
Take systems into production. Build and debug applications, APIs, tools and integrations. Iterate with customer teams, explain limitations and help deliver reliable workflows.
Close the loop with research. Work with researchers to turn customer issues and evaluation results into better representations, models, proof workflows and core technology.
Own problems and improve what comes next. Ask sharp questions, take responsibility for scoped work, communicate blockers early and turn one-off fixes into reusable patterns where possible.
You Will Thrive in This Role If You Have
Strong software engineering fundamentals. You can write clean code, reason about data structures and algorithms, and debug unfamiliar problems.
First-principles and logical thinking. You question assumptions, isolate the essential problem and explain your reasoning clearly.
High initiative and a habit of learning quickly. You have examples of making meaningful progress without waiting for detailed instructions.
A genuine interest in Pramaana's mission. You are deeply excited about reliable, verifiable AI to study the problem and build in this space.
Clear written and verbal communication, including the maturity to stay calm, be candid about uncertainty and work constructively with customers.
Comfort learning from more experienced engineers, asking for help when needed and incorporating feedback quickly.
Especially Strong Candidates May Also Have
Built an impressive personal project, research prototype, hackathon project or meaningful open-source contribution from scratch.
Experience with Python or TypeScript, APIs, backend development, LLM applications, evaluation or developer tools.
Explored formal verification, theorem proving, Lean, logic, symbolic reasoning or AI reliability through work or self-directed learning.
Hands-on experience working with users, handling unexpected problems or explaining technical ideas to non-specialists.
Prep for this interview
3 questions likely to come up at Pramaana Labs, each matched to a line in this posting.
- 1Integrations and APIs
They wrote: “Take systems into production. Build and debug applications, APIs, tools and integrations. Iterate with customer teams, explain limitations and help deliver reliable workflows.”
Walk me through connecting our product to a customer's internal system that has no documentation.
How to answer
Why they ask: This happens weekly in the job. They want a calm, step-by-step method.
- Find who owns the system and get read access to a test environment
- Watch real traffic or logs to learn the data shapes
- Build a thin adapter with logging around every call
- Agree on how failures get reported, and who fixes what
Tip: Talk about finding the owner of the system first. The code is the easy part.
- 2LLMs, RAG and agents
They wrote: “Experience with Python or TypeScript, APIs, backend development, LLM applications, evaluation or developer tools.”
How do you know an LLM feature is good enough to ship?
How to answer
Why they ask: Evals are what separate a demo from production. Many roles list them by name.
- Write 50–200 real examples with expected outcomes, with customer experts
- Agree on a pass bar and the errors that are never acceptable
- Score automatically where possible; review a sample by hand
- Re-run on every prompt or model change, and watch live traffic after launch
Tip: Describe a test set built with the customer, a pass bar agreed up front, and checks that run on every change.
- 3Coding
They wrote: “Strong software engineering fundamentals. You can write clean code, reason about data structures and algorithms, and debug unfamiliar problems.”
You get a codebase you've never seen and one hour to fix a bug. Where do you start?
How to answer
Why they ask: FDEs work inside customer and product code they didn't write.
- Reproduce the bug with the smallest example
- Find where the data goes wrong (search, logs, debugger)
- Make the smallest fix and add a test that fails without it
- Note anything risky you saw but didn't change
Tip: Reproduce first. Then narrow down with logs or a debugger before changing anything.
Not the one? Get the next one by email
New roles land here every day. Pick what you want to hear about.
Want the job, not just the posting? Learn how FDEs work.
FDE Info is our free weekly newsletter for forward deployed engineers: tools, field notes from real deployments, and how FDE teams hire and pay.
Free. One email a week. Unsubscribe in one click.