New opportunity

Artificial Intelligence Engineer

Go Digital Technology · Mumbai, India

About this role

Go Digital Technology seeks an AI engineer to lead the design, development and production deployment of generative AI and machine learning solutions. The role spans end-to-end ownership, technical leadership and collaboration with product and business teams.

Responsibilities

  • Architect GenAI systems covering data pipelines, training, evaluation, deployment and monitoring. Build and scale LLM-powered applications, retrieval-augmented generation, prompt optimization, fine-tuned models and AI-agent workflows.
  • Deploy production-grade solutions on AWS using Bedrock and SageMaker. Apply machine learning and deep learning to forecasting, prediction and automation.
  • Mentor AI engineers and data scientists. Ensure solutions meet scalability, performance and responsible AI requirements.

Required qualifications

  • 5–9 years in AI/ML, data science or AI engineering, including 1–2 years in a technical leadership role, and a track record of scaling production AI or GenAI systems.
  • Expertise in machine learning, deep learning and statistical modeling; hands-on GenAI experience; and experience deploying AI/ML solutions on AWS.
  • Proficiency in Python and libraries including pandas, NumPy, scikit-learn and PyTorch or TensorFlow; SQL and large-scale data processing; and ML system design and model evaluation.

Preferred qualifications

MLOps experience with CI/CD, monitoring and model versioning; exposure to Spark and distributed systems; familiarity with FAISS, Pinecone or Weaviate; and understanding of AI governance and responsible AI frameworks.

Location and arrangement: Mumbai, Maharashtra, India; hybrid, with four days in the office and one day remote. The posting lists permanent employment and compensation of ₹ 40-50 Lacs PA.

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

Skills for this role

Generative AIMachine LearningDeep LearningStatistical ModelingLarge Language ModelsRetrieval-Augmented GenerationPrompt EngineeringFine-TuningAI AgentsPythonpandasNumPyscikit-learnPyTorchTensorFlowSQLAWSAmazon BedrockAmazon SageMakerData ProcessingML System DesignModel EvaluationMLOpsCI/CDModel MonitoringModel VersioningSparkDistributed SystemsVector DatabasesFAISS LinkedIn? Hmm

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

  • Own the AI lifecycle

    The role leads solutions from design through deployment and monitoring, including data pipelines, training and evaluation. Prepare to explain end-to-end architectural decisions using a production system as an example.

  • Build and scale GenAI applications

    The posting names LLM applications, RAG, prompt optimization, fine-tuning and agent workflows. Prepare to explain when each approach is appropriate and how you would evaluate its results.

  • Deploy production AI on AWS

    Production-grade deployment with Bedrock and SageMaker is an explicit duty. Scalability, performance and responsible AI practices are also stated expectations.

  • Apply ML beyond GenAI

    The role includes machine learning, deep learning and statistical modeling for forecasting, prediction and automation. Prepare to discuss model choice and evaluation for these use cases, not only LLMs.

  • Lead across technical and business teams

    The engineer will mentor AI engineers and data scientists and collaborate with product and business teams. Prepare examples of technical direction, mentoring and translating a business goal into an AI solution.

Likely challenges to think through

  • Choosing the right GenAI approach

    Preparation hypothesis, not a reported company problem: RAG, prompt changes, fine-tuning and agents can offer different quality, complexity and performance trade-offs. Prepare a decision framework and explain what evidence would justify a more complex approach.

  • Taking prototypes into reliable production

    Preparation hypothesis: scaling an AI system may make evaluation, monitoring, performance and responsible use harder to balance. Prepare to walk through how you would test, deploy and monitor a system on AWS, while distinguishing required deployment experience from the posting’s preferred MLOps experience.

  • Balancing hands-on ownership with leadership

    Preparation hypothesis: end-to-end delivery, mentoring and product collaboration may compete for time. Prepare an example of how you set technical direction, delegated work and resolved a delivery trade-off without losing oversight of the system.

03

Practice your answers

Technical practice

How would you architect a generative AI solution from data pipeline through production monitoring?

What to coverSuggested preparation: Explain how you would connect data preparation, model or application development, evaluation, deployment and monitoring. Discuss design choices that would change with scale, performance needs or the use case.

How would you design and evaluate a retrieval-augmented generation application?

What to coverSuggested preparation: Cover document preparation, retrieval, use of a vector database and how retrieved content reaches the LLM. Explain how you would assess both retrieval quality and the resulting answers; FAISS, Pinecone and Weaviate are listed as nice-to-have familiarity, not required tools.

When would you use prompt optimization rather than fine-tuning or model adaptation?

What to coverSuggested preparation: Compare the data, effort, evaluation and operational implications of each approach. Describe how you would test whether an adaptation improves the intended task enough to justify its complexity.

How would you make an AI-agent workflow dependable in production?

What to coverSuggested preparation: Explain how you would structure orchestration, constrain agent actions and handle errors or uncertain outputs. Address how you would evaluate the workflow as a whole, not just its underlying model.

How would you approach deploying an AI solution with AWS Bedrock and SageMaker?

What to coverSuggested preparation: Describe which parts of an example solution you would place in each service and why, without assuming the employer uses a particular architecture. Cover deployment, evaluation and operational considerations for a production-grade system.

How would you build and validate a forecasting or prediction model?

What to coverSuggested preparation: Discuss an appropriate statistical, machine-learning or deep-learning baseline, relevant features and a validation scheme that avoids leakage. Explain how you would compare model quality with complexity and operational cost.

How would you prepare large-scale data for ML using SQL and Python?

What to coverSuggested preparation: Explain how you would check data quality, construct reproducible features and manage processing at scale. Discuss when distributed processing might help; Spark is listed as nice-to-have exposure.

How would you evaluate an LLM-powered application before release?

What to coverSuggested preparation: Define measures tied to the application’s task, alongside checks for reliability and problematic outputs. Explain how you would use representative test cases and interpret trade-offs rather than relying on a single score.

How would you troubleshoot a production AI system that becomes slower or less effective?

What to coverSuggested preparation: Describe what you would monitor across data, model, application and infrastructure, then how you would isolate the cause. Discuss safe changes, versioning and CI/CD as possible operational practices; MLOps experience is listed as nice to have.

How would you incorporate responsible AI into a system design?

What to coverSuggested preparation: Identify risks appropriate to the use case and explain how you would evaluate and mitigate them throughout development and deployment. Distinguish practical checks from formal governance frameworks, which the posting lists as nice-to-have understanding.

Behavioural practice

Tell me about a time you mentored an AI engineer or data scientist.

What to coverSuggested preparation: Use a real situation, your specific coaching actions and the result. Explain how you supported the person’s work while maintaining technical standards.

Describe a time you worked with product or business colleagues to define an AI solution.

What to coverSuggested preparation: Give the situation, how you clarified the problem and constraints, and the result. Show how you communicated technical trade-offs without assuming a particular company process.

Tell me about a time you led an AI project from design toward production.

What to coverSuggested preparation: State the situation, your leadership decisions and the outcome, including what you personally owned. Explain how you coordinated work across development, evaluation and deployment.

Describe a production AI setback you had to address.

What to coverSuggested preparation: Use a real situation, the steps you took to investigate and respond, and the result. Highlight how you prioritized reliability, performance or model quality under the circumstances.

Tell me about a time you raised a responsible-AI concern or challenged a proposed approach.

What to coverSuggested preparation: Describe the situation, the evidence you used and how you worked with others to decide what to do. State the outcome without overstating your authority or the impact.

02

Sharpen your knowledge

Topics to prepare

  • End-to-end GenAI system design

    Sketch a system from data pipeline through training or adaptation, evaluation, deployment, and monitoring. Explain scaling and performance trade-offs. This matches the role’s explicit end-to-end architecture and production ownership.

  • LLM solution choices

    For one application scenario, compare prompt optimization, RAG, fine-tuning, and an agent workflow; explain when each adds value and what could fail. All four are named in the posting.

  • ML, deep learning, and evaluation

    Choose a forecasting or prediction problem and justify a statistical baseline, an ML or deep-learning approach, and evaluation measures. The role explicitly covers these methods and model evaluation.

  • Responsible production AI

    Review a hypothetical deployment for performance, scalability, and responsible-AI risks, then propose checks before and after release. Responsible AI is an explicit responsibility; governance frameworks are only listed as nice to have.

  • Technical leadership and collaboration

    Rehearse explaining an AI system design to product and business stakeholders, including trade-offs and how you would guide engineers through delivery. The posting calls for team mentoring and cross-functional collaboration.

Skills to revise

  • Python and SQL data preparation

    Write SQL to extract and aggregate sample records, then use pandas and NumPy to check data quality and prepare features. Both SQL and these Python libraries are explicit requirements for the role’s data-processing work.

  • Implement and assess a model

    Build a small forecasting or prediction baseline with scikit-learn, then compare it with a PyTorch or TensorFlow model using a documented evaluation split. These libraries and ML/DL evaluation are explicitly named.

  • Build a small RAG workflow

    Create a document retrieval and answer-generation example; vary prompts and inspect retrieval errors and unsupported answers. RAG, LLM applications, and prompt optimization are explicit duties. Trying FAISS, Pinecone, or Weaviate is optional preparation because familiarity with them is only preferred.

  • Plan an AWS deployment

    If you have access, practice a small deployment using Bedrock or SageMaker; otherwise, walk through deployment steps, evaluation, and monitoring on paper. Production deployment with these AWS services is explicitly required.

  • Trace a model release

    Work through a sample model update: record its version, define a release check, and specify monitoring signals and a response to degraded results. This is relevant to production ownership; CI/CD, monitoring, and model versioning as MLOps experience are listed as nice to have.

04

Your preparation checklist

  • Prepare a production AI walkthrough

    The posting asks for end-to-end ownership and a track record of scaling production AI or GenAI systems. Prepare one example, if available, covering the problem, architecture, your decisions, evaluation, deployment, monitoring and measured results.

  • Sketch a GenAI system design

    Practice explaining a design for an LLM application with retrieval-augmented generation. Show the data pipeline, retrieval and prompt choices, evaluation, deployment, monitoring and how you would address scale and performance.

  • Explain AWS deployment decisions

    The role specifies AWS Bedrock and SageMaker. Prepare to explain relevant deployment experience, if available, or work through when you would use each service and how you would evaluate and monitor the resulting system.

  • Organize evidence for core ML skills

    Choose concise examples that demonstrate Python, SQL, large-scale data processing, model evaluation and ML or deep-learning methods. Be ready to explain trade-offs and results rather than list libraries.

  • Prepare a technical leadership example

    The posting calls for 1–2 years of technical leadership, mentoring, and collaboration with product and business teams. Prepare an example showing how you aligned a technical decision with a business need and supported other engineers.

  • Review production safeguards

    Prepare to discuss scalability, performance and responsible AI, which are stated responsibilities. CI/CD, model versioning, Spark and vector databases are listed as nice-to-haves; discuss them where you have relevant experience, without presenting them as required.

  • Write questions for the employer

    Ask which GenAI use cases are priorities, how the team evaluates production systems, what the lead engineer would own, and how product and business teams participate in decisions.

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…