Technical Solutions Engineer - Temporary full-time remote staff role (2-year term)

DataKind is looking for a hands-on Technical Solutions Engineer to drive data integration, solution design, and cross-team technical partnership from discovery through deployment. This role involves onboarding and implementing their platform for higher education institutions, requiring technical skills to connect systems and troubleshoot data flows.

Responsibilities:

• Directly build and ship the technical work each institution's onboarding requires – writing and modifying code, pipelines, and configuration to connect their systems to ours
• Configure, validate, and troubleshoot data mappings, schema alignment, and data flows specific to each institution's environment
• Anticipate integration risks and unblock issues independently before they stall a deployment
• Build reusable technical assets: reference architectures, integration playbooks, mapping templates so that each institution onboards faster than the last
• Serve as the primary technical point of contact for participating higher education institutions, partnering closely with the account/success manager on each relationship
• Lead technical discovery: understand each institution's data landscape and translate it into integration and governance requirements and a recommended solution design, while being aware of the internal technical and product roadmap and constraints
• Run solution design and architecture conversations with institutional IT, data, and IR teams, scoping integrations, defining data flows, and setting realistic technical expectations
• Produce integration specs, and technical implementation plans tailored to each institution's environment, governance needs, and constraints
• Translate our platform's capabilities and roadmap accurately back to institutions, and translate institutional technical feedback into clear requirements for internal Technology and Product teams
• Partner with Engineering and Product to confirm proposed integration solutions are feasible and align with platform direction
• Surface recurring technical patterns and gaps across institutions to inform product priorities
• Maintain a clear, shared view of each engagement's technical status, open issues, and dependencies