Senior Integration Manager
Job description
About the role
Partners move integrations from kickoff through go-live with ongoing ownership.
Software engineers turn product ideas into working code. Engineers work in small teams, review each other's work, and ship in small batches. Most teams follow agile practices such as sprints and daily standups. Engineers also write tests, fix bugs, and improve performance. The field values clear communication as much as technical skill. Engineers spend part of every week on planning, code review, and debugging, not just writing new code. The ability to explain a technical decision in plain words separates strong engineers from the rest.
Key facts
What you'll do
Partners execute integrations through kickoff, implementation, testing, and go-live.
Multiple integrations progress in parallel while maintaining delivery timelines and quality.
Partners rely on one technical contact spanning engineers to C-level stakeholders.
Technical discussions and solution designs align partner requirements with the platform.
Internal teams remove integration hurdles to keep workflows smooth.
Partners convert needs into clear technical requirements, and the team pushes back when necessary.
Technical sign-off confirms successful delivery before go-live.
Process improvements enhance integration documentation and scalability.
Requirements
The candidate holds 3+ years of experience in Integration Management, Technical Account Management, or Solutions Engineering.
Understanding of REST APIs, JSON, and HTTP is strong and practical.
Knowledge of webhooks, idempotency, and error handling is solid.
Networking fundamentals, including TCP/IP and DNS, are understood clearly.
Experience with API security, such as API keys, OAuth, JWT, and request signing (HMAC), is present.
Familiarity with logs and monitoring tools like ELK, Kibana, or Grafana is required.
Technical documentation, including API documentation, can be reviewed, understood, and created.
Analytical thinking identifies root causes within complex systems.
Communication remains excellent with both technical and business stakeholders.
An ownership mindset stays proactive, accountable, and delivery-driven.
Upper-Intermediate English (B2) proficiency or higher is necessary.
Nice to have
Experience in iGaming, fintech, or SaaS environments adds value.
Working with aggregators or platform integrations has occurred.
Exposure to high-scale environments with many concurrent integrations exists.
Handling partner negotiations or technical discussions at a senior level is familiar.
Writing scripts or working with a programming language, such as Python, JavaScript, or Bash, is possible.
Leadership potential points toward growth into a lead role.
Practical notes
The role is based in the European Union under a full-time contract.
Benefits may vary by location and contractual agreement.
Typical interview steps
Hiring for engineering roles usually starts with a recruiter screen, followed by one or two technical rounds. Candidates often solve a coding problem, discuss past projects, and answer system design questions. Some loops include a take-home task. Final rounds typically cover team fit and give candidates a chance to ask questions. Interviewers look for how you break down an unfamiliar problem, not just whether you reach the answer. Practicing a few problems aloud and reviewing your own past projects are the best preparation.
Good to know
Integration management combines technical depth and stakeholder communication.
REST APIs, JSON, and HTTP form the foundation of modern integrations.
Webhooks and idempotency ensure reliable event-driven communication.
API security relies on keys, tokens, and request signing to protect data and operations.
Monitoring tools like ELK, Kibana, and Grafana provide visibility into system health.
Career growth
Engineering careers usually progress from individual contributor to senior, staff, and principal levels. Some engineers move into management and lead teams of five to twenty people. Others stay on the technical track. Growth follows demonstrated impact, not tenure alone. A typical engineering ladder has clear levels with defined expectations for scope, quality, and mentorship. Moving up usually requires owning outcomes end to end rather than completing assigned tickets.