Associate Technical Project Manager

The Opportunity

QuoIntelligence has four engineering teams (Applications ML Data and Infrastructure) building Mercury and Agent Karla an AI-powered threat analyst used by ENISA and security teams across Europe. Right now one person coordinates everything: every daily standup every cross-team dependency and every status report. That doesnt scale.

The PM function here is evolving. Agent-powered design and development bring greater complexity and a faster pace and our operating model has to keep up. Project data sits in GitHub ZenHub and Microsoft tools waiting to be connected. Youll help shape what project management looks like next. If youre looking for a PMO or a ready-made playbook this role will frustrate you. If youd rather build it with AI keep reading.

This is a junior-to-mid role with real scope. Youll work alongside the PM lead (a former developer who handles strategy and cross-team alignment). You own the day-to-day: tracking reporting and team interaction. AI is how you scale it.

What Youll Do

• Embed with four engineering teams. Attend dailies across APP ML DATA and INFRA. Learn what each team ships and where they get stuck. Credibility comes from understanding the work not tracking it from a distance.

• Build AI-powered project operations. Replace manual status tracking with automations that pull from real activity data. The goal: exec-ready reports the CTO can use without asking anyone for an update.

• Become the cross-team interface. Connect teams that depend on each other surface blockers early and keep stakeholders informed without requiring your lead in every meeting.

• Own reporting with judgment. AI can summarize activity; it can also produce noise disguised as insight. Youll build reporting that earns trust because you understand the underlying work well enough to catch when somethings wrong.

• Improve how delivery works. Identify bottlenecks propose process changes and run experiments. Some will stick. Some wont. Thats expected.

What Success Looks Like

First 3 months: You understand the product the teams and how delivery works at QI. Youre attending dailies building relationships with engineers and spotting your first opportunities to improve how things work. No hard KPIs here. Success means you can explain what each team does and why it matters.

By 6 months: Youre actively building automations. AI-powered tracking and reporting processes are live and trusted. Trusted means your lead doesnt double-check every output because youve demonstrated the judgment to know when a report is accurate and when its off.

By 12 months: Auto-generated status and risk reports flow from real development activity. Cross-team dependencies are visible without anyone having to sit in every meeting. Youve taken on more scope because youve earned it.

AI-First in Project Management

AI is an operating principle at QI. Every workflow you build should reflect that. For a technical PM three principles matter most.

AI as your operating system. You use AI tools daily to draft reports analyze project data build automations and scale what one person can track. This is how you work by default. At a 40-person company theres no PMO to manage. Youre the one making manual overhead disappear.

Evaluate integrate repeat. You dont wait for someone to hand you a tool. You find project management and automation tools test them against real problems (pulling data from GitHub correlating ZenHub tickets with deployment activity generating stakeholder summaries) and adopt what works. You have opinions about which tools are good and why.

Define success before you ship. Every automation and process change has a clear success metric before it goes live. AI makes it easy to build fast but building the wrong thing faster doesnt help. You know the difference between this looks impressive and this actually works.

What Youll Bring

Must-haves:

• AI fluency. You use AI tools daily as part of how you work. Youve built something with AI: an automation a workflow a prototype a tool. You can walk through what you built why you built it and what you learned.

• Technical background. You understand how software gets built. You know what branches are how GitHub works and what a deployment pipeline does. You can hold a conversation with a developer about their work without faking it. No CS degree or PM certification needed; what matters is that engineers take you seriously.

• Communication and facilitation. This role sits between four engineering teams and the rest of the company. You bring people together and make sure the right stakeholders know what they need to know without turning every update into a meeting.

Nice-to-haves:

• Python scripting or light coding ability (useful for building automations especially with AI assistance)

• Cybersecurity or threat intelligence domain knowledge

• Experience with ZenHub Microsoft Teams/SharePoint/Lists

• Prior experience at a startup or early-stage company where nothing was fully defined

What We Offer

• Shape something early. The PM function for this new agentic environment is being built right now. The automations you create the processes you test and the reporting you set up will become how QI operates as it grows.

• Visible impact at 40 people. Theres no middle management absorbing your contributions. What you build the whole company uses.

• AI-native environment. QIs products are AI-powered intelligence tools. The company practices what it ships: AI is how every team works and this role is at the center of that transformation for Technology.

• Growing autonomy. Start close to the PM lead earn independence through demonstrated judgment. The more you prove you can own the more you will.

• Mission-driven work. QI provides cyber threat intelligence to organizations including ENISA (the EUs cybersecurity agency). The intelligence protects financial services energy infrastructure defense and government institutions across Europe.

• Remote-first European identity. Work from Spain or Italy. Cybersecurity Made in Europe label.

Frequently Asked Questions

Is this just a project admin role No. Youre not taking meeting notes and updating Gantt charts. Youre building the systems that replace that kind of work. The mandate is to automate project tracking using AI and produce reporting that executives actually use. If you want to follow a predefined process this isnt the role for you. If you want to help build one it is.

Whats the growth path You start working alongside the PM lead who handles strategy and cross-team alignment. As you demonstrate judgment and earn trust you take on more scope and autonomy. The company is growing and the PM function is being built now. Where this role goes depends on you.

How technical do I need to be Technical enough that engineers respect you. You should understand version control deployment workflows and how engineering teams deliver software. You dont need to write production code but you should be comfortable scripting with AI assistance and building integrations between tools. If the phrase pull request means nothing to you this isnt the right fit.

We welcome applications regardless of gender nationality ethnic origin religion disability age or sexual identity. Diversity is key to producing high-quality intelligence.