New opportunity

GEN AI Engineer

INFOSYS LIMITED · Bangalore, India

About this role

The GEN AI Engineer joins the Infosys Delivery team in Bangalore to implement designs and develop high-quality programs and systems for clients. The role sits within Engineering Services and calls for knowledge of generative AI, AI/ML solution architecture and design, and prompt engineering.

Responsibilities

  • Implement designs, develop programs and systems, and work with clients to deliver quality outcomes.
  • Create technical artifacts; serve as an initial contact for production issues, analyze problems, and coordinate responses with stakeholders.
  • Execute planned test cases and scenarios. Share project learnings through knowledge-management initiatives and apply lessons from other projects to improve effectiveness.

Requirements

  • 2–5 years of work experience. Accepted educational qualifications are Bachelor of Engineering, BSc, BTech, BCA, MCA, MSc, or MTech.
  • Advanced conceptual understanding of at least one programming language, one database, and one operating system; software-engineering practice on at least one project.
  • Ability to handle medium-to-complex tasks independently, understand design specifications, and work with design principles. The posting also calls for understanding of the software development life cycle, analytical ability, logical thinking, and awareness of current technologies and trends.
  • Technical and professional requirements identify generative AI and prompt engineering. The posting repeats both under preferred skills.

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

Skills for this role

Generative AIPrompt EngineeringAI/ML Solution ArchitectureProgrammingDatabasesOperating SystemsSoftware EngineeringDesign PrinciplesTest ExecutionSDLCProduction SupportTechnical AnalysisKnowledge ManagementAnalytical Thinking

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

  • Turn designs into client deliverables

    The posting emphasizes implementing designs, developing high-quality programs and systems, and partnering with clients. Prepare to explain how you interpret a design specification, make implementation decisions, and check that the result meets the intended outcome.

  • Apply generative AI and prompt engineering

    Generative AI within AI/ML solution architecture and design, and prompt engineering, are named technical requirements. Prepare to explain the design choices behind a generative-AI solution and how you assess whether a prompt serves its intended purpose.

  • Test and support what you build

    The role includes running planned test cases and scenarios, serving as an initial contact for production issues, and conducting technical analysis. Prepare to describe a disciplined path from test results or issue reports to diagnosis and response.

  • Create reusable technical knowledge

    The posting calls for technical artifacts, sharing project learnings, and applying knowledge from other projects. Prepare an example of documentation or a lesson learned that made subsequent engineering work more effective.

Likely challenges to think through

  • Balancing independent delivery with design constraints

    A likely difficulty is making progress on medium-to-complex tasks independently without drifting from the design specification; this is a preparation hypothesis, not a reported problem. Rehearse how you resolve ambiguity, document assumptions, and identify decisions that need clarification.

  • Balancing prompt behavior with system quality

    Because the role combines prompt engineering with high-quality software delivery, a plausible challenge is deciding whether an unwanted result calls for a prompt change, a system change, or further testing. Prepare a concrete example of comparing those options against the intended behavior.

  • Diagnosing issues while coordinating a response

    As an initial contact for production issues, the engineer may need to investigate quickly while keeping stakeholders informed; the posting does not specify an incident process. Prepare to explain how you would separate observed facts from hypotheses, prioritize the next check, and communicate findings.

03

Practice your answers

Technical practice

How would you translate a client need into a generative AI solution design?

What to coverThe posting identifies generative AI and AI/ML solution architecture and design. Suggested preparation: explain how you would clarify the desired outcome, define system boundaries, and compare design options against quality and efficiency.

How would you design a prompt for a task with a specific output format?

What to coverPrompt engineering is explicitly listed as a technical requirement. Suggested preparation: discuss clear instructions, relevant context, output constraints, and how you would revise the prompt when results do not meet the task.

How would you assess whether a prompt change improved results?

What to coverThe posting names prompt engineering and planned test execution, but does not prescribe an evaluation method. As a suggested preparation exercise, describe comparable test inputs, criteria tied to the intended output, and the trade-off between improving one case and maintaining performance across others.

How would you implement a design specification as a maintainable program?

What to coverThe role involves implementing designs, developing high-quality programs, and understanding design specifications independently. Suggested preparation: explain how you would identify interfaces and constraints, apply design principles, and check that the implementation matches the specification.

Which concepts in a programming language would you use to make a system reliable and efficient?

What to coverThe posting calls for advanced conceptual understanding of at least one programming language and contribution to efficient programs and systems. Suggested preparation: use a language you know to explain error handling, data structures, and a performance-versus-readability decision without assuming a required language.

How would you design and troubleshoot the data access for an application?

What to coverAdvanced conceptual understanding of one database is stated, but no database product is named. Suggested preparation: explain data organization, query behavior, and how you would investigate a slow or incorrect result in a database you know.

How can operating-system behavior affect a running program?

What to coverThe posting asks for advanced conceptual understanding of one operating system. Suggested preparation: discuss processes, memory, files, and permissions in an operating system you know, including how you would distinguish an application fault from an environment issue.

How would you execute a planned test scenario and report a failure?

What to coverThe role explicitly includes running test cases and scenarios according to a plan. Suggested preparation: describe checking expected against actual results, preserving reproducible evidence, and distinguishing a product defect from a test or environment problem.

What would you do when you are the first technical contact for a production issue?

What to coverThe posting assigns initial response, technical analysis, and stakeholder coordination for production issues. Suggested preparation: explain how you would establish impact, collect evidence, narrow possible causes, communicate findings, and verify that a proposed resolution addresses the issue.

What technical artifact would you create to support implementation and later maintenance?

What to coverCreating technical artifacts and understanding the software development life cycle are stated expectations; no artifact format is specified. Suggested preparation: choose an artifact relevant to a design or change and explain how it records decisions, supports testing, and helps another engineer understand the system.

Behavioural practice

Tell me about a time you worked with a client to clarify what a quality deliverable meant.

What to coverThe role involves partnering with clients to deliver high-quality outcomes. Use a real situation/action/result example that shows how you clarified expectations, handled a difference in interpretation, and established the result.

Describe a medium-to-complex task you handled independently.

What to coverThe posting calls for independent contribution on medium-to-complex tasks. Give a real situation/action/result example covering how you understood the specification, made decisions, sought clarification where needed, and checked the outcome.

Tell me about a production issue that required coordination with stakeholders.

What to coverInitial production response and stakeholder coordination are stated duties. Use a real situation/action/result example that separates your technical investigation from your communication actions and explains the outcome without overstating your role.

Describe a time you shared a project lesson or applied one learned elsewhere.

What to coverThe posting explicitly mentions knowledge-management initiatives and using learning from other projects to improve effectiveness. Give a real situation/action/result example showing what you documented or adopted, who could use it, and what changed.

02

Sharpen your knowledge

Topics to prepare

  • Generative AI solution design

    Posted requirement: generative AI within AI/ML solution architecture and design. Revision exercise: sketch a generic generative AI feature, label its inputs, outputs and system boundaries, and explain the design choices. The feature is practice, not a stated Infosys project.

  • Prompt engineering principles

    Posted requirement and preferred skill: prompt engineering. Revision exercise: compare two prompts for the same task and explain how clearer instructions and output criteria could change the result.

  • Programming language fundamentals

    Posted requirement: advanced conceptual understanding of at least one programming language. Revision exercise: choose one language you know and explain its error handling, data structures and approach to organizing maintainable code. The posting does not name a language.

  • Database and operating-system fundamentals

    Posted requirement: advanced conceptual understanding of one database and one operating system. Revision exercise: trace how a program reads data, handles a database failure and uses operating-system resources. The posting does not specify products.

  • Design principles and the SDLC

    Posted requirements: understand design specifications independently, apply design principles and understand the software development life cycle. Revision exercise: turn a short specification into components, acceptance criteria and a plan for implementation and testing.

Skills to revise

  • Implement a design

    Posted responsibility: implement designs and develop high-quality programs and systems, including medium-to-complex tasks independently. Practice implementing a small, self-contained specification in a language you choose, then explain how the result follows the design. The exercise is a preparation suggestion, not an assigned project.

  • Iterate on prompts

    Posted skill: prompt engineering. Practice writing a prompt for a sample task, testing it against several inputs and revising it when an output misses the stated criteria. The sample task is a preparation suggestion.

  • Execute planned test cases

    Posted responsibility: run test cases and scenarios as planned. Given a sample test plan, execute each case, record expected versus actual results and describe how you would report a failure.

  • Analyze a production issue

    Posted responsibility: be an initial contact for production issues, conduct technical analysis and coordinate with stakeholders. Rehearse a hypothetical failure: establish its impact, separate observations from possible causes and draft a concise status update. The failure scenario is a preparation suggestion.

  • Write a technical artifact

    Posted responsibilities: create technical artifacts and share project learnings through knowledge-management initiatives. Draft a brief design-and-test note for the practice implementation, including one lesson learned that another project could reuse.

04

Your preparation checklist

  • Prepare a project walkthrough

    Choose one software-engineering project and outline the design specification, your implementation, technical artifacts, tests, and outcome. Highlight a medium-to-complex task you handled independently, if applicable.

  • Practice a generative AI design exercise

    Sketch a hypothetical client solution with its components, design choices, and trade-offs. This is preparation for the posting’s generative AI and AI/ML solution architecture focus, not a specified project.

  • Demonstrate prompt engineering decisions

    Prepare sample prompts for a hypothetical use case, explain each revision, and define test cases for checking the responses. The posting names prompt engineering and planned test execution.

  • Organize evidence of core engineering knowledge

    Prepare brief examples showing how you used one programming language, one database, and one operating system, plus how your project work followed the software development life cycle.

  • Rehearse a production-issue response

    Walk through a real or hypothetical issue: initial response, technical analysis, stakeholder coordination, and resolution. Distinguish what you personally did from what you would propose.

  • Capture a reusable project lesson

    Draft a short knowledge-sharing note describing a project lesson and how it could improve future work; the role calls for sharing and applying learnings across projects.

  • Prepare questions for the employer

    Ask how this delivery team divides client-facing work, design implementation, prompt engineering, test execution, and first-response production support. The posting names these activities but does not describe their balance.

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

Availability last checked: 4 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…