New opportunity

AI Engineer

AutoCash.ai · Bangalore, India

About this role

AutoCash.ai seeks a full-time AI Engineer in Bangalore to build and deploy AI systems for its cash-management platform. The role turns data from banks, ERPs and payment systems into real-time forecasting, anomaly detection and decision-support insights for CFOs and finance teams. The engineer will work with product, data and treasury experts and help build the company’s India engineering hub.

Responsibilities

  • Develop and deploy models for cash-flow forecasting, transaction categorization and financial anomaly detection; build pipelines to ingest and normalize financial data.
  • Fine-tune and optimize models, including LLMs, for production performance, latency and cost. Build RAG pipelines and agentic workflows that let finance teams query and act on financial data conversationally, and integrate models into the platform through APIs and services.
  • Monitor models for drift, degradation and reliability. Use statistical methods, A/B tests and forecasting-accuracy measures to validate results. Apply model CI/CD, versioning, testing and monitoring practices, and align outputs with finance-team workflows.

Requirements

A bachelor’s or master’s degree in computer science, AI, machine learning, mathematics, statistics or a related field; 2–5 years building and deploying ML or AI systems, ideally in fintech, SaaS or data-intensive domains; strong Python skills; and hands-on experience with frameworks such as PyTorch, TensorFlow or JAX. The posting also calls for experience with LLMs, prompt engineering, RAG or fine-tuning; vector databases and embedding-based retrieval; familiarity with AWS, GCP or Azure and Docker or Kubernetes; and software-engineering fundamentals including version control, testing and CI/CD. Strong analytical and communication skills are needed to connect model results to business outcomes and explain limitations to nontechnical stakeholders.

Preferred

Exposure to treasury, banking or financial-data systems, including TMS, ERPs or payment rails; MLOps tools such as MLflow, Kubeflow or Weights & Biases; agentic or tool-using AI applications; and time-series forecasting or financial anomaly detection. The posting offers a competitive salary and benefits package, without specifying an amount, and describes a high-ownership role working directly with the founders and collaborating with U.S.-based leadership.

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

Skills for this role

PythonPyTorchTensorFlowJAXMachine LearningLarge Language ModelsPrompt EngineeringRetrieval-Augmented GenerationModel Fine-TuningVector DatabasesEmbedding-Based RetrievalTime-Series ForecastingAnomaly DetectionData PipelinesAPIsAWSGCPAzureDockerKubernetesMLOpsMLflowKubeflowWeights & BiasesCI/CDModel MonitoringA/B TestingStatistical AnalysisVersion ControlAgentic Workflows

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

  • Financial data pipelines

    The role builds pipelines to ingest and normalize data from banks, ERPs, and payment systems. Prepare to explain how you would make those inputs usable for downstream models.

  • Core financial models

    The posting names cash-flow forecasting, transaction categorization, and anomaly detection. Prepare to discuss model choices, validation methods, and how outputs would support finance decisions.

  • Conversational financial AI

    The role includes RAG pipelines and agentic workflows that let finance teams query and act on financial data, with models integrated through APIs and services. Prepare to explain retrieval and tool-use design in that setting.

  • Production performance and reliability

    The engineer will optimize models, including LLMs, for latency and cost; monitor drift and degradation; and apply model testing, versioning, and CI/CD. Prepare to discuss how you would evaluate a model after deployment.

  • Finance-workflow alignment

    The role works with product, data, and treasury experts to make outputs useful to CFOs and finance teams. Prepare to explain model behavior, limitations, and business relevance in nontechnical terms.

Likely challenges to think through

  • Inconsistent source data

    Likely challenge, not a confirmed problem: differences among bank, ERP, and payment-system data could complicate normalization and forecasting. Prepare to discuss validation, reconciliation, and how you would handle missing or delayed records without obscuring uncertainty.

  • Accuracy versus production constraints

    Likely challenge: the stated high accuracy bar for financial data may conflict with real-time use, latency, and cost targets. Prepare to explain how you would compare forecasting accuracy and reliability against operating constraints, then monitor the chosen approach.

  • Useful actions versus trustworthy outputs

    Likely challenge: conversational queries and agentic workflows must be useful while model limitations remain clear to finance users. Prepare to discuss how you would evaluate retrieved answers and proposed actions, and communicate uncertainty before relying on them.

03

Practice your answers

Technical practice

How would you ingest and normalize data from banks, ERPs, and payment systems for cash-management models?

What to coverSuggested answer focus: Explain how you would reconcile different transaction formats, timestamps, currencies, and identifiers while preserving source lineage. Discuss validation and handling missing or duplicate records before the data reaches a model.

How would you build and evaluate a cash-flow forecasting model?

What to coverSuggested answer focus: Compare a simple baseline with a time-series or ML approach, using time-ordered validation to avoid leakage. Explain which forecasting-error measures you would report and how you would check whether errors matter to finance-team decisions.

How would you approach transaction categorization?

What to coverSuggested answer focus: Describe how you would define categories with treasury experts, prepare labeled data, and assess performance across categories rather than relying on overall accuracy alone. Discuss how you would handle ambiguous transactions and changing descriptions.

How would you detect financial anomalies without overwhelming users with alerts?

What to coverSuggested answer focus: Explain a plausible baseline or model, how you would evaluate rare events, and the trade-off between missed anomalies and false positives. Address how finance experts could review findings and help refine what counts as actionable.

How would you design retrieval for a conversational query over financial data?

What to coverSuggested answer focus: Describe how data would be represented, embedded, retrieved, and supplied to an LLM, including where a vector database fits. Discuss checking retrieved evidence and limiting answers when the available data does not support a conclusion.

What safeguards would you consider for an agentic workflow that can act on financial data?

What to coverSuggested answer focus: Distinguish answering a question from invoking a tool or taking an action. As a preparation suggestion, discuss validation, permissions, traceability, and when a finance user should confirm an action; the posting does not specify particular actions or controls.

When would you fine-tune an LLM rather than improve its prompts or retrieval?

What to coverSuggested answer focus: Compare the approaches using task performance, data availability, latency, and cost, then explain how you would test a change before production use. The posting calls for LLM optimization but does not prescribe a particular model or fine-tuning method.

How would you serve an ML model through a reliable platform API?

What to coverSuggested answer focus: Cover input validation, versioned responses, latency, failure handling, and testing at the service boundary. As a preparation suggestion, explain how containers and a cloud platform could support deployment without assuming AutoCash.ai uses a specific provider.

How would you detect and respond to model drift or degradation after deployment?

What to coverSuggested answer focus: Distinguish changes in incoming financial data from changes in measured model quality, and identify signals you would monitor. Explain how versioning, tests, and model CI/CD could support investigation and a safe update or rollback.

How would you test whether a model improvement helps a finance workflow?

What to coverSuggested answer focus: Explain how you would choose outcome measures with product and treasury experts, apply an appropriate statistical comparison or A/B test, and interpret uncertainty. Distinguish an improvement in an offline model metric from an improvement in a CFO or finance-team decision.

Behavioural practice

Tell me about a time you worked with domain experts to make a model output more useful.

What to coverSuggested answer focus: Use a real situation, the questions you asked and changes you made, and the observed result. Connect the example to the role’s collaboration with product and treasury experts without claiming finance-domain experience you do not have.

Describe a time you explained a model’s limitations to a nontechnical stakeholder.

What to coverSuggested answer focus: State the decision at stake, how you communicated uncertainty or failure cases, and what happened next. Show how you made the explanation useful without overstating model reliability.

Tell me about a time you investigated a deployed system that was producing unreliable results.

What to coverSuggested answer focus: Describe the symptoms, your investigation and communication, and the outcome. If applicable, explain how monitoring or tests changed afterward; use an actual example rather than inventing a financial incident.

Describe a time you took ownership of an ambiguous engineering task.

What to coverSuggested answer focus: Explain the initial uncertainty, how you set priorities and sought input, and the result. This is suggested preparation for the posting’s high-ownership role and work helping build the India engineering hub, not a claim about a specific assigned project.

Tell me about a time you coordinated work across teams or locations.

What to coverSuggested answer focus: Give a real situation, the steps you took to align decisions and communicate progress, and the result. The role involves cross-functional work and collaboration with U.S.-based leadership, but no particular coordination process is specified.

02

Sharpen your knowledge

Topics to prepare

  • Financial-data meaning and cash workflows

    The role uses data from banks, ERPs and payment systems to support CFO and finance-team decisions; treasury-system exposure is preferred. Revision exercise: sketch how differently named transaction fields and timestamps would map to a common cash-flow record, and note which ambiguities need a treasury expert’s input.

  • Forecasting and anomaly evaluation

    The posting calls for cash-flow forecasting, financial anomaly detection and interpretation of forecasting accuracy; familiarity with these techniques is preferred. Revision exercise: explain how you would choose a time-based validation split, compare forecasts with a baseline and assess whether anomaly alerts are useful despite false positives.

  • LLM retrieval and tool-using workflows

    RAG pipelines, embedding-based retrieval and vector databases are specified; agentic workflows are part of the work. Revision exercise: diagram a finance question flowing through retrieval, answer generation and a proposed action, identifying where retrieved evidence or human confirmation would be needed. Those safeguards are preparation suggestions, not stated requirements.

  • Production model trade-offs

    The role includes fine-tuning and optimizing models, including LLMs, for performance, latency and cost, then monitoring drift and reliability. Revision exercise: compare two hypothetical model versions across accuracy, response time and cost, and explain what evidence would justify deployment or rollback.

  • Experiments and business interpretation

    The posting specifies statistical validation, A/B tests and explaining model limitations to finance and treasury stakeholders. Revision exercise: outline an experiment for a forecasting improvement, including the outcome measure, comparison and a plain-language explanation of what the result would not establish.

Skills to revise

  • Build a normalized financial-data pipeline

    Practice in Python with synthetic bank, ERP and payment records: parse inconsistent fields, normalize dates and amounts, flag missing values and test the output. This rehearses the stated pipeline responsibility without assuming access to company data.

  • Implement and test a financial ML baseline

    Using Python and one listed framework—PyTorch, TensorFlow or JAX—build a small forecasting, transaction-categorization or anomaly-detection prototype on synthetic data. Record a baseline and time-aware evaluation; these are models the role would develop and deploy.

  • Prototype embedding-based RAG

    Create a small synthetic finance-document set, index embeddings in a vector database and test whether retrieved passages support answers to finance questions. Add prompt tests for unsupported answers. This practices the specified retrieval, RAG and prompt-engineering experience.

  • Profile an LLM workflow

    On a small synthetic task, compare prompt or model configurations and record answer quality, latency and estimated cost. If using fine-tuning, compare it against an untuned baseline. This targets the stated production-optimization work; the exercise does not imply a particular model is used at AutoCash.ai.

  • Serve and package a model

    Expose a prototype through an API, add input-validation and response tests, then package it with Docker and outline a CI/CD check. APIs, testing, CI/CD and containerization appear in the posting; no particular cloud deployment is specified.

  • Monitor and explain results

    Set up a simple report of forecast error, input drift and service failures for a prototype, then write a short finance-facing explanation of its limitations. This rehearses the stated monitoring and communication responsibilities.

04

Your preparation checklist

  • Map the cash-management workflow

    Prepare a one-page diagram showing how bank, ERP and payment-system data could become cash forecasts, anomaly alerts and CFO-facing insights. Mark the design as a proposed approach, not AutoCash.ai’s existing architecture.

  • Prepare a relevant project walkthrough

    Select a past ML/AI deployment, if available, and summarize the problem, your contribution, Python and framework choices, deployment path, measured results and limitations. Be ready to explain how you would adapt the approach to financial data.

  • Practice a forecasting and anomaly-detection design

    Sketch a hypothetical pipeline for ingesting and normalizing transactions, categorizing them, forecasting cash flow and flagging anomalies. Include data-quality checks, forecasting-accuracy measures and an approach to validating alerts.

  • Outline a conversational finance feature

    Prepare a proposed RAG or tool-using workflow for querying financial data. Show where embeddings and retrieval fit, how APIs connect to the platform, and how you would test answer accuracy and control unsupported actions.

  • Assemble production-engineering evidence

    Gather concise examples, where available, of cloud and container use, version control, tests, model CI/CD, monitoring and model optimization. Explain how you measured or would measure drift, reliability, latency and cost.

  • Practice explaining trade-offs to finance stakeholders

    Prepare a short, plain-language explanation of one model result, its business relevance and its limitations. Include how you would use statistical validation or an A/B test to decide whether a change helps finance-team workflows.

  • Bring targeted questions for the team

    Ask which cash-management use cases take priority, what data-quality and accuracy challenges matter most, how product and treasury experts review outputs, and what the AI Engineer would own while the India engineering hub grows.

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…