> Markdown version of [/jobs/ext/3714654-fix-integration-engineer](https://www.wearedevelopers.com/jobs/ext/3714654-fix-integration-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # FIX Integration Engineer - **Company:** 2Bridge Partners - **Location:** New York, NY, United States (Remote available) - **Experience:** Experienced - **Contract:** Permanent contract - **Skills:** Java (Programming Language), Application Programming Interfaces (APIs), C Sharp (Programming Language), DevOps, Financial Information EXchange, Python (Programming Language), Windows PowerShell, SQL Databases, Scripting, Backend, Low Latency, SDET - **Published:** October 13, 2026 - **Apply:** https://www.juju.com/job/15_ad2348258 ## About the Role 1. Hands-on experience working with FIX protocol in production environments (required) 2. 2+ years in a technical role such as integration, solutions engineering, DevOps, or SDET 3. Scripting experience in Python or PowerShell; exposure to C# or Java is a plus 4. Comfort querying SQL databases across multiple tables 5. Experience supporting client-facing systems in time-sensitive or regulated environments ## Description 1. Own and support client-facing integrations in latency- and reliability-sensitive environments 2. Work directly with external clients, integrating real-time trading and messaging workflows 3. Gain deep exposure to production-grade financial connectivity and protocols What You'll Do 1. Integrate clients with backend services using FIX protocol as a primary interface 2. Support and troubleshoot FIX sessions, message flows, and connectivity issues 3. Integrate additional services using REST or gRPC APIs where applicable 4. Investigate logs and system behavior to diagnose integration and connectivity issues 5. Collaborate with internal engineering teams to improve integration reliability and tooling 6. Communicate technical concepts clearly to non-technical stakeholders