Citi interview questions

Connect your motivation to the listed engineering work and give a specific example of relevant experience.

Summarise your role, the system’s purpose, and your individual contribution.

Describe how you adjust detail, check understanding, and communicate impact or options.

Give practical examples of how you collaborate, make decisions, and deliver in a team.

Relate your goals to the role’s development, design, and collaboration responsibilities.

State your notice period and expectations clearly and professionally, without overstating flexibility.

Discuss service boundaries, failure handling, timeouts, retries, and how you would test resilience.

Describe the application structure, configuration approach, and a specific design decision you made.

Cover resource and request design, validation, suitable responses, and relevant testing.

Explain how you would inspect the query and execution plan, assess indexes and data access, and verify improvements.

Compare data structure, consistency, query needs, and operational considerations in the context of the use case.

Explain event flow, consumer behaviour, failure handling, and how you would make processing reliable.

Explain the context, options, trade-offs, decision process, and outcome, separating your contribution from the team’s.

Give a concrete example of prioritisation, the risks considered, and how you communicated the trade-off.

Outline diagnosis, coordination, restoration, and a practical prevention or monitoring improvement.

Describe how you assess impact, urgency, dependencies, and ownership, and how you keep stakeholders informed.

Give an example of constructive guidance, follow-up, and the effect on their work.

Show how you elicited needs, explained evidence and trade-offs, and reached or escalated a decision.

Link your motivation to requirements, process analysis, and stakeholder work in the role summary.

Summarise the business need, your responsibilities, stakeholders, and outcome.

Explain how you structure requirements, confirm shared understanding, and handle ambiguity.

Give examples of differing needs and how you tailored discussions or documentation.

Connect your goals to the role’s requirements, process, data, and delivery responsibilities.

State your notice period and expectations clearly and professionally.

Describe how you would validate filters, joins, aggregation, and source data, then reconcile the results.

Explain how you would reproduce the issue, inspect inputs and logic, trace execution, and validate a safe correction.

Cover workflow status and configuration, relevant data and logs, dependencies, and evidence for escalation.

Describe the process steps, roles, systems, exceptions, and how you would document and validate the gap.

Show how you define scope, actors, outcomes, testable criteria, and links for traceability.

Include representative scenarios, data and expected results, participant coordination, defect triage, and sign-off evidence.

Describe how you identified the underlying needs, documented decisions, and confirmed an agreed scope.

Explain the criteria used, stakeholder involvement, dependencies, and how deferred needs were recorded.

Give the baseline problem, evidence gathered, recommendation, and how the outcome was assessed.

Show how you would assess impact and risk, coordinate triage, present options, and document the decision.

Explain how you assessed scope and delivery effects, updated traceability, and aligned affected stakeholders.

Describe practical links among source needs, mappings, stories, acceptance criteria, tests, and approvals.

Connect your motivation to the listed data platforms, pipeline work, and collaboration responsibilities.

Summarise the data problem, your contribution, technologies used, and a verifiable outcome.

Describe how you communicate impact, evidence, next steps, and technical detail at the right level.

Give an example of how you clarified a need and collaborated through implementation.

Relate your goals to pipeline development, platform support, and application enhancement work.

State your notice period and expectations clearly and professionally.

Discuss transformations, partitioning, checkpoints or restart strategy, and validation of output.

Explain how you would inspect the execution plan and stages, assess data skew and resource use, and test changes.

Describe entities, relationships, grain, key definitions, and validation with users.

Cover consumer processing, ordering or offset considerations, duplicate handling, and monitoring.

Explain how you would verify partitions, table and file metadata, query logic, and source completeness.

Describe how you would inspect logs and job status, verify inputs and permissions, and record or escalate findings.

Describe the evidence, users affected, options considered, your recommendation, and the result.

Explain how you assess user impact, urgency, dependencies, and risk, then communicate decisions.

Show how you clarified symptoms, aligned on evidence, divided responsibilities, and verified the solution.

Give an example of practical guidance, how you checked understanding, and the effect on their work.

Describe triage, ownership, prioritisation, communication, and steps to reduce recurring failures.

Explain the need, migration or transition risks, stakeholder coordination, and how continuity was protected.

Connect your motivation to the listed KYC, fraud, dispute, or operational support work relevant to the role.

Give a specific example showing how you managed accuracy, workflow, and deadlines.

Explain what information you provide, how you track the request, and when you escalate.

Describe a practical method for tracking status, documentation, and outstanding actions.

Relate your goals to the role’s operational responsibilities and the skills you can contribute.

State your notice period and expectations clearly and professionally.

Describe how you verify required information and documentation, record status accurately, and address gaps.

Explain how you follow applicable procedures, review relevant information, document rationale, and escalate concerns.

Cover status tracking, appropriate stakeholder contact, accurate records, and timely escalation.

Describe how you review patterns and control steps, document evidence, and raise the issue through the right channel.

Explain how you validate source data, define clear indicators, and present exceptions or trends accurately.

Describe a consistent review of case evidence, documentation, decision criteria, and escalation where needed.

Describe the evidence, the cause you investigated, actions taken, and how you checked whether quality improved.

Explain how you assess risk and urgency, keep work visible, and communicate priorities or constraints.

Give an example showing clear ownership, complete evidence, follow-up, and an appropriate resolution.

Cover fact-based feedback, coaching or training, follow-up review, and escalation where needed.

Describe the problem, your contribution, stakeholders involved, and how you considered quality and controls.

Explain how you would clarify the request, protect controls, raise risks, and propose a compliant way forward.