Senior AI Engineer — Exploration & Prototyping

This is us 

Kaltura’s (NYSE:KLTR) mission is to power any video experience for any organization – live, on-demand, or real-time. We not only want to make using video simpler, but we also want to better people’s lives through video. Founded in 2006, Kaltura is now a global leader in the video market with millions of people using our products daily to teach, learn, watch, connect, and collaborate. Among our customers, you’ll find more than 1000 global, well-known organizations.    

15+ years since starting the company, we continue to foster a diverse and collaborative work environment where everyone gets a say. Our team is currently 700+ people, and we’re still growing. We have offices in New York, London, Singapore, and Tel Aviv, but our technology is all in the cloud. 

Kaltura has a fast-paced environment where initiative is always encouraged. Together with our hybrid work model and flexible state of mind, you get the right conditions for creative juices to flow freely. Thanks to our long line of products, cultivation of rich collaborative culture and care for each Kalturian, you’ll never run out of room to grow and evolve.   

If you don't meet 100% of the requirements below - that's okay, nobody's perfect! We believe in hiring people, not just a list of skills. We encourage you to apply if you think this is a role that would make you excited about coming to work every day. 

Requirements

The Role

You explore the questions the platform cannot move forward without. Whether a transport protocol change is worth the migration. How agent memory should be structured. Which LLMs and libraries belong in production and which are a year too early. These decisions are expensive to get wrong and impossible to make from documentation, so someone has to go and find out.

That is this role. You take an open question, run a focused spike, and come back with numbers and a recommendation. You read the source of the frameworks you evaluate rather than trusting their marketing. You build prototypes to settle arguments.

You do not own a subsystem and you do not ship to customers, which is exactly what protects the work: exploration inside a delivery team always loses to the sprint. You sit alongside the platform, research, and forward-deployed teams, you borrow their context freely, and your output is evidence they can act on.

You will be trusted with real influence early. The recommendations you write become the architecture other people build against, so the bar is not a working demo but a defensible conclusion, including the ones that say no.

What You'll Do

Run technical spikes that close open decisions, covering agent orchestration frameworks, real-time transport, memory protocols, agent interoperability standards, LLM selection and routing, evaluation harnesses, and the production library and stack choices underneath all of it.

Build prototypes to de-risk, standing up something real quickly, proving or disproving the thing in question, and moving on without becoming attached to the code.

Read and evaluate unfamiliar codebases, going into the source of a candidate framework to find out whether it can actually support what we need rather than what its documentation implies.

Design the measurements that make a decision defensible, building the harness, running the comparison, and reporting latency, cost, and failure behavior honestly.

Own build-versus-adopt recommendations for platform infrastructure, frameworks, and libraries, including a clear statement of what it would cost to be wrong.

Write the recommendation down. Every spike ends in a short, decisive document another engineer can act on, with the evidence, the rejected options, and the reasoning behind the call.

Hand off cleanly, transferring what you learned to the team that will own the capability in production, and staying available while they pick it up.

Track the landscape across agentic infrastructure, real-time frameworks, and adjacent AI tooling, and bring forward the things that genuinely change what we can build.

What You Bring

Required

B.Sc. in Computer Science (or equivalent technical field), mandatory.

7+ years of industry experience in software, ML, or research engineering roles, with real ownership of production systems.

Genuine technical breadth. You have worked across backend services, runtime, and infrastructure, and you are comfortable close to ML systems without needing to own the models. You can hold several unfamiliar domains at once.

Strong Python skills, and the ability to get something real running quickly.

A track record of technical evaluations that led to decisions, where you compared real options, produced evidence, and the organization acted on the result.

Evidence over intuition. You have designed benchmarks or measurement harnesses, and you can describe a time you were convinced something would work and the numbers said otherwise.

Experience with real-time, streaming, or latency-sensitive systems.

Hands-on experience with LLMs and agentic systems, including orchestration, tool calling, and how these systems behave and fail in production.

Comfortable working as an individual contributor without a team, self-directed, and able to finish. Exploration that never lands is the failure mode of this role.

Experience in a fast-moving SaaS company and in cloud environments (AWS, GCP, or Azure).

Strongly Preferred

Experience with voice or real-time agent frameworks such as Pipecat, LiveKit Agents, or equivalent.

Experience with WebRTC, media transport, or streaming infrastructure.

Experience with agent memory systems, MCP, or agent interoperability standards.

Comfortable reading and judging research literature, and translating it into a practical recommendation.

Open-source contributions, public technical writing, or published evaluations.

Early-employee or founding-engineer experience, where evaluating the whole stack was part of the job.

M.Sc. in Computer Science, Machine Learning, or a related field.

The perks:

1. Hybrid, flexible work environment  
2. Extended private health (including mental) insurance  
3. Personal and professional development programs 
4. Occasional Cross company long weekends