Technology Placement Analyst Review

I joined Citi as a summer placement intern within a compliance technology team focused on trade surveillance. The team builds and maintains surveillance models that monitor trader activity for compliance breaches, generating alerts that flow into a case management system for analyst review.
Day-to-day, the role involved attending daily stand-ups and sprint ceremonies, completing onboarding tasks, working through structured knowledge transfer sessions covering Spark, Docker, Kubernetes, and AI tooling, and independently progressing through a technical intro project. Later weeks shifted to active sprint contribution — writing production Java and Spark code, resolving build failures, addressing code quality gates, and beginning research into a real team ticket.

Yes — responsibility came earlier than expected. Within the first four weeks I had resolved environment blockers independently, and by weeks four to six I was writing and owning production Spark and Java code end-to-end: implementing surveillance logic, generating live alerts into a production database, fixing CI pipeline failures, and raising a pull request for code owner review. By week seven I was independently researching and scoping a real team ticket using AI tooling, contributing domain knowledge directly back to the team.

The placement introduced me to several technologies I had little prior experience with — Apache Spark for large-scale data processing, Java for production backend development, Maven for build management, and AutoSys for job scheduling. I also gained hands-on experience with CI/CD pipelines, pull request workflows, and code quality tooling including SonarQube. On the AI side, I began using Devin for code review and domain research, which was a practical introduction to AI-assisted development in an enterprise context. My Git workflow improved significantly — moving from basic usage to managing feature branches, resolving authentication issues, and working within a team PR review process. My general software engineering practices developed through writing production-grade code with proper error handling, logging, and test coverage. I also improved at breaking down unfamiliar technical problems independently — diagnosing build failures, reading pipeline logs, and iterating toward a fix without always needing direct guidance.

The level of support was well-structured and scaled appropriately as the placement progressed.
The first two weeks were heavily supported — a formal training programme covered enterprise software development, DevOps, Docker, and Kubernetes, and a full onboarding webinar series introduced firm culture, conduct, and strategy.
Once embedded in the team, support came primarily through a mentor who provided knowledge transfer sessions, guided environment setup, and was available for blockers. A manager held regular one-to-ones and was accessible day-to-day. Other team members helped resolve specific technical issues — particularly around Git configuration and build environment setup — when needed.
The intro project was structured to be completed largely independently, with guidance available on request rather than hand-held throughout. This meant I had to diagnose and resolve build failures, CI pipeline issues, and code quality problems myself before escalating, which I found valuable.
A recruiter also ran regular check-ins throughout, providing a separate point of contact for any broader placement or wellbeing concerns.

The culture was welcoming and inclusive from day one. The broader firm onboarding set a clear tone around values, conduct, and the importance of speaking up — and that translated into the day-to-day team environment as well.
Within the team specifically, the atmosphere was open and approachable. No question felt too basic to ask, and team members were consistently willing to stop what they were doing to help — whether that was walking through an unfamiliar concept, pairing on a tricky environment issue, or simply explaining how something worked within the wider organisation. That made it easy to get up to speed quickly without feeling like a burden for not knowing things yet.
There was also a strong sense of community across the wider intern cohort. Events including a volunteering day, a cross-networking intern lunch, and informal social time created opportunities to build connections outside of the immediate team — including with senior colleagues at VP level and above.
More broadly, the firm felt genuinely invested in the intern experience — with dedicated recruiter support, a structured onboarding programme, and clear encouragement to engage with the business beyond just the day-to-day role.

I enjoyed the placement considerably. The work was genuinely challenging from an early stage — being handed real responsibilities rather than observational tasks made it feel worthwhile. Getting to grips with an unfamiliar technical stack, working through problems independently, and seeing code I had written generate real output in a production system were all highlights. The team environment made a significant difference too — feeling welcomed and supported meant I could focus on learning rather than finding my feet socially. If anything, the main frustration was access delays early on slowing down the technical work, but that resolved as the weeks progressed.

Yes