System Integration Engineer/Developer

Title Resources Group is a title insurance underwriter serving customers and partners across America. The System Integration Engineer/Developer will build, maintain, and troubleshoot third-party integrations while contributing to backend and frontend product development, collaborating with external engineering teams, and using AI coding agents to improve delivery.

Responsibilities:

• Build, test, and maintain integrations with third-party APIs and services, and help support them once they're in production
• Troubleshoot integration failures across code, logs, and telemetry, and work out whether the problem is ours or theirs
• Work directly with engineers at partner companies to pin down contracts and push issues to resolution
• Contribute across the product outside of integration work — backend features and fixes, plus the front-end changes that go with them
• Leave behind enough documentation and monitoring that the next person isn't starting from scratch

Requirements:

• Comfort taking a piece of work and running with it — asking questions when you need to, but not needing to be walked through the details
• Comfort with AI coding agents (Cursor, Copilot, Claude Code, etc.): you can break a problem into a spec an agent can execute, direct it through the work, and review what comes back with a critical eye
• Familiarity with Azure — deploying services and using cloud logging to diagnose problems
• Solid analytical and troubleshooting skills, especially in systems you don't fully control
• Clear communication with technical people at other companies, where you can't rely on shared context
• Around 3–5 years building production software, including hands-on work integrating with third-party or external systems
• Some front-end experience — enough to carry a change through the UI as well as the API. We work in React and Angular; comparable component-framework experience translates fine
• Azure Functions, Service Bus, and Application Insights
• SQL Server
• API auth and retry patterns (OAuth 2.0, API keys, idempotency)
• GitLab CI
• experience in title, real estate, mortgage, or another data-provider-heavy domain
• Strongly preferred: C# and .NET Core — it's our primary stack