Текст заказа
About OpenMined
OpenMined is a 501(c)(3) non-profit foundation that brings together leading minds in AI, security, and privacy technology to develop open-source solutions that transform how data can be accessed and shared. Founded in 2017, we’ve grown into a global community of over 18,000 members working to ensure that privacy protection and AI innovation reinforce each other rather than undermine one another. We are driven by a simple challenge: the most valuable data for solving humanity’s greatest challenges remains locked away due to privacy concerns, and we can change that through technology rather than compromise.
About the Role
We're looking for a Staff Software Engineer to join OpenMined , a nonprofit building open-source infrastructure for federated AI.
You'll work across every squad in Engineering, the teams making this vision real: AI systems built on rare and private data, where inference is fully attributed and every voice can be heard. Today, the data that matters most for AI (a hospital's records, a publisher's archive, a lab's unpublished results) stays locked away, because sharing a copy means losing control of it. So AI gets built on whatever is public, and the people whose data could have made it better get neither a say nor credit. We think there's a better design: data owners keep the only copy of their data and still answer a researcher's query or support an AI prediction, on their own terms and with credit for every contribution, while developers compose models from many independent owners into systems that beat any single model, and prove it in public. Three engineering pillars build toward that, backed by a research scientist team: AI observability, private data on the Syft network, and federated inference across models from many owners. Each squad ships its own open-source projects. What we haven't built yet is the reliable, shared foundation those projects should stand on. Building it, pragmatically and from inside the teams, is the work this role exists to lead.
This is a hands-on technical leadership role , reporting to the Head of Engineering. You write code every day. You set the technical direction for Engineering 6 to 18 months out and build the cross-team agreement needed to execute it. You own the architecture and standards for one or more deployed system areas and make the call on their major design changes. It's an individual contributor role, with no direct reports and no formal authority over team leads, so you lead through design docs, RFCs, code review, pairing, and the credibility that comes from shipping alongside the teams you're guiding. You're the engineer others come to when a design won't survive scale, cost, or the next two years of requirements, and the voice that connects each squad's decisions to the organization's broader strategy.
You bring the judgment that comes from building and operating production systems at scale: the instinct for what will break, the discipline to decouple before abstracting, and the restraint to extract a shared primitive only when it genuinely saves someone work. You bring product sense too. Our users are data owners, researchers, developers, and AI agents, and they need different things from the same system, so you design user flows, APIs, and developer experiences with the same care as the architecture behind them.
If you're motivated by building distributed systems that matter, raising the bar for brilliant senior engineers through craft rather than mandate, and making hard technical calls in a fast-moving nonprofit that's trying to change how the world shares data, we'd love to hear from you. This is a fully remote role for people based in the US, Canada, or Latin America, working within one hour of US Eastern Time.
Responsibilities
Set technical direction. Identify the highest-leverage technical problems across Engineering, including ones nobody has articulated, and turn them into a 6–18 month technical direction, building the cross-team alignment required to execute it
Lead through influence. Drive initiatives spanning multiple teams through influence, written argument, and credibility rather than authority, using design docs, RFCs, and decision records that support async collaboration across a globally distributed team.
System ownership. Own architecture and technical standards for one or more deployed, cross-team system areas; be the decision-maker on its major design changes
Turn ambiguity into programs. Translate ambiguous organizational and product goals into concrete, sequenced technical programs with success criteria, grounded in user outcomes as well as system metrics
Establish patterns and shared libraries. Start with problem framing, architectural and design anti-patterns, and decoupling within projects, then identify components that should become shared organizational primitives where they genuinely reduce work. Define standard interfaces that keep teams loosely coupled, and make adoption easy enough that it happens without mandate
Prevent expensive mistakes. Identify designs that won't survive contact with scale, cost, or the next two years of requirements, and redirect them early.
Take on the work others can't. Lead intractable performance regressions, high-stakes migrations, systemic reliability failures, including recurring incidents nobody has root-caused. Drive production readiness across teams through monitoring, graceful degradation, runbooks, and incident learning.
Grow Senior engineers. Delegate genuine scope and coach judgment, not just technique, raising the engineering bar through design review, code review, and pairing
Advise the Head of Engineering. Surface technical risk, sequencing, staffing implications of architectural choices, and build-vs-buy decisions
Resolve cross-team disputes. Broker technical disagreements between teams and produce decisions that stick
Bring the user into every technical decision. Develop deep empathy for our users (data owners, researchers, developers, and AI agents) through direct conversations, usability testing, and analysis of how products are actually used. Translate those insights into product and technical direction.
Own the end-to-end experience. Design and prototype user flows, developer experiences, and APIs with the same care as the systems behind them, so that UX, interface design, and architecture reinforce one another across products.
Lead on AI/ML system design. Guide teams on building reliably with LLMs and agents, including retrieval, routing, ensembles, evaluation, cost and latency tradeoffs, and failure modes, and on where AI does and doesn't belong in a product.
Champion agentic engineering. Model effective use of AI coding agents (e.g., Claude Code, Cursor), and help teams adopt workflows, guardrails, and review practices that increase velocity without eroding quality, security, or maintainability.
Must-Haves
8+ years of professional software engineering experience , with a track record of personally building, shipping, and operating production systems at meaningful scale, including technical leadership across multiple teams
Demonstrated product sense and user empathy. You've shaped what got built (not just how) based on direct user research, feedback, and usage data, and you can point to products whose success came from that judgment
UX and interaction design skills. You've designed user flows, interfaces, and developer experiences (APIs, SDKs, CLIs), and you're comfortable prototyping, running usability sessions, and iterating on design feedback
Strong AI/ML understanding. Working knowledge of LLMs, embeddings, retrieval, evaluation, and agent architectures, plus the judgment to know their limits, costs, and failure modes in production
Hands-on experience building production software with AI