About Newxel
Newxel is an AI-native talent solutions company. We provide talent solutions and close engineering roles in the format that works best for the client: from hiring specialists directly into the client’s staff, to engaging engineers through our European hubs, to Employer of Record services. Whether it is a single position or a full R&D centre with dedicated labs.
We have been on the market for nine years, with revenue of about $20M, six legal entities, and clients such as Check Point, HiBob and Renesas. Our platform screens 1,000+ candidates in under 10 minutes, and we handle engineer recruitment and hiring ourselves.
Behind this sits our own agent platform: a runtime, a compiler and an organisational memory on Google Cloud. Our business agents run on it in production today: candidate sourcing, CV generation, vacancy creation, policy control and the Copilot our teams work with in Slack. The next step is to turn the platform into a product: client-facing services built on it, and agent integration for other companies.
Why this role exists
The platform works and runs our agents in production. Our CEO designed and largely built it, and today he is the only person who changes its core. At the same time, the platform is becoming a product. We’re connecting our first client-facing service to it; a detailed visual Agent Studio is designed and waiting to be built, and the list of improvements is long.
We are hiring an engineer to take over the platform, turn the CEO’s architecture and product vision into efficient systems that work in production, and lead the team that builds it.
What you will own
The platform core. Runtime, compiler, organisational memory, tool integrations, the external API for client-facing products, identity and permissions. In your first two weeks, you study the platform and agree with the CEO on a 30/60/90-day improvement plan. From then on, the plan, its delivery and its outcome are yours.
Production. A platform that is fast, reliable and economical to run: regular releases without the CEO’s involvement, safe rollbacks, clear numbers for failures, stuck runs and cost per run.
Agent Studio. The visual environment where people design agents, follow their runs, read their memory and manage permissions. It is designed and mocked up on real data. You lead building it and rolling it out, in parallel with the core.
The engineering team. The platform engineers report to you. You plan their work, review it, decide their access and scope, unblock them and grow them. When a component needs more people, you define the role and hire together with Recruitment Operations.
Security of code and knowledge. You build and run the controls: access to repositories, documents and data by role; secrets and their rotation; personal data in memory and logs; rules for AI tools on company data; clean offboarding.
The technical gate for agents. Our agent factory builds business agents as a separate function. You set the platform rules every agent must satisfy and run the technical review before an agent reaches production, regardless of who built it.
How you work with the CEO
The CEO holds the product and architectural vision and moves fast. You take that vision, challenge it with arguments where you see risk, and once a decision is made, you turn it into working code. You do not rewrite the platform to your own taste, and you do not work around it. A short list of architectural principles changes only by written decision from the CEO; everything inside them is yours to decide.
What you will not do
You do not own the product scope or the agent portfolio: those sit with the CEO and the agent factory. You do not write business specifications for agents. You do not change architectural principles on your own.
First 90 days
The outline below is our starting point; you confirm the dates in your 14-day plan. In two weeks, the 30/60/90-day improvement plan is agreed with the CEO. In 30 days, you have made your first
