Senior Mobile Traffic Infrastructure Engineer (Keitaro)

We are looking for a senior technical consultant with hands-on experience in mobile traffic infrastructure, backend routing, attribution, Keitaro, GEO segmentation, and anti-abuse systems.

Our current architecture is:

iOS App → AWS ECS / ALB → API → Keitaro

We need an expert to review the existing setup and help us design a reliable production-ready traffic routing and filtering architecture.

The main goal is to understand which traffic signals are realistically available within this stack, which of them are worth using, and how to structure the decision logic between the mobile app, backend, AWS infrastructure, and Keitaro.

Areas we would like to review include:

— IPv4 / IPv6
— GEO location and country-level routing
— ISP / ASN data
— VPN / proxy detection
— User-Agent
— Referrer data
— DNS-related signals
— suspicious or known-abuse IP databases
— request-rate limits and anti-bot / anti-abuse rules
— traffic attribution between different apps, sources, GEOs, and offers
— Keitaro tracking parameters, click IDs, subIDs, and postbacks
— offer routing, weighted distribution, caps, and fallback logic

We would also like an assessment of more advanced identification signals, including:

— device fingerprinting
— device-level signals available on iOS
— battery-related or environment signals
— third-party detection APIs / SDKs

We want to understand which of these signals are technically available on iOS, which require changes in the mobile application, what privacy or reliability limitations they have, and whether the additional complexity is justified.

Expected deliverables

We are initially looking for a technical consultation and architecture review, not immediate full-scale development.

We expect the specialist to provide:

— review of our current architecture;
— recommended traffic routing and filtering logic;
— recommended data sources, APIs, or services;
— assessment of accuracy and false-positive risks;
— expected infrastructure and third-party API costs;
— recommendations for Keitaro integration and attribution;
— QA / staging approach for testing the complete flow;
— clear implementation plan for our existing AWS + Keitaro infrastructure.

Preferred experience

Strong practical experience with several of the following is important:

— iOS mobile traffic infrastructure
— backend traffic routing
— AWS ECS / ALB
— Keitaro or similar tracking platforms
— mobile attribution
— server-to-server postbacks
— GEO / ASN / VPN / proxy detection
— anti-bot and anti-abuse systems
— affiliate traffic infrastructure
— high-volume traffic systems

Experience with real production mobile affiliate projects is highly preferred.

Please include a short description of similar systems you have worked with and explain what parts of this stack you personally designed or implemented.

We are open to starting with a paid 1–2 hour technical consultation.