"Let's build the curriculum for the role I'll hire in eighteen months"

At Harbour.Space, our strongest partnerships don't begin with a logo on a slide. They begin with a partner who hires our students. The Cloud Collective, a Barcelona based cloud consultancy and Google Cloud Premier partner, is one of them. They operate exclusively within the Google Cloud ecosystem, working with Spanish companies on everything from cloud migration to production-grade AI adoption — architecture, security, FinOps, and now agentic AI built on Gemini Enterprise. Theirs is a deliberately senior team: client meetings there are as likely to turn into a cost conversation as a technical one, which is exactly the instinct they're trying to instill earlier through partnerships like this one.

Through our Work & Study apprenticeships, they sponsor students who learn inside their team on real projects while studying with us. For them, sponsoring a Work & Study apprentice isn't a recruiting shortcut — it's a way of testing, in real time, whether the curriculum they're helping shape actually produces the judgement their clients pay for.

We sat down with them to talk about something they think about every day: the gap between what universities produce and what the cloud market is willing to pay for, and why the answer looks a lot like the model we already run.

Ask them where graduates fall short and the answer is not what you'd expect.

"The gap is not in knowing how to program. That gets solved well, and formats like Harbour.Space's solve it even better than the traditional university, because they teach with people from industry."

The shortfall, they argue, sits in everything that surrounds the code in a real cloud project. A fresh graduate can write a function. What they rarely arrive with is the ability to design an architecture with cost in mind (the FinOps discipline that every technical decision is also an economic one), or to think about governance, identity and security, which is where an enterprise client's risk actually lives.

And then there is the hardest thing of all to teach: the consultant layer.

"Sitting in front of a CFO and an engineer in the same meeting and translating between the two. The university still produces people who know how to build. The market is asking for people who know how to decide what to build, what it costs, and why."

We asked them to design the ideal cloud graduate for 2027 and name the capabilities almost no one arrives with today. They gave us three.

A FinOps mindset by default. Cost as a design variable from the first line of code, not a surprise on the invoice at the end of the month.

Real fluency in applied AI. Not writing prompts, but understanding the data behind the model, the governance, the compliance (with the EU AI Act now in force), and above all knowing when not to use AI. As they put it, judgement is worth more than technique.

Bilingualism between business and technology. A graduate who reads a P&L as comfortably as an architecture diagram, and who understands that behind every migration there is a business case, not a technical whim.

Their conclusion was the line that stayed with us:

"If in 2027 someone comes to me who thinks about cost, has judgement about AI, and speaks the client's language, I hire them in the interview. The problem is that today almost no one graduates that. We all learn it from scars on real projects."

That last sentence is, in a way, the entire reason Work & Study exists. Those scars are exactly what an apprenticeship lets a student earn before graduation, not after.

So what kind of collaboration does Barcelona actually need? Not the usual kind, where a student finishes the degree and only then meets a real project. The Cloud Collective wants the opposite.

"What barely exists is the opposite: that a consultancy brings a real case, anonymised, into the classroom, and students work on a live migration or AI problem guided by an industry practitioner rather than a professor reciting theory."

Harbour.Space already runs this way. Our modules are taught by people who do the work for a living, not by theory. What they want is for specialist firms to step further inside that format: to bring real projects instead of slides, and to design credentials together for the certifications the market actually pays for in cloud, AI and security.

Then came the line that, for us, defines the whole relationship.

"The collaboration that's needed is not 'send me interns'. It's 'let's build together the curriculum for the role I'll hire in eighteen months'."

This is the part people tend to miss about Work & Study. Our apprentices are not junior hires watching from the sidelines. They arrive with capability and experience already, and for the length of the sponsorship they work on the company's live problems, alongside the company's own team.

So the alignment runs in both directions at once. The student is not waiting at the end of a pipeline to be picked. They are inside it from the first week, building the same things the business builds, learning the cost discipline, the judgement and the client language on real work rather than in a lecture. By the time they graduate, they already fit the role, because they have been doing the role.

And the partner is not waiting for a curriculum to deliver their next hire. They are helping shape it, and hiring from inside it.
That is what a Work & Study partnership looks like when it works. Not a transaction at the end of a degree, but two sides solving the same problem together until the role and the person have grown into each other.

Interested in hiring through Work & Study, or sponsoring an apprentice the way The Cloud Collective does? Discover more.