New opportunity

AI Engineer

Willsfly Technologies Inc · Pune, India

About this role

Willsfly Technologies Inc seeks an AI Engineer in Pune, India, for an onsite, full-time role in its AI & Intelligent Systems department. The engineer will develop practical intelligent features for enterprise software and product systems, working with product and platform teams in a connected U.S. and India engineering environment.

Responsibilities

  • Build and improve enterprise AI systems involving retrieval, prompt orchestration, and workflow integration.
  • Integrate models into scalable products using sound API and system design practices.
  • Collaborate to improve product quality, usefulness, and maintainability, and contribute to secure, observable, production-aware AI engineering.

Required qualifications

  • 5+ years of experience in backend engineering, AI engineering, or intelligent workflow systems. The role information lists 5–7 years of experience.
  • Strong knowledge of APIs, data flow, and scalable service integration; hands-on exposure to LLM integration, prompt engineering, or retrieval-based systems; and ability to work in structured enterprise engineering environments.
  • The posting highlights RAG implementation, LLMs, LangChain, FastAPI, and prompt workflows.

Preferred qualifications

  • Experience with RAG, vector workflows, or enterprise AI use cases; exposure to model evaluation, observability, or productionization; and knowledge of cloud-hosted AI service delivery.
  • A bachelor’s degree in Computer Science, AI, Data Science, or Software Engineering is preferred. Azure AI Engineer certification is preferred; LLM or MLOps certification is a plus.

The listed salary range is ?18L–?28L LPA plus a performance bonus, with a 30–60 day notice period. Listed benefits include health insurance, a learning budget, and a flexible work culture. Applicants are asked to provide a resume, professional summary, work eligibility or authorization details, current location, and availability.

For full details about this role, click “Apply on company site” to view the employer’s original posting.

Skills for this role

RAGLLMsLangChainFastAPIPrompt engineeringAPI integrationBackend engineeringVector workflowsModel evaluationObservabilityMLOpsCloud-hosted AI services

Your skill match

Checking your profile…

YOUR NEXT STEP

Get interview-ready for this role

A focused preparation guide, built around this job’s responsibilities and requirements.

✦ AI-generated guide
Preparation suggestions, not the employer’s actual interview questions. Always check the original posting for current requirements.
01

Understand the role

What matters most

  • Enterprise retrieval and prompt workflows

    The role calls for building and improving AI systems across retrieval, prompt orchestration, and workflow integration. Prepare to explain how you would design a RAG-backed feature and improve its usefulness over time.

  • Scalable model integration

    The posting emphasizes integrating models into products with strong API, data-flow, and system-design discipline. Prepare to discuss service boundaries, failure handling, and integration with existing product workflows.

  • Production quality and maintainability

    Responsibilities include secure, observable, production-aware engineering and collaboration with product and platform teams. Prepare examples of design choices that make an AI feature supportable and maintainable.

  • Enterprise delivery collaboration

    The role sits in a connected U.S. and India product-engineering environment and stresses delivery clarity. Prepare to describe how you communicate technical trade-offs and coordinate changes across teams.

Likely challenges to think through

  • Usefulness versus dependable behavior

    Likely preparation challenge, not a reported company problem: retrieval and prompts may produce useful answers while remaining inconsistent or hard to verify. Be ready to explain how you would evaluate outputs, identify failure cases, and decide when to revise retrieval or prompting.

  • Model flexibility versus service discipline

    Likely preparation challenge: rapid changes to models or prompts can complicate API contracts, data flow, and maintainability. Prepare a design rationale for containing those changes within a scalable product integration.

  • Feature speed versus operational safeguards

    Likely preparation challenge: delivering an intelligent feature quickly can compete with security, observability, and production readiness. Prepare to explain which safeguards you would establish early and what you would monitor after release.

03

Practice your answers

Technical practice

How would you design retrieval for an enterprise AI feature?

What to coverThe role includes building AI systems across retrieval and workflow integration. Suggested preparation: explain how content becomes retrievable, how relevant results reach an LLM, and how you would check whether the answers are useful.

How would you troubleshoot poor results from a vector-based retrieval workflow?

What to coverVector workflows are listed as preferred experience. Suggested preparation: distinguish retrieval failures from answer-generation failures, then discuss how you would inspect retrieved results and weigh changes to the retrieval approach.

How would you structure and improve a prompt workflow?

What to coverThe posting highlights prompt workflows and prompt orchestration. Suggested preparation: describe how you would manage inputs, retrieved context and outputs, and how you would test a prompt change before adopting it.

How would you expose an LLM-backed feature through a product API?

What to coverThe role calls for model integration, strong API discipline and scalable product environments; FastAPI is highlighted. Suggested preparation: discuss interface design, request and response handling, failure behaviour, and where framework choices affect maintainability.

How would you design data flow between an AI service and an existing product system?

What to coverStrong knowledge of data flow and scalable service integration is a minimum qualification. Suggested preparation: explain system boundaries, how information moves through the feature, and trade-offs between tighter integration and independent services.

How would you integrate an intelligent feature into a broader workflow?

What to coverWorkflow integration and practical enterprise features are explicit responsibilities. Suggested preparation: describe where an AI step adds value, what happens when it cannot produce a useful result, and how the surrounding workflow remains dependable.

How would you evaluate whether an AI feature improves product usefulness?

What to coverThe role involves product quality and usefulness, and model evaluation is preferred exposure. Suggested preparation: propose representative test cases, explain how you would assess output quality, and distinguish model behaviour from end-to-end product outcomes.

What would you observe when troubleshooting a production AI feature?

What to coverThe posting calls for observable, production-aware engineering. Suggested preparation: discuss how you would trace a request through retrieval, model integration and the product workflow while balancing diagnostic value against sensitive-data exposure.

How would you account for security in a retrieval-backed AI feature?

What to coverSecure AI engineering is an explicit responsibility. Suggested preparation: discuss risks around access to retrieved content and data passed to models, and explain how security decisions interact with usefulness and maintainability.

What would you consider when delivering an AI service in a cloud-hosted product environment?

What to coverCloud-hosted AI service delivery and productionization are preferred areas of knowledge. Suggested preparation: compare deployment and operational trade-offs, including scalability, failure handling and the ability to maintain the service over time.

Behavioural practice

Tell me about a time you worked with product and platform teams to improve a feature.

What to coverCollaboration to improve quality, usefulness and maintainability is part of this role. Suggested preparation: use a real situation, your specific actions with each team, and the resulting product or engineering outcome.

Describe a time you coordinated technical delivery across teams in different locations.

What to coverThe role sits in a connected U.S. and India product engineering structure. Suggested preparation: give the situation, how you kept decisions and handoffs clear, and the result without assuming any particular working arrangement at Willsfly.

Give an example of a technical decision where you balanced immediate delivery with maintainability.

What to coverThe posting emphasizes architecture-conscious execution and long-range software continuity. Suggested preparation: describe the situation, alternatives you considered, the action you took, and what happened afterward.

Tell me about a time you investigated a quality problem in a deployed software feature.

What to coverQuality, observability and production-aware engineering are stated priorities. Suggested preparation: explain the situation, how you identified the cause and worked toward a fix, and the measurable or observable result.

Describe a time you kept a complex engineering deliverable on track while requirements evolved.

What to coverThe role calls for structured enterprise engineering and delivery accountability. Suggested preparation: recount the situation, how you clarified priorities and communicated decisions, and the result of your actions.

02

Sharpen your knowledge

Topics to prepare

  • Retrieval and RAG design

    The posting names retrieval in the responsibilities and highlights RAG implementation; vector workflows are preferred. Sketch a document-to-answer data flow and explain how retrieval quality, source relevance, and stale content affect the result.

  • Prompt orchestration and workflow integration

    The role calls for prompt orchestration and workflow integration. Diagram a multi-step enterprise workflow, identifying what each prompt receives, what it returns, and where failures should be handled.

  • API and scalable service design

    Strong knowledge of APIs, data flow, and scalable service integration is a minimum qualification. Trace a model-backed request from API entry to response, noting service boundaries, latency, and error handling.

  • Production quality and operational tradeoffs

    The responsibilities mention secure, observable, production-aware engineering; evaluation and productionization exposure are preferred. Compare ways to detect poor answers, protect sensitive data, and diagnose failures in a deployed feature.

Skills to revise

  • Build a small RAG flow

    As preparation for the highlighted RAG implementation work, assemble a small retrieval-to-answer example and inspect cases where the retrieved material does not support the answer. This is a practice exercise, not a specified employer assignment.

  • Implement a model-backed API

    Practice exposing a model interaction through a FastAPI endpoint with input validation and explicit error responses. FastAPI is highlighted, and API integration into scalable products is a stated responsibility.

  • Prototype a prompt workflow

    Practice a short, multi-step prompt flow using LangChain, then vary an input and inspect the intermediate outputs. LangChain and prompt workflows are highlighted; use the exercise to discuss integration and maintainability.

  • Evaluate and instrument an AI feature

    As preparation for preferred evaluation and observability exposure, define a small test set, record answer quality and failures, and specify what operational signals would help investigate a bad response. No particular evaluation or monitoring tool is required by the posting.

04

Your preparation checklist

  • Prepare an enterprise AI project walkthrough

    Choose a relevant project, if available, and document its goal, your contribution, architecture, trade-offs and outcome. Focus on retrieval, prompt orchestration or workflow integration, which the role names as responsibilities.

  • Map your experience to the hiring baseline

    Prepare concise evidence of backend, AI or intelligent-workflow experience; API and data-flow design; scalable service integration; and hands-on LLM, prompt or retrieval work. The posting specifies 5+ years and a structured enterprise engineering environment.

  • Practice a RAG feature design

    As interview practice, sketch an enterprise retrieval-to-answer workflow covering data ingestion, retrieval, prompts and integration into a product. Explain design choices and failure cases; RAG, vector workflows, LangChain and FastAPI appear in the posting, but it does not prescribe a stack.

  • Explain production-readiness decisions

    Prepare an example or design notes showing how you would address security, observability, evaluation and maintainability for a model-backed service. The role calls for secure, observable engineering; evaluation and productionization are preferred exposure.

  • Rehearse a cross-team delivery story

    Outline a specific example, if available, of working with product and platform teams: the decisions made, how quality or usefulness was assessed, and how delivery was coordinated. The posting describes a connected U.S. and India engineering environment.

  • Prepare application materials and employer questions

    Have an updated resume, relevant professional summary, work-authorization details, current location and availability ready, as requested. Ask how the team evaluates intelligent features, integrates them into products and coordinates across locations.

AI-generated from the job information · Prepared Sep 30, 2026 (UTC)Useful preparation, not a guarantee of eligibility or an offer.

Availability last checked: 5 Nov 2026. Status can change after a check; confirm on the employer’s website. Report an issue · Our checking policy

KEEP EXPLORING

Similar AI jobs

Related skills and specializations in India. Matched to this role, not your profile.

Explore more jobs
Finding similar opportunities…