New opportunity

Large Language Model Architect

Accenture · Hyderabad, India

About this role

The Large Language Model Architect is a hands-on AI LLM Technology Architecture engineering role in Hyderabad. The position designs and operationalizes enterprise LLM, generative AI and agentic AI components for client engagements, translating architecture into production-quality Snowflake applications, RAG pipelines and multi-agent workflows. The listing states 5–10 years of experience and separately requires a minimum of 7.5 years.

Responsibilities

  • Build prompts, tools, agents, orchestration flows, memory and context handling, retrieval pipelines and evaluation harnesses. Develop Cortex-powered applications within Snowflake, including RAG and document intelligence using Cortex Search and Cortex AI Functions, and integrate Streamlit and Snowpark applications.
  • Implement ingestion, parsing, chunking, enrichment, embeddings, vector search and retrieval for structured and unstructured content. Apply RBAC, masking, lineage and monitoring for regulated use cases.
  • Engineer PII detection and redaction, prompt-injection defenses, content filters, guardrails, authentication, authorization and audit logging. Contribute code, technical decisions, reusable patterns, component designs, integration specifications, deployment runbooks and evaluation results. Work with architects, data engineers, product owners and security stakeholders to deliver tested, observable and maintainable components.

Requirements

  • A bachelor’s degree in Computer Science, Computer Engineering, Data Science, AI/ML, Information Technology or a related engineering discipline; the posting also specifies 15 years of full-time education.
  • Hands-on Python development; knowledge of APIs, distributed systems, testing, CI/CD, observability and secure software development. Experience delivering AI/ML or data products in banking, insurance, retail, healthcare, travel, logistics or telecom.
  • Hands-on experience with Snowflake Cortex AI, Cortex Agents, Cortex Search, Cortex Analyst, Cortex AI/LLM Functions, Snowpark, Streamlit in Snowflake, Dynamic Tables, Tasks, Streams, Snowflake ML, RBAC, masking policies and observability. Understanding of RAG, tool calling, agent orchestration, prompts, embeddings, vector databases and evaluation metrics, alongside production AI security, governance, reliability, scalability and cost controls. Experience with Git, automated testing, infrastructure as code and agile client delivery.

Preferred

SnowPro Advanced Architect or Data Engineer certification or Snowflake ML exposure; Snowpark Python, semantic models, dbt, Native Apps, data sharing and performance tuning; LangChain, LangGraph, LlamaIndex, Haystack, MLflow, FastAPI, Docker or Kubernetes; and Responsible AI, model risk management, synthetic data, human-in-the-loop review, A/B testing or GenAI cost optimization.

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

Skills for this role

Large Language Models (LLMs)Generative AIAgentic AIRetrieval-Augmented Generation (RAG)Prompt EngineeringAgent OrchestrationEmbeddingsVector SearchLLM EvaluationPythonAPIsDistributed SystemsSnowflake Cortex AICortex AgentsCortex SearchCortex AnalystCortex AI FunctionsSnowparkStreamlitDynamic TablesSnowflake TasksSnowflake StreamsSnowflake MLRole-Based Access Control (RBAC)Data MaskingObservabilityPII DetectionPrompt-Injection DefensesCI/CDInfrastructure as Code

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

  • Build production components in Snowflake

    The posting emphasizes hands-on engineering of Cortex-powered applications, including Cortex Search, Cortex AI Functions, Snowpark and Streamlit. Prepare to explain how an architecture becomes tested, deployable components inside Snowflake.

  • Design and evaluate RAG and agent workflows

    The role covers ingestion, chunking, embeddings, retrieval, prompts, tools, orchestration and evaluation harnesses. Prepare to walk through design choices across that pipeline and how evaluation results inform changes.

  • Engineer security and governance into AI applications

    The posting calls for RBAC, masking, PII redaction, prompt-injection defenses, authorization, lineage and audit logging, including for regulated use cases. Prepare to show where these controls belong in an application design.

  • Lead maintainable client delivery

    The role combines coding and technical decisions with collaboration across architecture, data, product and security teams. It also calls for reusable patterns, integration specifications, runbooks and domain-aware design; prepare examples of those engineering outputs.

Likely challenges to think through

  • Balance answer quality against operating cost

    Preparation hypothesis: retrieval depth, agent steps and model calls may improve results while increasing latency and cost. Prepare to discuss evaluation metrics and how you would use them alongside performance and cost controls named in the posting.

  • Keep agent capabilities within security boundaries

    Preparation hypothesis: tool use and access to enterprise content can create tension between useful workflows and privacy or authorization controls. Prepare to reason through permission checks, PII handling, injection defenses and auditability at each step.

  • Reuse patterns without ignoring domain constraints

    Preparation hypothesis: components built for different client domains may need different data handling, controls and adoption choices. Prepare to explain what you would standardize and what you would adapt after working with domain and security stakeholders.

03

Practice your answers

Technical practice

How would you turn an LLM architecture into a production application inside Snowflake?

What to coverInferred preparation suggestion: Walk through component boundaries, model invocation, Cortex AI capabilities, Snowpark integration and how data remains within the intended security perimeter. Explain the trade-offs you would document before implementation.

How would you prepare structured and unstructured enterprise content for RAG?

What to coverInferred preparation suggestion: Cover ingestion, parsing, chunking, enrichment and embeddings, including how content changes reach the retrieval index. Explain how you would choose chunk boundaries and handle incomplete or inconsistent source data.

How would you design and troubleshoot retrieval with Cortex Search?

What to coverInferred preparation suggestion: Describe indexing, vector search and retrieval choices, then distinguish a retrieval failure from a generation failure. Discuss how you would inspect results and adjust the pipeline without assuming that a prompt change fixes poor retrieval.

How would you evaluate an LLM application before and after release?

What to coverInferred preparation suggestion: Propose an evaluation harness that tests answer quality, grounding and relevant safety outcomes against representative cases. Explain how evaluation results and monitoring would guide changes to prompts, retrieval or model integration.

How would you design a multi-agent workflow with tools and memory?

What to coverInferred preparation suggestion: Explain when agent orchestration and tool calling add value over a simpler flow, and how you would manage context and state. Address tool permissions, failure handling and tests for unintended actions.

How would you integrate Cortex capabilities into a user-facing Snowflake application?

What to coverInferred preparation suggestion: Discuss appropriate roles for Cortex AI Functions, Cortex Analyst, Snowpark and Streamlit in Snowflake. Explain the interfaces and tests you would use to keep the components maintainable.

How would you defend a RAG or agent application against unsafe inputs and outputs?

What to coverInferred preparation suggestion: Cover prompt-injection defenses, PII detection and redaction, content filters and guardrails at relevant points in the flow. Explain how you would test the controls, including cases where retrieved content attempts to direct an agent.

How would you enforce governance for a regulated Snowflake use case?

What to coverInferred preparation suggestion: Explain how RBAC, masking, authentication, authorization, lineage and audit logging work together across data access and application actions. Discuss how you would verify that users and tools receive only permitted information.

How would you deliver and maintain these components through a software engineering workflow?

What to coverInferred preparation suggestion: Describe Python and API design, automated testing, Git-based review, CI/CD and infrastructure-as-code considerations. Include what a deployment runbook and integration specification should make clear to other engineers.

How would you diagnose a slow, costly or unreliable production LLM workflow?

What to coverInferred preparation suggestion: Trace the request across ingestion freshness, retrieval, model calls and application components using observability data. Explain the performance, reliability and cost trade-offs you would evaluate before changing the design.

Behavioural practice

When have you led a technical design into working components?

What to coverInferred preparation suggestion: Use a real situation to explain your engineering responsibilities, the decisions you made and the code or design artifacts you contributed. Close with the result and what evidence showed the components were ready for use.

When have you resolved competing priorities across technical and security stakeholders?

What to coverInferred preparation suggestion: Describe the situation, the concerns raised by architects, data engineers, product owners or security stakeholders, and your actions to reach a decision. State the result without presenting a hypothetical agreement as a personal achievement.

When have industry constraints changed an AI or data-product design?

What to coverInferred preparation suggestion: Choose a real example involving domain data, process constraints, controls or adoption risks. Explain what you changed and the resulting effect; the posting names several industries but does not require an example from any particular one.

When have you investigated a production quality or reliability problem?

What to coverInferred preparation suggestion: Set out the symptoms, how you used tests or monitoring to narrow the cause, and the corrective action you took. Finish with the observed result and any follow-up that reduced recurrence.

When have you made an engineering approach reusable for others?

What to coverInferred preparation suggestion: Describe the situation, your actions to create a pattern, component design or runbook, and how you worked with others to make it usable. Give the actual result, including any limits or lessons learned.

02

Sharpen your knowledge

Topics to prepare

  • RAG architecture and retrieval quality

    Draw the path from enterprise documents through parsing, chunking, embeddings and vector search to a cited answer. Explain how you would test retrieval separately from answer generation. The posting explicitly calls for RAG pipelines and retrieval over structured and unstructured content.

  • Agent orchestration and context handling

    Diagram a tool-calling workflow with agent responsibilities, context and memory boundaries, and failure paths. Explain when a direct model call would be simpler. The role includes prompts, tools, agents, orchestration flows and multi-agent workflows.

  • Snowflake LLM architecture

    Map Cortex Search, Cortex AI Functions, Cortex Agents and Cortex Analyst to their possible roles in an application; then explain where Snowpark, Streamlit, Dynamic Tables, Tasks and Streams fit. The posting requires hands-on experience with these Snowflake capabilities.

  • Security, privacy and governance

    Threat-model a regulated document assistant: trace PII exposure, prompt injection and unauthorized retrieval, then identify controls and audit evidence for each risk. The posting names RBAC, masking, guardrails, authentication, authorization, lineage and audit logging.

  • Production evaluation and operations

    Draft an evaluation plan covering retrieval quality, answer quality, safety, latency and cost, with monitoring and regression checks after a change. The posting requires evaluation metrics, observability, reliability, scalability and cost controls.

Skills to revise

  • Build a Python retrieval pipeline

    Using a small sample of structured and unstructured content, implement parsing, chunking and enrichment, then prepare embeddings and retrieval queries for Cortex Search. This rehearses the Python, ingestion and RAG implementation work explicitly described.

  • Integrate a Snowflake application

    Prototype, or write a concrete implementation plan for, a Snowpark and Streamlit flow that invokes Cortex AI Functions and presents retrieved evidence. Identify where Cortex Agents or Cortex Analyst would be used rather than adding them without purpose. These integrations are named in the required skills and responsibilities.

  • Implement controlled tool calling

    Write a small Python agent flow with a defined tool interface, context limits, error handling and a test for an unsafe or failed tool response. The role calls for hands-on agents, tool calling, orchestration and maintainable components.

  • Apply data-access and safety controls

    Implement or work through a test case for RBAC, masking and PII redaction; include a prompt-injection attempt and verify that unauthorized content is neither retrieved nor returned. The posting specifically requires these production controls.

  • Test and deliver an observable component

    Create unit and integration tests for one RAG component, add an evaluation regression check, and outline its Git-based CI/CD steps, logs and deployment runbook. The role requires automated testing, observability, CI/CD and engineering documentation.

04

Your preparation checklist

  • Map the stated requirements to evidence

    The posting specifies a minimum of 7.5 years, 15 years of full-time education, a relevant bachelor’s degree, Python, Snowflake and client-facing delivery. Prepare a factual evidence sheet for requirements you can document; leave gaps unclaimed.

  • Prepare a production project walkthrough

    Select a real AI/ML or data product from one of the listed industries, if available. Summarize the problem, your hands-on contributions, architecture, controls, deployment and measured results; distinguish your work from the team’s.

  • Sketch a Snowflake-based LLM design

    As interview practice, draw a RAG or agent workflow covering ingestion, parsing, chunking, embeddings, Cortex Search, Cortex AI Functions, tool calls and evaluation. Show where Snowpark or Streamlit fits, and label any design choices as proposals rather than job facts.

  • Rehearse security and governance trade-offs

    The role calls for RBAC, masking, lineage, PII controls, prompt-injection defenses and audit logging. Prepare a threat-and-control table explaining where each applies in the proposed design and how you would test it.

  • Define an evaluation and operations plan

    Draft a small evaluation matrix for retrieval, answer quality and agent behavior, including test cases and failure thresholds you would propose. Add monitoring, reliability, scalability and cost considerations; the posting names these concerns but prescribes no specific targets.

  • Show how you turn designs into maintainable components

    Prepare a concise example of a Python API or component design with automated tests, Git/CI/CD steps, observability, an integration specification and a deployment runbook. Use actual artifacts where available; otherwise present a clearly labeled sample.

  • Write questions for the employer

    Ask which Snowflake capabilities are in use, what enterprise data and controls shape the first engagement, how evaluation and production readiness are decided, and how the architect works with data engineers, product owners and security stakeholders.

AI-generated from the job information · Prepared Sep 29, 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…