Pay
$127K–$190K is typical
The middle half of what similar US postings state. This one doesn’t list pay.
From 2,396 postings in the last year. Stated ranges, not salaries paid.
Cincinnati, Ohio
Live, first seen by us 20 days agoEmployment type in the employer’s posting: Full timeFrom the employer’s posting
You will design and write code every week: Terraform, pipelines, stream processing applications and platform services.
Make your mark at one of the biggest names in payments. We're looking for a Lead Platform Engineer to join our Enterprise Data Platform Engineering team as the hands-on technical lead for our new streaming data platform. We are building a shared platform on Apache Kafka for the whole company. It carries payment events in real time to applications, to the data lake and to services that need the current state of that data with low latency. You will shape the technical direction of the platform and own its technical strategy, and you will build it yourself. You will design and write code every week: Terraform, pipelines, stream processing applications and platform services. The team is small, and everyone builds. In your first year you will help stand up the platform in production, onboard the first teams and start moving existing Kafka workloads onto it. You will share the platform on-call rotation. What you'll own
These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.
$127K–$190K is typical
The middle half of what similar US postings state. This one doesn’t list pay.
From 2,396 postings in the last year. Stated ranges, not salaries paid.
Day 20
Similar jobs usually come down between day 6 and day 56.
At Global Payments, jobs usually come down by about day 25.
From 13,991 similar postings that came down, and 70 of Global Payments’s. Coming down is not always a hire.
26 open jobs
Open jobs by the week we first saw them, last 12 weeks.
Add your resume and we’ll mark which of these tools you already use, and point out anything in the posting that could rule you out.
- Kafka on Kubernetes. You have built and run self-managed Kafka on Kubernetes entirely through automation and infrastructure as code, including operators, upgrades, scaling and recovery. - Strong programming skills with deep Kafka knowledge. You write production code in Java with the Kafka clients, Kafka Streams or Apache Flink. You can design and build platform functionality such as an encryption module: an application that transforms every event in flight by calling an external service, without losing data or falling behind. - Strong cloud engineering on AWS or Google Cloud, across regions. You know networking and private connectivity, identity and access, encryption, and key and secrets management.
- Strong programming skills with deep Kafka knowledge. You write production code in Java with the Kafka clients, Kafka Streams or Apache Flink. You can design and build platform functionality such as an encryption module: an application that transforms every event in flight by calling an external service, without losing data or falling behind. - Strong cloud engineering on AWS or Google Cloud, across regions. You know networking and private connectivity, identity and access, encryption, and key and secrets management. - Infrastructure as code as a daily practice. You write, review and test Terraform modules, build and rebuild environments from code, put guardrails and policy in code, and turn approved patterns into reusable templates.
- Experience in payments, fintech or another highly regulated industry, especially with PCI DSS. - Certifications: Confluent Certified Administrator for Apache Kafka or Confluent Certified Developer for Apache Kafka, and AWS or Google Cloud certifications. - Contributions to open-source Apache Kafka or related projects.
What you'll own - The platform, designed and built in code: Kafka across regions, schema registry and data contracts, connectors and change data capture, stream processing, delivery into Apache Iceberg tables, and real-time serving to applications. - Self-service for product teams, built as platform services: topic as a service, schema as a service and self-service ingestion of new data sources, with templates for the patterns teams are allowed to use.
- Contributions to open-source Apache Kafka or related projects. - Experience with a managed Kafka service, Apache Iceberg, low-latency data serving or distributed NoSQL databases, or work on more than one public cloud. EEOC Statement
Job Description Lead Platform Engineer, Kafka and Streaming Data Ready to take your career global?
Make your mark at one of the biggest names in payments. We're looking for a Lead Platform Engineer to join our Enterprise Data Platform Engineering team as the hands-on technical lead for our new streaming data platform. We are building a shared platform on Apache Kafka for the whole company. It carries payment events in real time to applications, to the data lake and to services that need the current state of that data with low latency. You will shape the technical direction of the platform and own its technical strategy, and you will build it yourself. You will design and write code every week: Terraform, pipelines, stream processing applications and platform services. The team is small, and everyone builds. In your first year you will help stand up the platform in production, onboard the first teams and start moving existing Kafka workloads onto it. You will share the platform on-call rotation. What you'll own
- Self-service for product teams, built as platform services: topic as a service, schema as a service and self-service ingestion of new data sources, with templates for the patterns teams are allowed to use. - The technical strategy: architecture, standards, roadmap and the plan to move existing Kafka workloads onto the platform. You write the designs and standards the team builds to. - Card-data protection to PCI DSS. You design and build the streaming encryption module: a stream processing application on Kafka that encrypts or tokenizes card fields in flight through the company's tokenization service. You also own keys, access control and audit evidence.
- The technical strategy: architecture, standards, roadmap and the plan to move existing Kafka workloads onto the platform. You write the designs and standards the team builds to. - Card-data protection to PCI DSS. You design and build the streaming encryption module: a stream processing application on Kafka that encrypts or tokenizes card fields in flight through the company's tokenization service. You also own keys, access control and audit evidence. - Reliability: replication between regions, failover drills, service objectives, monitoring and alerting, load testing, capacity planning, and the root cause of production incidents.
- Reliability: replication between regions, failover drills, service objectives, monitoring and alerting, load testing, capacity planning, and the root cause of production incidents. - The move onto the platform: live workloads moved without downtime with the teams that own them, existing self-managed Kafka kept healthy until it retires, and the platform's cost shown to each team that uses it. What you'll bring
What you'll bring - Expert, hands-on Apache Kafka. You have designed and run a multi-region Kafka platform used by many teams and moved live workloads onto it without downtime. You know replication between clusters, Kafka Connect, change data capture and schema registry in depth. - Kafka on Kubernetes. You have built and run self-managed Kafka on Kubernetes entirely through automation and infrastructure as code, including operators, upgrades, scaling and recovery.
- Expert, hands-on Apache Kafka. You have designed and run a multi-region Kafka platform used by many teams and moved live workloads onto it without downtime. You know replication between clusters, Kafka Connect, change data capture and schema registry in depth. - Kafka on Kubernetes. You have built and run self-managed Kafka on Kubernetes entirely through automation and infrastructure as code, including operators, upgrades, scaling and recovery. - Strong programming skills with deep Kafka knowledge. You write production code in Java with the Kafka clients, Kafka Streams or Apache Flink. You can design and build platform functionality such as an encryption module: an application that transforms every event in flight by calling an external service, without losing data or falling behind.
- Certifications: Confluent Certified Administrator for Apache Kafka or Confluent Certified Developer for Apache Kafka, and AWS or Google Cloud certifications. - Contributions to open-source Apache Kafka or related projects. - Experience with a managed Kafka service, Apache Iceberg, low-latency data serving or distributed NoSQL databases, or work on more than one public cloud.
- Strong cloud engineering on AWS or Google Cloud, across regions. You know networking and private connectivity, identity and access, encryption, and key and secrets management. - Infrastructure as code as a daily practice. You write, review and test Terraform modules, build and rebuild environments from code, put guardrails and policy in code, and turn approved patterns into reusable templates. - DevOps and automation. You have built CI/CD pipelines and self-service platform services, such as topic and schema provisioning and data ingestion, and you prove service objectives with monitoring, load tests and failover tests.
Complete your application on tsys.wd1.myworkdayjobs.com. The employer’s form will show what is required.
Already applied? Track this application
Job Description
Lead Platform Engineer, Kafka and Streaming Data
Ready to take your career global?
Make your mark at one of the biggest names in payments.
We're looking for a Lead Platform Engineer to join our Enterprise Data Platform Engineering team as the hands-on technical lead for our new streaming data platform. We are building a shared platform on Apache Kafka for the whole company. It carries payment events in real time to applications, to the data lake and to services that need the current state of that data with low latency. You will shape the technical direction of the platform and own its technical strategy, and you will build it yourself. You will design and write code every week: Terraform, pipelines, stream processing applications and platform services. The team is small, and everyone builds. In your first year you will help stand up the platform in production, onboard the first teams and start moving existing Kafka workloads onto it. You will share the platform on-call rotation.
What you'll own
What you'll bring
It's a bonus if you have
EEOC Statement
Global Payments is an equal opportunity employer. We evaluate qualified applicants without regard to race, color, religion, sex, sexual orientation, gender identity, marital status, genetic information, national origin, disability, veteran status, and other protected characteristics. The EEO is the Law poster is available here.
If you are made a conditional offer of employment and will be working in the United States, you will be required to undergo a drug test. In developing this job description care was taken to include all competencies and requirements needed to successfully perform the position. Reasonable accommodations will be provided for individuals with qualified disabilities both during the hiring process, as well as to allow the individual to perform the essential functions of the job, if hired.
Washington Candidates: Click here for information on the Fair Chance Act.
New Data Engineer postings at the employers we follow are up 14% over the last 6 weeks compared with the 6 before.
Each bar is one week of new postings. The darkest bars are the last 6 weeks.
Counted from the hiring pages we’ve followed for at least five weeks, so employers we add don’t look like growth. Updated weekly.
We file this job under Data Engineer, by the work the posting describes.
Data engineers build and run the pipelines that copy data out of apps and outside services into a warehouse or lake, and fix them when a source changes or a load fails.
Expect SQL, Python, a cloud platform, a scheduler such as Airflow, and often tools for large data such as Spark or Kafka.
An analytics engineer works one step later, turning the raw data a data engineer lands into clean tables people can query.
The government has no code for data engineers, so these figures are for the closest group, database architects, which includes data integration and data warehousing specialists.
Source: US Bureau of Labor Statistics, Occupational Employment and Wage Statistics (May 2025) and Employment Projections (2025 to 2035). Occupation code 15-1243.
Selected passages from the saved posting. Check the full description for conditions and exceptions.
No pay amount identified in the saved description.
Cincinnati, Ohio
Working pattern and location restrictions need checking in the full posting.
No clear work-authorization passage found. Eligibility is unconfirmed.