Solutions Designer

About the role Tag's Americas technology team is small by design: a new business front door, a solutions design capability, a build function, and a rollout function, working AI-natively across the region's creative production and channel activation businesses. You are the architecture brain of the function. When a major RFP or a client BAU opportunity needs a real solution designed — not a slide, a solution — you take the requirement and turn it into an architecture that can actually be built, assembled first from our existing platform catalogue and escalated to engineering only when something genuinely new is needed. You sit on the engineering side of the spectrum: hands-on enough to configure and stand up the platforms yourself, and to prove an architecture works before anyone commits to it. You work hand in hand with the New Business Technology Lead, who owns the response, the narrative, and the client room; you own the architecture and its buildability. What you will own Solution architecture for major RFPs and client BAU opportunities across both divisions: from requirement to a designed, buildable solution Hands-on assembly and configuration from the existing product catalogue — proving architectures with working configuration, not diagrams alone Partnership with the New Business Technology Lead: joining major pursuits for technical sections, architecture discussions, and demo Q&A; ensuring nothing promised is unbuildable Clean escalation of genuinely net-new build to Forward Deployed Engineering: full client context, acceptance criteria, and the architecture — and staying in the room for the demonstration Technical design authority on what is assembled versus built: applying the catalogue-first rule and protecting engineering capacity for genuinely new work Contributing reference architectures to the demo library so recurring patterns become reusable assets What success looks like Within twelve months, every major pursuit and BAU opportunity has an architecture that engineering can build without rework, the majority of designed solutions are assembled from the existing catalogue rather than built fresh, and the design-to-build handoff is clean enough that what gets demonstrated is what gets delivered. What we are looking for Solutions architecture or solutions engineering background in content production, marketing technology, or an adjacent technical domain — comfortable on the engineering side of the spectrum Demonstrated ability to configure, integrate, and stand up software platforms hands-on: APIs, integrations, cloud services, and modern AI tooling as working instruments Designs for buildability: architectures that a small engineering team can deliver, not aspirational diagrams Strong collaborator with pre-sales: can translate deep technical design into support for a client-facing partner without needing to own the room AI-native working habits: agentic tooling as the default way of proving and assembling solutions Judgment on assemble-versus-build, and the discipline to say no to net-new work the catalogue already answers Working model You do not own the RFP response, decks, or the client room (New Business Technology Lead), net-new build delivery (Forward Deployed Engineering), or post-win rollout (Customer Success). On major pursuits you and the New Business Technology Lead co-own the work: their narrative, your architecture. The role is deliberately scoped so one person can genuinely do it.