Lead Integration Engineer

Quick Facts

• Role: Lead Integration Engineer (integration and API leadership)

• Work model: Hybrid; full-time (40h/week)

• Location: Warsaw, Poland

• Rate: Up to 46 EUR/h (B2B)

Description

Lead integration modernization for pharmaceutical R&D systems, building a modern integration layer to enable how Research and Development systems exchange data.

You will design API-first architectures, lead event-driven integrations with Kafka, and shape cloud-native platform engineering practices on Azure Kubernetes Service.

In this role, you will take significant ownership by defining integration patterns, engineering standards, and technical governance while mentoring engineers.

Responsibilities

• Design and implement API-first architectures

• Build reusable integration capabilities

• Drive standardization of API contracts, schemas, and governance

• Lead adoption of event-based integrations using Kafka

• Define event standards and integration patterns

• Implement Infrastructure as Code using Terraform

• Build cloud-native services running on Azure Kubernetes Service

• Define CI/CD standards using GitHub Actions

• Improve observability, monitoring, and deployment automation

• Participate in architecture and design reviews

• Mentor engineers and establish engineering best practices

• Drive technology modernization and execute the technical roadmap

• Ensure alignment with enterprise standards, security, and compliance requirements

Requirements

• 15+ years of software engineering experience

• Education in Computer Science, Software Development, or Engineering

• Python and FastAPI

• Databricks (Databricks, Databricks Apps) and/or Lakebase

• REST APIs and microservices

• Kafka and event-driven architecture

• Kubernetes (Azure Kubernetes Service)

• Terraform and Infrastructure as Code

• Azure platform services

• GitHub Actions and CI/CD pipelines

• Distributed systems design

• SDLC best practices

• Fluent English

• Based in Poland

Benefits

• Up to 46 EUR/h (B2B)

• Hybrid work model; office presence frequency agreed during interviews

• Significant ownership to shape architecture, integration patterns, engineering practices, and technology direction