Company: KAVIA AI

Location: India — Remote

Type: Full-time

Reports to: Chief Operating Officer and Head of Customer Solutions Engineering

Experience: 4–8 years

Compensation: INR 20,00,000 to INR 28,00,000 annual CTC, based on background, experience, and demonstrated customer-facing technical ownership

About KAVIA AI

KAVIA AI is an enterprise software company building the enterprise software engineering platform for complex codebases.

We help engineering teams understand, plan, change, and validate large software systems. KAVIA connects code understanding, workflow automation, artifact generation, reviewable code, and validation across repositories and environments.

Our platform is used by enterprise teams working on consequential software systems. As KAVIA’s product and customer footprint grow, we are expanding the customer engineering capability that turns difficult technical use cases into successful pilots and production adoption.

The Role

This is a hands-on, customer-facing engineering role at a growing enterprise software company. At KAVIA, the Customer Solutions Engineer serves as a Forward Deployed Engineer: part software engineer, part technical problem solver, and part pilot owner.

Reporting to KAVIA’s Chief Operating Officer and Head of Customer Solutions Engineering, you will work closely with enterprise engineering customers, KAVIA’s product and engineering teams, and company leadership. You will understand a customer’s codebase and operating constraints, demonstrate KAVIA against the right problem, translate that problem into a tightly scoped pilot, and stay accountable through technical validation.

Success in this role is not measured by the number of demos delivered. It is measured by whether KAVIA earns technical confidence: the right problem is selected, the evaluation is credible, blockers are resolved, results are documented, and the customer can make an informed production decision.

This is not a conventional sales-engineering role built around standard demonstrations, and it is not a support role limited to routing issues. You must be comfortable reading unfamiliar code, working directly in technical environments, and communicating clearly with both engineers and senior stakeholders. The role requires regular overlap with US and European business hours and may include occasional customer travel.

What You’ll DoLead Technical Discovery

- Run structured discovery with engineering leaders, architects, developers, and other technical stakeholders.
- Understand the customer’s codebase, architecture, repositories, build and test systems, development workflow, constraints, and desired outcome.
- Separate the stated request from the underlying engineering problem, and identify where KAVIA can create measurable value.
- Surface dependencies, security or deployment requirements, data-access constraints, technical risks, and decision criteria early.
- Determine whether an opportunity is technically ready for a demonstration or pilot, and say so clearly when it is not.

Prepare and Deliver Tailored Demonstrations
- Design demonstrations around the customer’s actual use case rather than rely on a generic product walkthrough.
- Select representative code, workflows, and evidence that make KAVIA’s value understandable and technically credible.
- Configure and test the demonstration environment, anticipate likely questions, and prepare recovery paths when live systems behave unexpectedly.
- Explain KAVIA’s reasoning, outputs,



limitations, and deployment options with precision and without overclaiming.
- Capture questions and objections, follow up with clear technical answers, and identify what must be proven next.

Convert Use Cases into Well-Scoped Pilots
- Translate discovery into a concise pilot definition with a clear problem statement, scope, inputs, deliverables, responsibilities, dependencies, schedule, and acceptance criteria.
- Define success measures that compare KAVIA-assisted work with the customer’s current process, including time, effort, quality, completeness, or validation outcomes where appropriate.
- Keep pilots narrow enough to execute quickly while meaningful enough to support a purchase or deployment decision.
- Align customer and internal stakeholders on what is in scope, what is not, and what evidence will constitute success before work begins.

Own Pilot Execution and Resolve Technical Blockers
- Serve as the technical owner for assigned pilots from kickoff through final validation.
- Work directly with repositories, manifests, branches, build systems, APIs, development environments, and deployment configurations as required by the engagement.
- Use KAVIA hands-on to investigate the customer’s problem, generate or review outputs, and validate results against agreed criteria.
- Diagnose blockers, distinguish product issues from environment or integration issues, and coordinate the right engineering response without losing momentum.
- Maintain a clear execution plan, technical decision log, risk list, and next action for every active pilot.
- Escalate product gaps and delivery risks early, with enough evidence for engineering and leadership to act.

Move Customers to Technical Validation
- Design and run the final validation against the agreed acceptance criteria, including build, test, review, or workflow evidence where applicable.
- Present results honestly, including what worked, what remains unresolved, and what would be required for production use.
- Quantify before-and-after outcomes when the evidence supports them and avoid unsupported or inflated claims.
- Produce the technical readout, recommendations, open issues, and proposed next step needed for the customer and KAVIA to make a decision.
- Support the transition from successful pilot to deployment, expansion, or a clearly defined follow-on phase.

Turn Customer Learning into Reusable Assets
- Write concise technical follow-ups, solution notes, pilot plans, validation summaries, runbooks, and implementation guidance.
- Contribute credible technical evidence and approved results to case studies, sales collateral, product documentation, and enablement material.
- Convert repeated customer patterns into reusable demo assets, pilot templates, checklists, and internal playbooks.
- Bring structured customer feedback to product and engineering, distinguishing one-off requests from broadly valuable product improvements.
- Help improve KAVIA’s customer-engineering methods as the company builds a repeatable enterprise adoption motion.

What We’re Looking ForRequired




- 4–8 years of professional software engineering, solutions engineering, implementation engineering, or forward deployed engineering experience, with substantial hands-on technical ownership.
- Strong software engineering fundamentals and production experience in at least one widely used programming language such as Python, Java, TypeScript, JavaScript, Go, C, or C++.
- Ability to enter an unfamiliar codebase, form a useful system model, trace dependencies, diagnose failures, and make progress without a fully specified playbook.
- Working knowledge of Git-based development, APIs, build and test workflows, CI/CD, containers, cloud or on-premises environments, and modern software delivery practices.
- Experience leading technical discovery, demonstrations, proofs of concept, pilots, implementations, or similarly bounded customer engagements.
- Ability to translate an ambiguous customer problem into a clear technical plan, measurable success criteria, and disciplined execution.
- Strong written and spoken English, including the ability to explain complex technical matters to engineers, executives, and cross-functional stakeholders.
- Sound judgment under pressure, intellectual honesty about product limitations, and the confidence to challenge an unworkable scope or unsupported claim.
- Solid project ownership, including action tracking, risk management, documentation, follow-through, and timely escalation.
- Ability to maintain dependable overlap with US or European business hours when customer meetings and pilot execution require it.
- Comfort working in a startup environment where priorities change, processes are still being built, and customer outcomes matter more than role boundaries.

Strong Plus
- Experience with enterprise developer tools, AI-assisted software engineering, code intelligence, software modernization, testing, or engineering productivity platforms.
- Experience with complex brownfield systems, multi-repository codebases, embedded Linux, Android, Yocto, RDK, OpenWrt, automotive software, telecom software, or similar platform environments.
- Experience designing secure enterprise deployments, including customer-controlled cloud, self-hosted, restricted-network, or air-gapped environments.
- Experience working with large language models, agentic workflows, retrieval systems, knowledge graphs, or evaluation frameworks.
- Experience gathering defensible before-and-after metrics and presenting technical validation results to enterprise decision-makers.
- Experience working across product, engineering, sales, and customer teams without losing clarity about technical ownership.
- Startup experience or a record of building repeatable methods from early customer engagements.

A Note from KAVIA We are not looking for someone who has used every technology or worked in every domain listed above.

We are looking for a strong, hands-on engineer who can earn trust with enterprise customers, bring structure to ambiguous technical work, and stay accountable until the customer has credible evidence. Applicants with demonstrated engineering depth and customer-facing ownership are encouraged to apply, even if their current title is not Customer Solutions Engineer or Forward Deployment Engineer.

How to Apply

- Please fill this form https://docs.google.com/forms/d/e/1FAIpQLSeKv92ccKCbznHuF8fh5V_6M1FuhEoMuyBPZJU2Wn5TzpRv5Q/viewform?usp=header
- Your current location in India and your ability to maintain regular overlap with US business hours.

📌 Customer Solutions Engineer - Forward Deployment Engineering (India)
🏢 KAVIA AI
📍 India