T24 Technical Lead (Payments) at Julius Baer
Singapore, Southeast, Singapore -
Full Time


Start Date

Immediate

Expiry Date

01 Aug, 25

Salary

0.0

Posted On

02 May, 25

Experience

0 year(s) or above

Remote Job

Yes

Telecommute

Yes

Sponsor Visa

No

Skills

Good communication skills

Industry

Information Technology/IT

Description

At Julius Baer, we celebrate and value the individual qualities you bring, enabling you to be impactful, to be entrepreneurial, to be empowered, and to create value beyond wealth. Let’s shape the future of wealth management together.
This role is for a T24 Technical Lead with a deep understanding of private banking modules, also acting as a senior developer. The role requires Payments (TPH) module expertise.

PERSONAL AND SOCIAL

  • Good communication skills
  • Good work ethics
  • Good problem-solving abilities
  • Good team player
  • Good service attitude
  • Systematic and meticulous
  • Ability to work both independently as well as in team
    We are looking forward to receiving your full job application through our online application tool.
Responsibilities

REGULATORY RESPONSIBILITIES &/OR RISK MANAGEMENT

  • Demonstration of appropriate values and behaviours including but not limited to standards on honesty and integrity, due care and diligence, fair dealing (treating customers fairly), management of conflicts of interest, competence and continuous development, adequate risk management, and compliance with applicable laws and regulations
  • Take responsibility for ensuring that risks and issues are identified and managed closely and drive all stakeholders to deliver on time and to the required quality standards

RESPONSIBILITIES AS A GUARDRAIL FOR THE PLATFORM

  • BJB development standards and T24 coding best practices are followed
  • Build fully complies with the blueprint, security concept and infra design
  • T-shirt sizes and estimates are within BJB estimate framework
  • Impact assessment of all T24 changes and identify downstream impact
  • Design uses the correct integration patterns and formats
  • Design is fully scalable, reliable and resilient
  • Design is not creating any platform debt (or) using any obsolete technology
  • Non-functional requirements are fully met
  • Documentation updates and sign off like JIRA, Confluence, unit test documents, source code review reports, sonar scans, vulnerability scans, operational handover documents, etc.
  • Inform platform AR of any item to report to security, IT risk, architecture to register
  • Close collaboration with Business Engineers, System Architects, PMs, test management teams
  • Continuous sharing of latest dev concepts with developers
Loading...