Viktor is the AI teammate. He lives in Slack and Microsoft Teams, connects to thousands of tools, and does real work for real companies: finance, marketing, ops, engineering. We're building the product that replaces half the SaaS stack.
The team is small. The scope is not.
You build Solutions Engineering at Viktor from zero. You're the technical partner on our enterprise deals: you build bespoke demos and use cases, answer technical and security questions, and run POCs and onboarding for bigger teams. It's a player-coach seat: you work deals yourself and hire the two Solutions Engineers who follow.
Our Account Executives need this on their highest-potential deals. Today engineers get pulled in, which slows product work, and AEs can't go deep enough on integrations and security on their own.
You report to Robbie O'Connor, our Chief Revenue Officer. Accounts and the sales number belong to the AEs, the support queue to User Operations, and product engineering to our engineers.
We'll be honest: the scope is still being shaped, and the enterprise motion is new. Some of the role, like post-sales support for VIP enterprise customers, gets tested in practice while you're already running live deals.
Run pre-sales for enterprise prospects: answer their technical and security questions, set them up properly when they're getting started, and keep deals moving.
Build bespoke demos and use cases for the deals that matter most.
Be the first technical touch on POCs and onboarding in place of our engineers, and build a repeatable onboarding for bigger teams.
Support VIP enterprise customers after the sale.
Hire two Solutions Engineers, one in Dublin or Warsaw and one in New York, while still working deals yourself.
By day 90:
AEs reuse a standard enterprise demo and three use-case builds.
A POC template with success criteria has run on at least two live deals.
A security and integration answer bank has cut how often engineers get pulled into deals.
4+ years as a Solutions Engineer, solutions architect or forward-deployed engineer at a PLG, API or AI company, on deals with technical buyers.
You build real things for customers: scripts, integrations and agent workflows.
You've run POCs that converted, and you can name the success criteria and the outcome.
You handle security and IT questions from buyers without overpromising.
You build with AI agents and LLM APIs, hands on.
You demo, but you don't build.
You'd promise a feature, a roadmap date or a compliance date to win a deal.
You build Solutions Engineering from zero and decide what the role is. The path from there is leading a growing SE team across Europe and the US.
Small team, high trust, low process. Decisions are made by owners, not committees. You will ship your first week. You will talk to users your first day.
We don't do alignment meetings or stakeholder syncs. We build things, see if they work, and iterate.
Why ViktorWe're one of the fastest-growing companies in the world. The product works. The market is pulling.
This is a rare window: everyone here owns something real. Not a task. A surface of the company that customers depend on.
That doesn't last forever. Right now, it's still true.
CompensationTop-of-the-market salary and the kind of ownership that only exists at this stage.
The best work happens when you're in the room. Munich, New York, Dublin, and Warsaw. Remote for some roles.
