Drimva

TD Bank

Software Engineer – Compliance Technology

$120K–$170K

New York, New York · On-site · Full-time · Posted Sep 17, 2026

Experience
3 to 5 years of technology delivery and software engineering experience.
Education
Minimum bachelor’s degree in computer science or a related field.

About the job

Design, build, deliver, and support technology solutions for compliance, surveillance, supervision, and regulatory controls in financial services.

What you'll do

  • Lead end-to-end delivery of compliance technology initiatives, including roadmaps, dependencies, and stakeholder coordination.
  • Design and develop scalable, secure systems using distributed, API-driven, event-driven, microservices, and cloud-native architectures.
  • Translate regulatory and control requirements into auditable technology solutions and support audits, reviews, and remediation.

What they ask for

  • Hands-on back-end development experience with Java RESTful services, SQL and NoSQL databases, and message queues including Kafka.
  • Experience with big data technologies, data analytics, and AI; integration projects involving multiple systems and platforms.
  • Experience in Agile delivery and driving technology strategies and roadmaps aligned with business objectives.
  • Bachelor’s degree in computer science or a related field.

Nice to have

  • Experience delivering regulatory, risk, compliance, surveillance, or supervisory technology solutions; financial-services experience is preferred.
  • Knowledge of trade surveillance, market abuse monitoring, or global markets and trading lifecycles; experience with big data, cloud technologies, and architecture.

Pay

$120,000.00 - $170,000.00 USD (base salary)

Tools

Java RESTful services, SQL, NoSQL, Kafka, big data, artificial intelligence (AI), machine learning (ML)

AI focus

Develop solutions using artificial intelligence and machine learning, alongside big data and automation, to improve operational efficiency and regulatory outcomes.

Model-written summary · the original posting is authoritative

First seen Oct 28, 2026 · Last verified Nov 5, 2026 (UTC)