New opportunity

Lead Data and AI Solution Engineer

Great Eastern · Singapore

About this role

Great Eastern seeks a Lead Data and AI Solution Engineer for its Data & AI Center of Excellence at SG-GE Centre, Singapore. The role architects and delivers production-ready data and AI solutions that support advanced analytics, business transformation and operational excellence in the insurance domain.

Responsibilities

  • Design and lead end-to-end data and AI solution architectures; build and scale enterprise Generative AI and agentic AI solutions.
  • Establish AI integration patterns across systems, platforms and APIs, and translate business requirements into technical solutions and architecture roadmaps.
  • Set practices for AI governance, security and responsible AI; collaborate across teams, mentor engineers and help grow the Data & AI Center of Excellence.
  • Identify and mitigate business and regulatory compliance risks while keeping current with emerging technologies and threats.

Qualifications

  • Strong experience in data and AI engineering and solution architecture, with hands-on expertise in Generative AI, LLMs and/or agentic AI frameworks.
  • Ability to design scalable cloud-based data and AI architectures, with strong AWS proficiency and knowledge of Azure or GCP; understanding of data integration, APIs, microservices and modern data platforms.
  • Experience operationalizing AI through MLOps or LLMOps and integrating and orchestrating AI/ML tools and libraries. Familiarity with NLP applications such as sentiment analysis and article summarization.
  • Leadership, mentoring, problem-solving and a focus on governance, compliance and responsible AI.
  • A master’s degree or higher in Data Science, Statistics, Computer Science, Computer Engineering or an equivalent discipline involving extensive data analysis.

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

Skills for this role

Data and AI solution architectureGenerative AILarge Language ModelsAgentic AINatural Language ProcessingSentiment analysisArticle summarizationAWSAzureGoogle Cloud PlatformData integrationAPIsMicroservicesMLOpsLLMOpsAI governanceResponsible AICloud architectureAI orchestrationTechnical leadershipMentoring

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

  • Production-ready data and AI architecture

    The role leads end-to-end architectures that turn business needs into technical solutions and roadmaps. Prepare to explain architecture decisions from requirements through deployment and operation.

  • Enterprise GenAI and agentic AI delivery

    Building and scaling GenAI and agentic AI solutions is an explicit responsibility. Prepare to discuss hands-on design choices for LLM-based solutions and how they would be made reliable at enterprise scale.

  • Integration and operationalization

    The posting emphasizes patterns across systems, platforms and APIs, alongside data integration, microservices, MLOps or LLMOps, and strong AWS proficiency. Prepare to explain how these pieces fit into a maintainable production design.

  • Governance and CoE leadership

    The lead sets AI governance, security and responsible-AI practices, mitigates business and regulatory risks, collaborates across teams, and mentors engineers. Prepare examples of technical decision-making that accounts for those responsibilities.

Likely challenges to think through

  • Innovation versus control

    A likely challenge is scaling GenAI or agentic capabilities while managing security, responsible-AI and compliance risks; this is a preparation hypothesis, not a stated employer problem. Prepare to explain how you would assess risks and choose safeguards without losing sight of business value.

  • Business needs versus architectural complexity

    Translating insurance-domain objectives into roadmaps may require choosing between near-term delivery and reusable integration patterns. Prepare a concrete example of how you would clarify requirements, compare options, and sequence an architecture.

  • Hands-on delivery versus team leadership

    The role calls for both production-ready engineering and mentoring within the CoE, which may compete for time. Prepare to describe how you would retain ownership of critical technical decisions while enabling other engineers to deliver.

03

Practice your answers

Technical practice

How would you turn an insurance-domain business need into a Data and AI architecture roadmap?

What to coverThe posting calls for translating business requirements into technical solutions and roadmaps. Suggested preparation (inference): explain how you would clarify the desired outcome, data availability, constraints and success measures before sequencing a production-ready design.

How would you design an end-to-end data and AI solution for production?

What to coverThe role leads end-to-end architectures and requires knowledge of data integration and modern data platforms. Suggested preparation (inference): walk through data flow, service boundaries, reliability and scaling trade-offs, including how you would identify a failing component.

How would you evaluate and scale an enterprise Generative AI solution?

What to coverBuilding and scaling GenAI solutions is an explicit responsibility. Suggested preparation (inference): discuss quality evaluation, latency, cost and operational reliability, and how those findings would affect the architecture.

When would an agentic AI approach be appropriate, and how would you control it?

What to coverThe posting specifically mentions building agentic AI solutions and hands-on framework expertise. Suggested preparation (inference): compare agentic and simpler approaches, then explain boundaries on actions, monitoring and failure handling.

How would you integrate an AI capability across existing systems and APIs?

What to coverThe role drives integration patterns across systems, platforms and APIs and calls for microservices knowledge. Suggested preparation (inference): cover interface contracts, data flow, security and how you would troubleshoot an integration failure.

What trade-offs would guide a scalable cloud-based Data and AI architecture?

What to coverThe posting seeks strong AWS proficiency and cloud architecture skills across AWS, Azure or GCP. Suggested preparation (inference): explain how you would weigh scalability, resilience, security and cost without assuming the employer uses a particular service.

How would you operationalize and monitor an AI solution after deployment?

What to coverExperience with MLOps or LLMOps is stated in the posting. Suggested preparation (inference): describe versioning, release checks, monitoring and rollback, including what signals would prompt investigation.

How would you choose and orchestrate AI/ML tools and libraries?

What to coverThe posting calls for proficiency in integrating and orchestrating AI/ML tools and libraries. Suggested preparation (inference): explain selection criteria, component interfaces and how you would isolate errors across a workflow.

How would you evaluate an NLP application such as sentiment analysis or article summarization?

What to coverBoth applications appear in the posting as examples of NLP use cases. Suggested preparation (inference): compare task-appropriate quality measures, review representative errors and explain how business needs would shape evaluation.

How would you incorporate governance, security and responsible AI into a solution design?

What to coverThe role establishes practices in these areas and addresses business and regulatory compliance risks. Suggested preparation (inference): discuss risk identification, controls, review points and how you would respond when a new threat changes the design.

Behavioural practice

Tell me about a time you aligned teams around a technical architecture.

What to coverThe role involves cross-functional delivery and influencing teams. Suggested preparation (inference): use a real situation, describe how you handled differing priorities, and state the decision and result.

Tell me about a time you mentored an engineer through a difficult problem.

What to coverMentoring engineers and growing the Data & AI CoE capability are stated responsibilities. Suggested preparation (inference): give the situation, your specific coaching actions and the observable result without taking credit for someone else's work.

Tell me about a time you identified and mitigated a governance or compliance risk.

What to coverThe posting emphasizes accountability for business and regulatory compliance risks. Suggested preparation (inference): explain the situation, how you raised and addressed the concern, and what changed as a result.

Tell me about a time you took initiative to improve a solution or way of working.

What to coverThe posting asks for initiative, ownership and willingness to embrace change. Suggested preparation (inference): describe the original problem, the change you led and its measurable or observable result.

Tell me about a time an emerging technology or threat changed your technical recommendation.

What to coverThe role calls for keeping abreast of emerging technologies and threats and highlighting potential risks. Suggested preparation (inference): use a real situation, explain how you assessed the new information, and describe your recommendation and its result.

02

Sharpen your knowledge

Topics to prepare

  • End-to-end data and AI architecture

    Review how data ingestion, AI components and serving fit into a production-ready architecture. Exercise: sketch an insurance-domain solution and explain its scaling and reliability trade-offs. The posting explicitly calls for end-to-end, scalable data and AI architectures.

  • Generative and agentic AI design

    Compare an LLM-based workflow with an agentic workflow, including where each needs limits and oversight. Exercise: explain which approach you would choose for a hypothetical insurance use case and why. The role explicitly includes building and scaling GenAI and agentic AI solutions.

  • Enterprise integration patterns

    Revise how APIs, microservices, data platforms and AI components interact. Exercise: draw two integration patterns and explain their data flows and failure points. The posting calls out integration across systems, platforms and APIs.

  • MLOps and LLMOps principles

    Review the path from an AI prototype to an operated solution, including evaluation, monitoring and controlled changes. Exercise: outline that lifecycle for one LLM application. Experience operationalizing AI with MLOps or LLMOps is explicitly requested.

  • AI governance and compliance

    Review security, responsible AI and business-risk considerations for an insurance-domain AI architecture. Exercise: list plausible risks and corresponding mitigations, clearly treating the examples as your preparation rather than stated company policy. Governance and regulatory-risk mitigation are explicit responsibilities.

Skills to revise

  • Translate requirements into a roadmap

    Practice turning a hypothetical business need into a solution brief with requirements, architecture decisions and phased delivery steps. This directly reflects the stated responsibility to translate business requirements into technical solutions and architecture roadmaps.

  • Design a cloud deployment

    Draw a scalable AWS-based data and AI architecture and explain how its design choices might differ on Azure or GCP. This practices the advertised strong AWS proficiency and cloud-architecture requirement without assuming a particular service stack.

  • Prototype and evaluate an NLP workflow

    As a preparation exercise, create a small LLM workflow for article summarization or sentiment analysis; inspect a few outputs for accuracy and failure cases. The posting names hands-on LLM expertise and both NLP use cases, but does not prescribe a specific project.

  • Specify an AI integration interface

    Draft an API contract and sequence of interactions between an AI component, a microservice and a data platform; include an error path. This practices the explicitly requested integration and orchestration capabilities.

  • Plan operational checks

    Write a deployment checklist for an AI solution covering evaluation, monitoring, change control and rollback, then walk through a hypothetical failed release. This exercises the posting’s MLOps or LLMOps requirement.

  • Lead a design and risk review

    Practice presenting an architecture to a cross-functional audience, asking an engineer to critique it, and recording governance and compliance risks with mitigations. This combines the role’s explicit leadership, mentoring and risk-accountability responsibilities.

04

Your preparation checklist

  • Prepare an end-to-end project walkthrough

    Choose a data or AI solution you led, if available. Explain the business need, architecture, your decisions, production rollout and measurable outcome. The role calls for hands-on architecture leadership.

  • Sketch an enterprise GenAI design

    Prepare a clearly labeled hypothetical insurance use case. Diagram an LLM or agentic workflow, its data sources, system and API integrations, and how you would evaluate its output. Sentiment analysis or article summarization could serve as the example.

  • Practice a cloud architecture exercise

    Draw a scalable design using AWS, which the posting emphasizes. Show data integration, APIs, microservices and a modern data platform; be ready to explain trade-offs and where Azure or GCP knowledge applies.

  • Show how the solution reaches production

    Prepare a sequence from development through deployment and monitoring using MLOps or LLMOps practices. Identify how AI tools or libraries would be integrated and orchestrated, and distinguish past experience from proposed choices.

  • Map governance and risk controls

    Create a short risk-and-control table for the hypothetical design covering security, responsible AI, business and regulatory compliance risks, and emerging threats. Explain who would own and review each proposed control rather than claiming it is Great Eastern policy.

  • Rehearse leadership and roadmap examples

    Prepare examples, if available, of translating business requirements into a technical roadmap, working across teams and mentoring engineers. State your contribution, the trade-offs resolved and the outcome.

  • Organize evidence against the stated qualifications

    Assemble concise examples of data and AI engineering, solution architecture, AWS, GenAI or agentic AI, and operationalization work. Have relevant degree details ready; the posting specifies a master’s degree or above in a listed or equivalent data-intensive discipline.

  • Draft questions for the interviewers

    Ask which insurance use cases the Data & AI Center of Excellence prioritizes, what production and governance challenges the team faces, and how this lead role balances hands-on delivery with mentoring. These are questions to investigate, not stated company practices.

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 Singapore. Matched to this role, not your profile.

Explore more jobs
Finding similar opportunities…