New opportunity

Machine Learning

Globant · Hartford, United States

About this role

Globant seeks an AI / Machine Learning Engineer for its Machine Learning position in Hartford, CT. The full-time role supports AI and emerging-technology initiatives across business and technology teams, developing and prototyping solutions and helping move use cases from proof of concept toward production. The stated salary range is 82,000–110,000 annually; final compensation depends on the role, hiring location, skills, experience, and qualifications.

Responsibilities

  • Develop and prototype machine learning, Generative AI, and agentic AI solutions for business problems. Work with foundation models, LLMs, prompt engineering, fine-tuning, and multimodal AI.
  • Design RAG solutions using vector databases, memory, tool use, and function calling; support multi-agent workflows and autonomous AI capabilities.
  • Build applications and integrations with Python, ReactJS, and NodeJS. Conduct experiments, proofs of concept, testing, and model evaluation.
  • Partner with data, engineering, and business teams on production readiness. Support MLOps, AI Ops, deployment, monitoring, and CI/CD; promote AI governance, ethics, and bias mitigation. Explain technical concepts to technical and non-technical stakeholders.

Required qualifications

  • Bachelor's degree in Computer Science or another STEM field, or equivalent professional experience. Experience in AI/ML, Generative AI, or advanced analytics, with knowledge of machine learning fundamentals and model evaluation.
  • Hands-on experience with LLMs, OpenAI, prompt engineering, Python, ReactJS, and NodeJS. Familiarity with agentic frameworks such as LangChain, Strands, or CrewAI; experience with RAG, vector databases, tool/function calling, and agentic workflows.
  • Understanding of MLOps, AI Ops, and CI/CD; experience with Jenkins, GitHub, Claude, and Copilot. Strong analytical, problem-solving, and communication skills, with the ability to work in Agile, cross-functional teams.

Preferred qualifications

Experience with AWS Bedrock; exposure to Azure or GCP AI services; experience with multimodal AI, fine-tuning, and taking AI solutions from experimentation or proof of concept through production deployment. A comprehensive benefits package is mentioned, with details in the Globant Experience Guide.

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

Skills for this role

Machine LearningGenerative AILarge Language ModelsAgentic AIPythonReactJSNodeJSOpenAIPrompt EngineeringFine-tuningMultimodal AIRAGVector DatabasesLangChainStrandsCrewAITool CallingFunction CallingMulti-agent WorkflowsModel EvaluationMLOpsAI OpsCI/CDJenkinsGitHubClaudeCopilotAWS BedrockAzure AI ServicesGoogle Cloud Platform AI Services (GCP) AI services](https://example.com)

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

  • Business-focused AI prototypes

    The role develops AI/ML, generative AI, and agentic AI solutions for business problems. Testing and model evaluation are explicit duties, so prepare to explain how a proof of concept would be judged against a defined use case.

  • RAG and agentic solution design

    The posting calls for RAG, vector databases, memory, tool and function calling, and support for multi-agent workflows. Prepare to explain design choices and how each component contributes to the intended behavior.

  • Application development and integration

    The role builds applications and integrations with Python, ReactJS, and NodeJS. Be ready to describe how an AI capability connects to an application, rather than discussing models in isolation.

  • Progression toward production

    The role partners with data, engineering, and business teams to move use cases beyond proof of concept. Deployment, monitoring, CI/CD, MLOps, AI Ops, and responsible AI practices are stated responsibilities.

Likely challenges to think through

  • Fast experiments versus credible evaluation

    A likely difficulty is moving quickly on prototypes without mistaking a promising demonstration for a useful solution. Prepare an approach to defining success criteria, testing representative cases, and using evaluation results to decide what to refine.

  • Agent flexibility versus predictable behavior

    RAG and tool-using or multi-agent workflows can add capability while making outputs harder to trace and control. Prepare to discuss when a simpler workflow is sufficient and how to test retrieval quality, tool calls, and failure cases.

  • Prototype speed versus production safeguards

    Moving an AI use case toward deployment may require balancing iteration with monitoring, CI/CD, governance, ethics, and bias mitigation. Prepare to explain how you would work with business and engineering partners to identify those needs before release; this is a preparation hypothesis, not a reported Globant problem.

03

Practice your answers

Technical practice

How would you choose and evaluate an ML approach for a business problem?

What to coverSuggested answer focus: Define the objective, establish a baseline, and choose evaluation measures that reflect the intended use. Explain how you would detect overfitting and decide whether the result is useful enough to pursue.

How would you improve an LLM application through prompt engineering?

What to coverSuggested answer focus: Describe how you would structure instructions and examples, then test changes against representative inputs. Discuss how you would assess answer quality, consistency, and failure cases when working with models such as OpenAI or Claude.

When would you consider fine-tuning or multimodal AI instead of a prompt-only approach?

What to coverSuggested answer focus: Compare the problem each approach could address and the additional data, evaluation, and maintenance it may require. Fine-tuning and multimodal AI are listed in the posting; a practical decision framework is a suggested preparation topic, not a stated employer preference.

How would you design and troubleshoot a RAG solution?

What to coverSuggested answer focus: Walk through document preparation, retrieval from a vector database, and using retrieved context in a response. Explain how you would investigate irrelevant retrieval or answers unsupported by the retrieved material.

How would you control tool use and memory in an agentic workflow?

What to coverSuggested answer focus: Describe when function calling, memory, or multiple agents would help, and when a simpler workflow would suffice. Discuss how you would handle failed tool calls, limit unintended actions, and test the workflow; familiarity with frameworks such as LangChain, Strands, or CrewAI is stated in the posting.

How would you connect a Python AI service to a ReactJS and NodeJS application?

What to coverSuggested answer focus: Outline the responsibilities of each component and how requests, responses, and errors would move between them. Discuss trade-offs in keeping model-facing logic separate from the user interface and testing the integration.

How would you assess whether an AI proof of concept is ready to advance?

What to coverSuggested answer focus: Define test cases and success measures tied to the business problem, including examples where the solution fails. Explain what evidence you would share with data, engineering, and business partners before investing in production work.

What would you put in place to deploy and monitor an AI solution?

What to coverSuggested answer focus: Discuss CI/CD, repeatable testing, deployment checks, and monitoring of application and model behaviour. Relate GitHub and Jenkins to that workflow without assuming the posting specifies a particular pipeline design.

How would you evaluate governance and bias risks in a proposed AI use case?

What to coverSuggested answer focus: Identify who could be affected, what harmful or uneven outcomes to test for, and how you would document findings. Explain how evaluation and ongoing monitoring could inform mitigation rather than treating a successful prototype as sufficient.

How would you compare AI service options for a prototype moving toward production?

What to coverSuggested answer focus: Consider model capabilities, integration effort, evaluation results, and operational needs when comparing options. AWS Bedrock experience and exposure to Azure or GCP AI services are preferred, so platform-specific comparisons are a suggested preparation topic, not a stated requirement for every solution.

Behavioural practice

Tell me about a time you defined an AI or analytics problem with business and technical partners.

What to coverSuggested answer focus: Give the situation, your actions to clarify the problem and align the teams, and the result. Explain how you handled differing priorities or definitions of success.

Describe a time an experiment or proof of concept did not meet its goal.

What to coverSuggested answer focus: Set out the situation, how you investigated the result and decided what to change or stop, and what happened next. Use a real example rather than implying that every experiment led to deployment.

Tell me about a time you helped move a technical solution toward production.

What to coverSuggested answer focus: Describe the starting state, your specific work with engineering or data partners on testing and operational readiness, and the result. If the work stopped before deployment, be clear about what was completed and learned.

Give an example of explaining a complex technical concept to a non-technical stakeholder.

What to coverSuggested answer focus: Describe the audience and decision at stake, how you adapted your explanation, and the outcome. Show how you communicated limitations as well as potential value.

Describe a time you raised a risk in an AI or data-driven project.

What to coverSuggested answer focus: Explain the situation, the risk you identified, how you discussed it with others, and the result. Responsible AI, governance, and bias mitigation appear in the posting; using a real example of those issues is a suggested preparation approach if applicable.

02

Sharpen your knowledge

Topics to prepare

  • Machine learning fundamentals and evaluation

    Revision suggestion: For a hypothetical AI use case, define a baseline, evaluation measures, test cases and likely failure modes. The posting explicitly requires ML fundamentals, testing and model evaluation.

  • LLMs and prompt engineering

    Revision suggestion: Compare two prompt approaches for the same task and explain how you would judge their outputs. Hands-on LLM, OpenAI and prompt-engineering experience is required; fine-tuning and multimodal AI are also mentioned, with experience in those techniques preferred.

  • RAG architecture

    Revision suggestion: Sketch a retrieval-to-answer flow and explain where a vector database, memory and evaluation fit. The role explicitly involves designing RAG and vector-database solutions.

  • Agentic workflows

    Revision suggestion: Diagram a task that uses function calling and a multi-agent workflow, including when a tool should not be called. The posting requires experience with tool/function calling and agentic workflows and familiarity with frameworks such as LangChain, Strands or CrewAI.

  • Production readiness and responsible AI

    Revision suggestion: Outline what you would check before moving a proof of concept toward production, covering monitoring, CI/CD, governance and bias. These are stated responsibilities, alongside collaboration with data, engineering and business teams.

Skills to revise

  • Python and OpenAI prototyping

    Practice suggestion: Build a small Python LLM prototype using OpenAI, vary its prompts and record results against a few test cases. Python, OpenAI and hands-on LLM work are listed as required.

  • ReactJS and NodeJS integration

    Practice suggestion: Connect a simple ReactJS interface to a NodeJS component that sends a request to an AI prototype and displays its response. Both technologies are in the mandatory skillset, and the role develops applications and integrations.

  • RAG and tool-calling implementation

    Practice suggestion: Prototype retrieval with a vector database and add a clearly bounded tool/function call; test what happens when retrieval is irrelevant or the tool fails. The posting explicitly calls for implementing RAG, vector-database and tool-use solutions.

  • GitHub and Jenkins delivery

    Practice suggestion: Put a prototype in GitHub and configure a Jenkins job to run its tests; explain what you would monitor after deployment. Jenkins and GitHub experience is required, and the role supports CI/CD and monitoring.

  • Claude and Copilot use

    Practice suggestion: Use Claude to examine a prototype response and Copilot while revising a small code change, then independently verify both outputs. Experience with Claude and Copilot is listed in the required qualifications.

  • Cross-functional explanation

    Practice suggestion: Give two short explanations of the same prototype evaluation result—one for an engineering teammate and one for a business stakeholder. The role calls for communication across technical and non-technical audiences in Agile, cross-functional work.

04

Your preparation checklist

  • Prepare an AI project walkthrough

    Select a real AI/ML or Generative AI project, if available. Prepare a one-page account of the business problem, your contribution, model choices, experiments, evaluation results, and what reached proof of concept or production. These are central responsibilities in the posting.

  • Sketch a RAG and agentic design

    As a practice exercise, diagram document retrieval, a vector database, an LLM, memory, and tool/function calling for a business use case. Explain when an agentic or multi-agent workflow would help, and where you would limit its autonomy.

  • Demonstrate the stated development stack

    Prepare specific examples of work with Python, ReactJS, NodeJS, OpenAI/LLMs, Jenkins, GitHub, Claude, and Copilot where you have used them. Note your actual contribution and be ready to distinguish hands-on experience from familiarity.

  • Build an evaluation plan

    For the practice design, write a short test plan covering a baseline, task-quality measures, failure cases, and how prompt or model changes would be compared. The role explicitly includes experimentation, testing, and model evaluation.

  • Map the path from prototype to production

    Prepare a brief deployment sketch covering CI/CD, monitoring, MLOps or AI Ops, and handoffs with data, engineering, and business teams. Include governance, ethics, and bias checks, which the posting names as responsibilities.

  • Practice two versions of your explanation

    Explain the same AI design once to an engineer and once to a business stakeholder. Aim to make the trade-offs and evaluation findings clear without overstating what a prototype proves.

  • Bring targeted questions for Globant

    Ask which AI use cases are currently moving beyond proof of concept, how teams evaluate and monitor them, and which of the listed tools and cloud services are used in this role. The posting describes these responsibilities but does not specify the team's implementation.

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

Availability last checked: Nov 4, 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 United States. Matched to this role, not your profile.

Explore more jobs
Finding similar opportunities…