New opportunity

AI Engineer – Agentic AI & Cloud Discovery

PRAGMATIKE · Bengaluru, India

About this role

PRAGMATIKE is recruiting for a global enterprise cybersecurity company building products to secure AI agents, LLM-powered applications, and the data they access. Two AI Engineer openings in India will turn LLM and machine learning approaches into production-grade security capabilities. The role is remote-first, full-time, with a stated November 2026 start date.

Workstreams:

  • Agentic AI Forensics: Convert agent traces, prompts, tool calls, and security events into structured, explainable findings for security analysts using LLM reasoning, RAG, extraction, and evaluation.
  • Cloud Discovery: Classify cloud resources and workloads to identify AI agents, model endpoints, and AI-enabled applications, and infer their purpose and security risk at scale.

Responsibilities

  • Design LLM-powered analysis and classification pipelines, prototype prompting, RAG, extraction, and ML classifiers in Python, and deploy production services in Go that meet defined accuracy targets.
  • Build ground-truth datasets, evaluation metrics, and regression suites; monitor production model quality and drift and address degradation.
  • Work with security researchers to translate attack patterns and risk signals into detection and summarization logic. Integrate results with event, storage, and UI layers for security teams. Use AI-assisted development for implementation, testing, debugging, and experimentation.

Requirements

  • 4+ years of software engineering experience, including 2+ years shipping LLM- or ML-backed features to production. Strong Go and Python skills; hands-on experience with LLM APIs, prompt engineering, structured outputs, RAG, and LLM/ML evaluation.
  • Understanding of AI agent architectures, tool calling, MCP or similar protocols, multi-step planning, and common failure modes. Experience deploying with Docker, Kubernetes, and AWS, GCP, or Azure.
  • Fluent English, strong communication, independent ownership in a distributed team, and comfort using AI coding assistants such as Claude Code, Cursor, GitHub Copilot, or Codex; use of these tools is a must-have. Candidates will be asked how they use and validate AI in development during interviews.

Preferred

Security analytics, SIEM/SOAR, digital forensics, cybersecurity or trust and safety; cloud APIs, IAM, and resource inventory; vector databases, embeddings, model fine-tuning, AI application tracing, OpenTelemetry-style observability, or introducing AI-assisted development workflows across teams.

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

Skills for this role

GoPythonLLM APIsPrompt engineeringRAGStructured extractionMachine learning classificationLLM evaluationRegression testingAI agent architecturesTool callingMCPDockerKubernetesAWSGCPAzureClaude CodeCursorGitHub CopilotCodexSecurity analyticsSIEMSOARDigital forensicsCloud provider APIsIAMVector databasesEmbedding pipelinesModel fine-tuning

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

  • Deliver the assigned security workstream

    The role joins either Agentic AI Forensics, turning agent traces and security events into explainable findings, or Cloud Discovery, classifying cloud resources to identify AI systems and infer risk. Prepare to explain an approach to the relevant workstream without assuming responsibility for both.

  • Move AI prototypes into production

    The posting calls for Python experimentation with prompting, RAG, extraction, and classifiers, followed by production Go services that meet defined accuracy targets. Prepare an example of how an approach was tested, hardened, and deployed.

  • Measure and maintain model quality

    The role includes ground-truth datasets, evaluation metrics, regression suites, and production monitoring for drift and degradation. Prepare to discuss how evaluation results inform changes after release.

  • Make results actionable for security teams

    The engineer will work with security researchers to translate attack patterns and risk signals into detection and summarization logic, then integrate results with event, storage, and UI layers. Prepare to explain how findings remain useful and understandable to analysts.

  • Use AI-assisted development with independent ownership

    AI coding assistants are a stated must-have, and the posting says interviews will cover their use and output validation. The role also calls for independent work in a remote-first team. Prepare a specific development example that distinguishes AI-generated work from your own checks and decisions.

Likely challenges to think through

  • Useful findings without overstating evidence

    Preparation hypothesis for the forensics workstream: LLM reasoning over prompts, tool calls, and events may produce plausible summaries that exceed what the traces support. Prepare to discuss evidence-linked extraction, human review, and evaluation of finding accuracy versus analyst usefulness.

  • Classifying incomplete cloud signals at scale

    Preparation hypothesis for the discovery workstream: resource inventories may not clearly reveal whether a workload is an AI agent or what risk it presents. Prepare to discuss how to handle uncertainty while balancing classification coverage, false positives, and processing at scale.

  • Fast experimentation versus dependable releases

    Preparation hypothesis across both workstreams: Python prototypes and AI-assisted coding can accelerate iteration, while Go services and security-facing outputs need reliable behavior. Prepare to explain how regression tests, accuracy measures, deployment checks, and production monitoring would guide that transition.

03

Practice your answers

Technical practice

How would you turn agent traces, prompts, tool calls, and security events into explainable findings?

What to coverThe Agentic AI Forensics workstream calls for structured findings that security analysts can use. Suggested answer focus: describe how you would link evidence to a finding, use prompting, RAG, and structured extraction where useful, and check for unsupported conclusions.

How would you classify cloud resources to discover AI agents and model endpoints at scale?

What to coverThe Cloud Discovery workstream includes identifying AI-enabled workloads and inferring their purpose and security risk. Suggested answer focus: discuss available resource signals, classification uncertainty, and when to use rules, ML, or LLM-based classification.

What failure modes would you examine in a multi-step agent that calls tools?

What to coverThe posting names agent architectures, tool calling, MCP or similar protocols, and common failure modes. Suggested answer focus: trace decisions across steps and distinguish erroneous planning, unsafe tool use, and unreliable tool outputs.

How would you evaluate an LLM-powered security finding or cloud classification pipeline?

What to coverThe role calls for ground-truth datasets, accuracy targets, human review, and regression suites. Suggested answer focus: explain labeling criteria, metrics for consequential errors, and tests that catch regressions across different cases.

How would you detect and investigate declining model quality after deployment?

What to coverMonitoring production quality and drift, then addressing degradation, is an explicit responsibility. Suggested answer focus: compare current outputs with baselines and reviewed examples, investigate changes in inputs or dependencies, and decide when to revise or roll back an approach.

How would you move a Python LLM/ML prototype into a production Go service?

What to coverThe posting pairs Python experimentation and data pipelines with Go production services. Suggested answer focus: explain how you would preserve evaluated behavior while addressing service reliability, API boundaries, testing, and operational trade-offs.

How would you deploy and operate one of these services in a cloud-native environment?

What to coverThe requirements name Docker, Kubernetes, and experience with AWS, GCP, or Azure. Suggested answer focus: discuss packaging, configuration, scaling, and observability choices without assuming a particular cloud provider or architecture.

How would you translate a security researcher's attack pattern into detection and summarization logic?

What to coverThe role explicitly involves working with security researchers on attack patterns and risk signals. Suggested answer focus: clarify the evidence and desired analyst conclusion, then test whether the resulting detection and summary remain accurate on ambiguous cases.

How would you integrate AI-generated results into event, storage, and UI layers?

What to coverThe posting calls for surfacing actionable results to security teams through those layers. Suggested answer focus: describe the result fields, evidence links, uncertainty, and failure handling needed to make a finding usable and reviewable.

How would you use and validate an AI coding assistant during development?

What to coverThe posting requires AI-assisted development and says candidates will be asked about their real-world use and validation of it. Suggested answer focus: distinguish suitable implementation, test, or debugging tasks from work needing closer review, and explain how you verify generated output.

Behavioural practice

Tell me about a time you owned a technical workstream with limited day-to-day direction.

What to coverThe role emphasizes independent ownership in a remote-first, distributed team. Suggested answer focus: use situation, action, and result to show how you set priorities, communicated decisions, and resolved a blocker.

Describe a time you worked with a domain expert to turn an ambiguous signal into a usable feature.

What to coverThe posting describes collaboration with security researchers on detection and summarization logic. Suggested answer focus: give the situation, your actions to clarify the signal and test interpretations, and the resulting change to the feature or shared understanding.

Tell me about a time you found that a shipped ML or LLM feature was underperforming.

What to coverProduction quality monitoring and addressing degradation are stated responsibilities. Suggested answer focus: describe the situation, how you investigated and communicated the issue, what action you took, and the measured result.

Describe a time you had to choose between a promising prototype and a more dependable production approach.

What to coverThe role spans rapid Python experimentation and reliable Go production services. Suggested answer focus: explain the situation, the trade-offs and evidence behind your decision, your actions, and the outcome.

Tell me about a time you made a complex technical result understandable to its users.

What to coverThe forensics workstream aims to deliver explainable, actionable findings for security analysts. Suggested answer focus: use situation, action, and result to show how you handled evidence, uncertainty, and user feedback without overstating the result.

02

Sharpen your knowledge

Topics to prepare

  • Agent architectures and failure modes

    Posting: The role requires understanding tool calling, MCP or similar protocols, multi-step planning, and common failure modes. Revise by diagramming an agent run with tool calls and identifying where incorrect tool use or misleading outputs could arise.

  • Agentic AI forensics

    Posting: One workstream turns traces, prompts, tool calls, and security events into explainable findings. Revise by outlining how those inputs could support a finding, what evidence an analyst would need to see, and what would remain uncertain.

  • Cloud discovery classification

    Posting: The other workstream classifies resources and workloads to identify agents, model endpoints, and AI-enabled applications, then infer purpose and risk. Revise by defining possible labels and ambiguous cases. Cloud APIs and IAM are listed as nice-to-have knowledge, not requirements.

  • LLM analysis approaches

    Posting: Prompting, structured outputs, RAG, and ML classifiers are used across the work. Revise by comparing when retrieval, extraction, or classification would fit each workstream, and how you would check whether an output is supported by its inputs.

  • Evaluation and production quality

    Posting: The role calls for ground truth, accuracy targets, offline evaluation, regression suites, and monitoring for drift. Revise by sketching an evaluation plan with labeled examples, error categories, human review, and a response to worsening production results.

  • Production and integration design

    Posting: Python prototypes become Go services deployed with Docker, Kubernetes, and AWS, GCP, or Azure; results connect to event, storage, and UI layers. Revise by drawing that path and identifying where outputs and quality checks belong.

Skills to revise

  • Prototype an analysis pipeline in Python

    Posting: Python is used for experimentation and data pipelines, including LLM APIs, prompting, RAG, and structured extraction. Practice turning a small set of sample agent events into structured findings, recording the prompt, retrieved context, output, and extraction errors.

  • Implement a Go service boundary

    Posting: LLM-powered pipelines are productionized as Go backend services. Practice a small Go handler that accepts an analysis request, validates a structured result, and returns an error when the result is unusable; this is a preparation exercise, not a stated project.

  • Build an evaluation and regression set

    Posting: Engineers define ground-truth datasets, metrics, and regression suites. Practice labeling a small set of classification or finding examples, measuring accuracy by error type, and rerunning the set after a prompt or classifier change.

  • Rehearse cloud-native deployment

    Posting: Docker, Kubernetes, and experience with AWS, GCP, or Azure are required. Practice containerizing a small Go service and explaining a Kubernetes deployment on one of the listed cloud platforms; do not treat all three providers as required.

  • Validate AI-assisted development

    Posting: Use of an AI coding assistant is a must-have, and interviewers ask how outputs are validated. Practice using one of the listed assistants, or a similar tool, for a bounded implementation or debugging task; inspect its changes, run tests, and note what you corrected.

  • Translate risk signals into analyst output

    Posting: The role works with security researchers on detection and summarization logic and surfaces results to security teams. As a preparation exercise, take a sample attack pattern, define its observable signals, and draft an evidence-backed finding with explicit uncertainty.

04

Your preparation checklist

  • Prepare a production project walkthrough

    The posting asks for production LLM/ML experience, Go services, and Python pipelines. Prepare one relevant example showing your role, prototype-to-release decisions, measured quality, deployment, and what changed after launch; use only work you actually did.

  • Sketch an agent-forensics design

    As a preparation exercise for one advertised workstream, diagram how traces, prompts, tool calls, and security events could become structured, explainable analyst findings. Note where RAG, extraction, tool-calling context, and human review would fit.

  • Sketch a cloud-discovery design

    For the other advertised workstream, outline how to classify resources and workloads as agents, model endpoints, or AI-enabled applications at scale. Explain what evidence would support a purpose or risk inference; treat cloud APIs and IAM depth as preferred, not required.

  • Build an evaluation plan

    The role calls for ground-truth datasets, accuracy targets, regression suites, and drift monitoring. Prepare a sample labeling rubric, metrics, failure-case tests, and a response plan for degraded quality without inventing the employer’s target values.

  • Explain the path to a production service

    Draw a proposed Python-to-Go handoff with LLM API and structured-output handling, event and storage integration, and results for a security UI. Be ready to discuss deployment and operational trade-offs using Docker, Kubernetes, and a cloud provider.

  • Document how you validate AI-assisted coding

    The posting explicitly says interviews cover AI coding tools and validation. Prepare a real example naming the tool used, the task, the tests or review applied to its output, and where you rejected or revised a suggestion.

  • Write questions for the employer

    Ask which workstream this opening serves, how security researchers define findings or risk signals, what ground truth and accuracy targets exist, and how model-quality issues are surfaced to the team.

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…