New opportunity

Data & AI Architect

CBRE · Sydney, Australia

About this role

CBRE seeks a Data & AI Architect to lead the design, delivery and evolution of its enterprise data and AI capability across its Pacific business. Based in Sydney CBD on a hybrid arrangement, this senior technical authority will connect architectural decisions to business strategy while remaining hands-on in solution design and delivery.

Responsibilities

  • Lead, mentor and develop a team of data and AI professionals; work with senior business and technology leaders to own the architecture strategy and roadmap.
  • Define current- and future-state data architecture across domains, platforms, integrations and data flows, aligned with business and technology strategy.
  • Guide cloud data platform, model, pipeline and storage design. Ensure platforms and ingestion are scalable, secure, cost-efficient and consistent with enterprise standards.
  • Modernise and rationalise data stores and platforms to reduce duplication and promote reuse. Build AI-ready foundations for advanced analytics and innovation, and contribute directly to strategic projects.

Requirements

  • 10+ years in data engineering, data or solution architecture, or AI/ML platform roles, including 5+ years in a senior architecture or leadership capacity.
  • Proven delivery of cloud data platforms and lakehouse architectures using Azure, AWS, GCP, Databricks or Snowflake; experience designing and deploying AI, machine learning and generative AI solutions.
  • Knowledge of LLMs, RAG, MLOps and vector database architectures; strong data architecture, modelling, integration and governance skills; hands-on capability in Python, Java, JavaScript or C#.
  • Strong stakeholder engagement, team leadership and influencing skills, with an ability to balance long-term strategy and practical delivery.

Benefits and conditions: The role offers executive stakeholder exposure, career development and access to cloud, data and AI technologies. Benefits include 14 weeks of paid primary carer leave plus a one-month return-to-work bonus, four weeks of paid secondary carer leave, two paid volunteer days annually, and listed travel, health and wellbeing benefits. The successful applicant must undergo pre-employment background screening.

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

Skills for this role

Data architectureSolution architectureData engineeringCloud data platformsLakehouse architectureAzureAWSGCPDatabricksSnowflakeData modellingData integrationData governanceData pipelinesData storage architectureMachine LearningGenerative AILarge Language ModelsRAGMLOpsVector databasesPythonJavaJavaScriptC#Team leadershipStakeholder engagement

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

  • Own the Pacific architecture roadmap

    CBRE assigns this role ownership of the Data & AI architecture strategy and roadmap, including current- and future-state designs aligned with business and technology strategy.

  • Lead the Data & AI team and influence stakeholders

    The role leads, mentors and develops Data & AI professionals while working with senior business and technology leaders to connect technical choices to business strategy.

  • Design dependable cloud data platforms

    The architect guides cloud platform, lakehouse, model, pipeline and storage design, with explicit attention to scalability, security, cost efficiency and enterprise standards.

  • Modernise data architecture for reuse

    CBRE calls for architectural leadership across domains, integrations and data flows, and for rationalising data stores and platforms to reduce duplication.

  • Build AI-ready foundations while delivering solutions

    The posting pairs advanced-analytics and AI-ready data foundations with hands-on solution design and strategic project delivery; it also seeks experience deploying AI, ML and generative AI solutions.

Likely challenges to think through

  • Balancing roadmap ownership with hands-on delivery

    Preparation hypothesis: strategic design could compete for time with project delivery. Prepare an example showing how you set architectural direction, delegated decisions and stayed technically involved without becoming a delivery bottleneck.

  • Rationalising platforms without disrupting useful work

    Preparation hypothesis: reducing duplication across domains may require trade-offs between standardisation and existing needs; CBRE does not describe its current estate. Prepare to explain how you would assess dependencies, sequence changes and measure reuse before proposing consolidation.

  • Making AI platforms practical and controlled

    Preparation hypothesis: supporting AI innovation while keeping ingestion and platforms secure, scalable and cost-efficient may create competing design choices. Prepare a concrete architecture trade-off that covers data governance, operating cost and a path from prototype to production.

03

Practice your answers

Technical practice

How would you define a current-state and future-state data architecture for a Pacific-wide business?

What to coverThe role owns the architecture strategy and roadmap across domains, platforms, integrations and data flows. Suggested focus: explain how you would map the current landscape, connect target decisions to business priorities and sequence changes that can be delivered.

How would you design a cloud lakehouse architecture for enterprise analytics?

What to coverThe posting calls for experience delivering cloud data platforms and lakehouse architectures. Suggested focus: discuss storage, processing and modelling choices, and how you would evaluate a suitable platform from those named in the posting without assuming CBRE has selected one.

How would you model and integrate data across domains while maintaining governance?

What to coverThe role provides architectural leadership across domains and integrations and calls for strong modelling and governance skills. Suggested focus: address shared definitions, ownership, data quality and the trade-off between domain-specific needs and enterprise reuse.

How would you design data ingestion and pipelines to scale reliably?

What to coverThe posting asks the architect to guide pipeline design and ensure ingestion is scalable. Suggested focus: compare ingestion patterns, explain how you would handle changing data and failures, and describe how you would evaluate reliability.

How would you balance security, cost and enterprise standards in a cloud data platform?

What to coverThese are explicit considerations for platforms and ingestion in the role. Suggested focus: explain how architectural choices affect access, operating cost and scalability, and how you would document trade-offs against enterprise standards.

How would you rationalise overlapping data stores without disrupting their users?

What to coverThe role calls for modernisation that reduces duplication and promotes reuse. Suggested focus: describe how you would identify overlap, choose what to consolidate and plan a phased migration with checks that needed data remains available.

What makes an enterprise data foundation ready for AI and advanced analytics?

What to coverBuilding AI-ready data foundations is a stated responsibility. Suggested focus: connect data quality, discoverability, governance and reusable access patterns to the needs of analytics and AI solutions.

How would you design and evaluate a RAG solution using an LLM and vector database?

What to coverThe posting explicitly names LLMs, RAG and vector database architectures. Suggested focus: cover retrieval and indexing choices, access to source data, and how you would test answer quality and limitations before deployment.

How would you take a machine learning or generative AI solution from design into operation?

What to coverThe role calls for AI and machine learning deployment experience and knowledge of MLOps. Suggested focus: discuss evaluation, versioning, deployment and monitoring, including how operational feedback could inform changes.

How would you troubleshoot a failing or slow data pipeline while staying hands-on?

What to coverThe role combines architectural leadership with hands-on delivery and names Python, Java, JavaScript or C# as relevant languages. Suggested focus: walk through how you would isolate the cause, verify a fix and decide whether a code change or architectural change is warranted.

Behavioural practice

Tell me about a time you developed a data or AI team member.

What to coverLeading, mentoring and developing a team is a stated responsibility. Suggested focus: use a real situation, the coaching actions you took and an observable result for the person or team.

Describe a time you influenced senior leaders on an architecture decision.

What to coverThe role works closely with senior business and technology leaders and connects technical choices to strategy. Suggested focus: explain the situation, how you presented trade-offs or addressed disagreement, and the resulting decision.

Tell me about a time you balanced a long-term architecture roadmap with an urgent delivery need.

What to coverThe posting explicitly calls for balancing strategy with practical delivery. Suggested focus: describe the competing pressures, the decision and actions you took, and the effect on delivery and the longer-term plan.

Describe a time you aligned teams around shared data standards or reuse.

What to coverEstablishing best practice and reducing duplication are part of the advertised work. Suggested focus: give a real example of differing needs, how you gained agreement and what changed as a result.

Tell me about a strategic project where you remained directly involved in solution design.

What to coverThe role calls for a senior technical authority who also remains hands-on in strategic delivery. Suggested focus: distinguish your own design actions from the team's work, explain a challenge you addressed and state the outcome.

02

Sharpen your knowledge

Topics to prepare

  • Enterprise architecture and roadmap

    The posting calls for current- and future-state architecture aligned with business and technology strategy. As a revision exercise, outline a hypothetical architecture roadmap and explain how you would sequence near-term delivery against longer-term changes.

  • Cloud lakehouse design

    The posting requires experience delivering cloud data platforms and lakehouse architectures on Azure, AWS, GCP, Databricks or Snowflake. As a revision exercise, compare two listed options for a hypothetical workload, explaining platform, storage and pipeline trade-offs without assuming CBRE uses either.

  • Data modelling, integration and governance

    The posting explicitly names modelling, integration, governance, data domains and flows. As a revision exercise, sketch how two hypothetical domains would exchange data, then explain model ownership, data quality and governance decisions.

  • Secure, efficient modernisation

    The role calls for scalable, secure, cost-efficient ingestion and rationalising stores to reduce duplication. As a revision exercise, assess a hypothetical set of overlapping data stores and explain what you would consolidate, retain or reuse, including the risks.

  • AI-ready foundations and AI architectures

    The posting names deployed AI, machine learning and generative AI solutions, plus LLMs, RAG, MLOps and vector database architectures. As a revision exercise, trace a hypothetical RAG solution from governed data through retrieval and deployment, identifying design and operational trade-offs.

Skills to revise

  • Produce an architecture design

    Practice drawing a hypothetical current-state and future-state diagram covering domains, integrations, pipelines and storage. Annotate scalability, security and cost decisions; this reflects the role's hands-on solution design responsibility.

  • Implement a small ingestion pipeline

    As a suggested practice exercise, use one language listed in the posting—Python, Java, JavaScript or C#—to transform sample data, validate records and handle failures. This tests the hands-on coding capability and ingestion concerns the posting names.

  • Review an AI solution design

    Practice critiquing a hypothetical ML or generative AI design: identify its data dependencies, retrieval or vector-database choices where relevant, and how deployment would be operated. The posting asks for AI solution delivery and MLOps knowledge; this exercise is not a stated interview task.

  • Present and defend a roadmap

    Rehearse a short explanation of a hypothetical architecture decision to senior business and technology stakeholders, including alternatives, delivery milestones and team responsibilities. This reflects the posting's emphasis on influencing, team leadership and balancing strategy with delivery.

04

Your preparation checklist

  • Map evidence to the role

    Prepare a one-page evidence map for the posted experience thresholds, cloud lakehouse delivery, AI solution delivery and hands-on coding requirement. Note gaps rather than implying experience you cannot substantiate.

  • Rehearse a cloud platform walkthrough

    If you have a relevant project, prepare a diagram and concise account of your decisions on models, ingestion, pipelines and storage, including scale, security, cost and outcomes. The posting names Azure, AWS, GCP, Databricks and Snowflake as relevant platforms.

  • Practice a current-to-future-state design

    As an interview exercise, sketch data domains, integrations and flows, then propose a migration path that reduces duplicate stores and promotes reuse. Explain assumptions and trade-offs; this is preparation, not a claim about CBRE’s existing architecture.

  • Prepare an AI solution walkthrough

    If supported by your experience, describe a deployed ML or generative AI solution, your contribution and its outcome. Be ready to explain where LLMs, RAG, vector databases and MLOps fit—and when they would not.

  • Select leadership and influencing examples

    Prepare two specific examples covering team development and a decision made with senior business or technology stakeholders. Show how you balanced a longer-term architecture goal with practical delivery.

  • Draft a strategy-to-delivery roadmap

    Practice presenting a short, hypothetical roadmap for AI-ready data foundations across a Pacific business. State the business decisions it would support, delivery priorities, dependencies and measures you would validate with CBRE.

  • Write questions for the interviewers

    Ask which data and AI capabilities are priorities, where duplication or integration causes the most difficulty, and how architecture decisions and hands-on delivery are shared across the team.

  • Plan an accurate AI-use disclosure

    CBRE asks candidates to disclose AI use in the application and interview process. Record any use in your preparation so you can describe it accurately if relevant.

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

Explore more jobs
Finding similar opportunities…