<div class="content-intro"><p><strong><span data-contrast="auto">About Us</span></strong></p> <p><span data-contrast="auto">At </span><strong><span data-contrast="auto">BGBx</span></strong><span data-contrast="auto">, we're driven by a simple idea: breakthrough thinking creates breakthrough impact. As an independent commercial solutions partner to pharmaceutical and life science companies, we bring together strategists, scientists, communicators, creatives, technologists, and data experts to tackle some of healthcare's most important challenges.</span><span data-ccp-props="{}"> </span></p> <p><span data-contrast="auto">Our teams work across consulting and communications to help clients shape strategy, launch innovations, engage stakeholders, and drive meaningful results throughout the product lifecycle. The work is complex, fast-moving, and deeply connected to improving lives, creating opportunities for curious minds to make a real difference every day.</span><span data-ccp-props="{}"> </span></p> <p><span data-contrast="auto">If you're energized by collaboration, inspired by innovation, and motivated by work that matters, you'll find a place to grow, contribute, and make a meaningful impact at BGBx. </span></p></div><p><strong>Position Overview</strong></p> <p><strong>The Agent Fleet Architect will build the operating system for an AI-native organization.</strong></p> <p>We are looking for someone who sees AI differently: not as a collection of copilots, not as isolated automations, and not as a graveyard of bots. You see <strong>systems. </strong>Agents talking to agents. Tools exposing capabilities. Context flowing across the organization. Humans stepping in where they add value. Work moving automatically from trigger to outcome. You want to build the layer that makes all of this work together.</p> <p><strong>The mission</strong></p> <p>We become an <strong>AI-native organization</strong>, not a company that happens to use AI. A company designed around humans, agents and software systems working together. Our engineering teams build the foundations: APIs, data, permissions, MCPs, CLIs, knowledge, tools and reliable internal capabilities. They make the organization <strong>understandable and accessible to machines</strong>.<em>You make it <strong>actionable</strong>. </em>You take those capabilities and turn them into agents, fleets and workflows that actually get work done.<em> </em><strong>Engineering builds the rails. You make the trains move.</strong></p> <p><strong>You build fleets, not bots</strong></p> <p>One agent is interesting, but a hundred disconnected agents are chaos. The real opportunity is in designing how they work together.</p> <p>You think about:</p> <ul> <li>Who does what, and in what order?</li> <li>What does each agent need to know?</li> <li>Which model, agent, human or tool should handle the next step?</li> <li>How does work move without losing context?</li> <li>How do we build something once and make it available everywhere?</li> <li>What should persist, where, and for whom?</li> <li>What is each agent allowed to know and do?</li> <li>How do we know what happened when something goes wrong?</li> <li><strong>Human-in-the-loop.</strong> Where do people add judgment instead of friction?</li> </ul> <p>You are designing the <strong>connective tissue</strong> of the organization.</p> <p><strong>You care about the workflow</strong></p> <p>You are not impressed because an agent can perform one clever task.</p> <p>You want the whole loop:</p> <ul> <li>A signal appears.</li> <li>An agent understands it.</li> <li>It gathers the right context.</li> <li>It calls the right tools.</li> <li>It delegates part of the job.</li> <li>Another agent picks it up.</li> <li>A human approves something important.</li> <li>A system gets updated.</li> <li>Slack gets notified.</li> <li>The next action happens automatically.</li> <li>The loop closes.</li> </ul> <p>That is what you care about. Not the demo. <strong>The workflow.</strong></p> <p><strong>Deep engineering underneath. Ridiculous speed on top.</strong></p> <p>You believe great engineering and low-code belong together. Deep engineering teams should not spend their lives building every individual automation, they should build <strong>powerful primitives</strong>: APIs. MCP servers & CLIs. Identity. Permissions. Structured data. Reusable tools. Reliable infrastructure. Then builders should be able to combine those primitives into powerful agents and workflows at extraordinary speed.</p> <p>You understand why a low-code agent sitting on top of excellent engineering infrastructure can be more valuable than another bespoke application living in isolation. You want engineering to make more of the organization <strong>programmable</strong>. Then you want to unleash it.</p> <p><strong>You understand the technology</strong></p> <ul> <li>You are not a no-code tourist.</li> <li>You have written code.</li> <li>You understand software systems.</li> <li>You can read an API spec.&