New opportunity

AI Research Internship

AryaXAI · Bangalore, India

About this role

AryaXAI advertises a full-time, six-month AI research internship with Lexsi Labs, with a rolling start date and potential extension or full-time offer. The posting lists Bangalore and remote work; applicants must be located in India. Interns collaborate with research and engineering teams on one of several frontier AI research areas focused on alignment, interpretability, safety or tabular foundation models.

Responsibilities

  • Depending on the assigned area, develop open-source Python tooling for alignment, explainability, uncertainty quantification, robustness and machine unlearning; investigate model behavior across text, image and tabular data using explainability or mechanistic-interpretability methods.
  • Alternatively, develop and benchmark uncertainty and robustness methods; improve tabular foundation model architectures and the TabTune library; or explore reinforcement-learning algorithms and RL fine-tuning tooling.
  • Write and maintain experiment code, conduct systematic studies, and contribute to whitepapers or conference submissions.

Required qualifications

  • Strong Python skills and the ability to write clean, modular, testable code; deep understanding of machine learning and deep learning with hands-on PyTorch experience.
  • Knowledge of transformer fundamentals, including attention, positional encodings, tokenization and training objectives in architectures such as BERT, GPT, LLaMA, T5, mixture-of-experts models and Mamba.
  • Experience with Git workflows, packaging, documentation, CI/CD and collaborative development; strong communication, peer-review and teamwork skills. No minimum years of experience or education requirement is stated.

Preferred qualifications

  • Expertise in at least one relevant area: explainability methods; circuit analysis and activation patching; Bayesian uncertainty estimation, ensembles or test-time augmentation; quantization and pruning; LLM alignment, prompting, RLHF and reward modeling; tabular foundation models such as Orion, TabPFN or TabICL; or fine-tuning methods including LoRA, adapters, instruction tuning and knowledge distillation.
  • Publications or equivalent research experience, open-source AI/ML contributions, exposure to risk-sensitive fields such as finance or healthcare, and familiarity with large-scale training infrastructure are additional advantages.

The posting offers a competitive stipend without stating an amount, access to GPUs and cloud credits, and opportunities for research authorship.

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

Skills for this role

PythonMachine LearningDeep LearningPyTorchTransformer ArchitecturesAttention MechanismsTokenizationBERTGPTLLaMAT5Mixture of ExpertsMambaGitCI/CDTechnical DocumentationCode ReviewResearch CommunicationAI AlignmentExplainable AIMechanistic InterpretabilityUncertainty QuantificationModel RobustnessMachine UnlearningSHAPLIMEIntegrated GradientsLayer-wise Relevance PropagationGrad-CAMActivation Patching ஃ code review maybe okay

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

  • Contribute deeply to one research area

    The posting says interns work on one of several areas, including interpretability, uncertainty and robustness, tabular foundation models, or reinforcement learning. Prepare to explain a focused research approach in one relevant area rather than claiming breadth across all tracks.

  • Run systematic experiments

    Interns maintain experiment code, conduct systematic studies, and may contribute to whitepapers or conference submissions. Prepare to explain how to choose baselines, record results, and distinguish evidence from a promising observation.

  • Build maintainable research tooling

    The role includes open-source Python tooling or library work, and requires clean, modular, testable code, PyTorch, Git workflows, packaging, and documentation. Prepare an example of turning an experiment into code others can review and reuse.

  • Connect model fundamentals to the assigned work

    The posting requires deep ML and deep-learning understanding and knowledge of transformer attention, positional encodings, tokenization, and training objectives. Prepare to explain how relevant model choices affect the methods and measurements in a chosen track.

Likely challenges to think through

  • Choosing depth from a broad remit

    A likely preparation challenge is deciding where to go deep when the advertised tracks differ substantially and an intern works on only one. Select one track for detailed discussion, while being ready to explain how its methods differ from adjacent tracks.

  • Balancing research iteration with reusable code

    The duties combine exploratory studies with maintained experiments and open-source tooling. A plausible trade-off is moving quickly without making results hard to reproduce or code hard to review. Prepare an example of using tests, documentation, and recorded experiment settings without slowing every iteration.

  • Supporting trust claims with evidence

    If assigned to explainability, mechanistic interpretability, uncertainty, or robustness, useful-looking outputs may not establish that a method reliably identifies behavior or risk. Prepare to discuss controls, baselines, failure cases, and limits on conclusions; this is a research challenge inferred from the listed duties, not a confirmed problem at Lexsi Labs.

03

Practice your answers

Technical practice

How would you structure an open-source Python library for model analysis so others can extend and test it?

What to coverPreparation suggestion: Discuss modular interfaces, tests for numerical behavior and edge cases, and documentation with reproducible examples. Explain how packaging, Git reviews, and CI checks would help collaborators maintain the library.

How would you diagnose a PyTorch model whose training loss falls but validation performance deteriorates?

What to coverPreparation suggestion: Distinguish overfitting from data leakage or evaluation errors using learning curves, split checks, and a verified evaluation mode. Explain which controlled change you would test first and what result would support your diagnosis.

How do attention, positional information, tokenization, and training objectives shape transformer behavior?

What to coverPreparation suggestion: Explain each component and compare, for example, masked-language modeling in BERT with autoregressive prediction in GPT-style models. Discuss how those choices affect an experiment or interpretation of its results.

How would you evaluate an explanation method across text, image, and tabular models?

What to coverPreparation suggestion: Choose relevant methods named in the posting, such as SHAP, integrated gradients, or Grad-CAM, and explain where each is applicable. Discuss faithfulness checks, sensitivity to baselines or perturbations, and why a plausible-looking explanation is not proof of causality.

How would you use activation patching to investigate a model failure?

What to coverPreparation suggestion: Describe a controlled pair of inputs, the activation intervention, and a measurable change in output. Address confounding effects and what additional tests would be needed before claiming a circuit explains the behavior.

How would you benchmark uncertainty estimates alongside model robustness?

What to coverPreparation suggestion: Compare a stated approach such as an ensemble, Bayesian method, or test-time augmentation against an appropriate baseline. Discuss calibration, performance under distribution shift, computational cost, and how you would avoid drawing conclusions from a single metric.

If assigned to tabular foundation models or TabTune, how would you test whether a proposed improvement helps?

What to coverPreparation suggestion: Define representative tabular tasks, strong baselines, consistent splits, and an ablation of the proposed change. Discuss predictive performance alongside runtime or resource use, without assuming a particular architecture or dataset is required.

If assigned to RL fine-tuning for alignment, how would you evaluate a proposed algorithmic change?

What to coverPreparation suggestion: State the objective, baseline, and observable measures of desired behavior, then describe controlled comparisons and failure checks. Discuss reward misspecification and the trade-off between apparent gains and training cost.

When would you choose LoRA or adapters rather than full-model fine-tuning?

What to coverPreparation suggestion: Compare trainable parameters, memory, adaptation flexibility, and possible quality differences. Explain how you would evaluate the choice for an instruction-tuning or domain-specialization task; these are preferred areas, not duties guaranteed for every intern.

How would you design a systematic study that could support a research paper or technical report?

What to coverPreparation suggestion: Define a falsifiable question, baselines, ablations, metrics, and a reproducible experiment record. Explain how you would handle negative results and separate observations from claims the evidence does not support.

Behavioural practice

Tell me about a time you collaborated across research and engineering on a technical problem.

What to coverPreparation suggestion: Use a real situation, your specific coordination or implementation actions, and the result. Show how you reconciled research goals with engineering constraints rather than claiming sole ownership of a team outcome.

Describe a time a code review changed your approach.

What to coverPreparation suggestion: Give the situation, the feedback received, the action you took, and the result. Focus on how the change improved correctness, testability, or maintainability.

Tell me about a study whose results did not support your initial hypothesis.

What to coverPreparation suggestion: Explain the question, how you checked the experiment and investigated alternatives, and what you concluded. Include how you communicated uncertainty or negative findings to others.

Describe a time you explained a complex ML result to collaborators with different technical backgrounds.

What to coverPreparation suggestion: Identify the audience and decision at stake, the explanation or written material you produced, and the result. Show how you distinguished evidence, limitations, and open questions.

Tell me about a time you took initiative on an ambiguous technical task.

What to coverPreparation suggestion: Describe the ambiguity, how you set a tractable scope or sought input, what you did, and the result. Relate your example to reliable progress without implying a particular Lexsi Labs workflow.

02

Sharpen your knowledge

Topics to prepare

  • Machine learning and deep learning foundations

    Required: Review optimization, generalization, overfitting and evaluation. Exercise: explain how you would distinguish a genuine model improvement from data leakage or a weak baseline; the posting asks for deep ML/DL understanding and systematic studies.

  • Transformer fundamentals

    Required: Sketch attention, positional encodings and tokenization, then compare the training objectives of BERT, GPT and T5. Be ready to discuss how LLaMA, mixture-of-experts models and Mamba differ where relevant; the posting explicitly names these architectures.

  • Research study design

    Role responsibility: Plan a small study with a baseline, controlled comparisons, metrics and a failure analysis. Explain what evidence would support a claim suitable for a whitepaper or conference submission.

  • One relevant research specialization

    Preferred, not a requirement to master every area: Choose one posting-listed direction—such as explainability or mechanistic interpretability, uncertainty and robustness, tabular foundation models, or alignment and RL—and explain a representative method, its assumptions, a comparison baseline and a likely failure mode. Interns work on one assigned area.

Skills to revise

  • Modular Python and tests

    Required: Refactor a small experiment into reusable functions and add tests for data shapes and edge cases. This mirrors the stated need for clean, modular, testable Python and open-source tooling.

  • PyTorch experimentation

    Required: Implement a small training and evaluation loop, record configurations and results, and diagnose one training failure. The posting requires hands-on PyTorch and maintained experiment code.

  • Git and library maintenance

    Required: Practice a focused Git change with a test, package metadata, usage documentation and a CI check; write a brief code-review response. These reflect the posting’s Git, packaging, documentation, CI/CD and peer-review requirements.

  • Method implementation in a chosen area

    Suggested preparation for a preferred specialty: Implement and compare one named method—for example, SHAP for explainability, activation patching for interpretability, or an ensemble for uncertainty—against a simple baseline. State what the result does and does not show; these are possible research areas, not tasks every intern will perform.

  • Research communication

    Required collaboration and research contribution: Write a one-page experiment summary covering the question, method, results, limitations and next test, then practice explaining it to both a researcher and an engineer.

04

Your preparation checklist

  • Choose a research focus

    The posting says interns work on one of several areas and that expertise in any one preferred domain is useful. Prepare a short explanation of which area interests you, the question you would investigate, and why.

  • Prepare a project walkthrough

    The role involves experiment code and systematic studies. Select a real project, if available, and prepare a walkthrough of its problem, PyTorch implementation, baselines, metrics, results, limitations, and your contribution.

  • Build a small, testable example

    The posting requires clean, modular Python and cites Git, packaging, documentation, and CI/CD. As preparation, make a compact example in your chosen area with tests, a README, and a reproducible run command.

  • Rehearse transformer fundamentals

    The posting names attention, positional encodings, tokenization, and training objectives. Prepare a one-page explanation comparing how these appear in two named model families, such as BERT and GPT, with a small PyTorch example you can explain.

  • Work through a research design exercise

    For your chosen area, draft a proposed experiment with a hypothesis, dataset or model choice, baseline, evaluation metric, and likely failure mode. This is interview preparation, not a stated assignment.

  • Prepare to discuss collaboration and findings

    The role includes peer review, teamwork, and possible whitepapers or submissions. Identify a real example of feedback you gave or received, and prepare a brief summary of how you would report inconclusive results.

  • Draft application answers and employer questions

    The application asks about a problem you solved, preferred research area, and comfortable data modalities. Draft concise, truthful answers; then ask how an intern’s area is selected, what a six-month project is expected to produce, and how research and engineering teams collaborate.

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…