Jasper Innovation & Technology Culture

What types of products or services does your engineering team work on/create? What problem are you solving for customers?

At Jasper, our engineering team builds tools that help enterprise marketing teams move from ideas to impact faster — without losing their unique brand voice. Our platform includes Jasper IQ, which learns a company’s style, tone and knowledge base so every piece of content sounds authentically on-brand; Canvas, an AI-assisted editor that helps teams brainstorm, draft and refine ideas in real time; and Agents, customizable AI workflows that take care of repetitive content and marketing tasks.

The problem we’re solving is one nearly every modern marketing team feels: There’s more content to create, across more channels, for more audiences — and scaling high-quality content consistently is tough. Jasper gives teams the best of both worlds: speed and scale from generative AI, paired with the context and control needed to stay creative, strategic and on-brand.

Tell us about a recent project where your team used AI as a tool. What was it meant to accomplish? How did you use AI to assist?

Jasper is an AI-native company, so AI plays a role in nearly every stage of how we build, from early concepts to deployment. A recent example is Jasper IQ Audiences, a feature that helps customers create LLM-optimized audience profiles. The goal was to make it easier for marketers to generate content that resonates deeply with specific segments.

We used AI throughout the project. During design, AI tools helped our product and design teams explore multiple interface ideas and user flows quickly, almost like having an extra designer in the room. During development, our engineers used AI pair-programming to accelerate coding, improve quality and speed up iteration. And in the refinement phase, we used AI to analyze and optimize how audience data was structured, ensuring profiles were clear, accurate and effective for downstream content generation. The result is a feature that embodies our approach at Jasper — powered by AI, built with AI and designed to help marketers work smarter and faster.

What would that project have looked like if you didn’t have AI as a tool to use? How has AI changed the way you work, in general?

Without AI, the buildout of Audiences would have taken significantly longer. AI speeds up nearly every part of our process, from exploring design concepts to writing and reviewing code to fine-tuning how audience data is structured. Without those tools, our team would have spent far more time on manual coding, testing and iteration, slowing down the entire release cycle.

More broadly, AI is embedded in almost every facet of how I work. I use it for research, brainstorming, development and even in creating materials that help educate and enable the field. It helps me move faster, test ideas more efficiently and focus more time on strategy and problem-solving rather than repetitive tasks. At this point, it’s hard to imagine working any other way. AI has become a core part of how we build, learn and deliver at Jasper.

How does your team stay ahead of emerging technology trends while scaling fast?

We build experimentation into the structure of how we work. I co-lead our front-end special interest group with Thibaut, a self-organized group of engineers who pick up problems they care about to keep the codebase in good shape. We don’t fix tech debt just once; our goal is to improve the underlying process so things stay healthy as we grow.

Knowledge-sharing is continuous rather than scheduled. We have dedicated Slack channels for AI topics, a learning and development budget that lets engineers trial new tooling directly, and “Demo Derbies” and hackathons where the bar is “Show something rough and real.”

What makes it work culturally is that our CEO, Timothy, has made integrating AI into how you work part of how you’re evaluated. You might expect this to create pressure, but it hasn’t, because the expectation comes with real support: dedicated time, tooling budget and a culture where sharing half-finished experiments is celebrated.

What recent product or feature are you most proud of — and what impact has it had?

One I’m really proud of is the end-to-end agentic development workflow we’ve built internally and rolled out over the past two weeks. As the engineering directly responsible individual for our design system, I personally felt the friction on both sides: designers waiting on engineer availability for design system changes, and my own engineering capacity being pulled away from product work. It was one of those problems that seemed solvable, so we went and solved it. 

Once a ticket is created in Linear, the whole loop just runs. The agent picks it up, opens a pull request, and notifies the right people to review, and if they request changes, it makes them automatically. No one is orchestrating any of it. 

What makes it meaningful is that non-engineers can now participate in that loop directly. Designers can ship design tweaks without waiting for someone to have capacity. In just the first week, the agent initiated work on 120 PRs across the whole product, and we’re only just getting started.

How do you create a culture where innovation and experimentation are encouraged daily?

The core principle we operate by is demos over meetings. If you have an idea, you build a rough version first and share it, not create a slide about it. In practice, this shows up every day. Someone drops a Loom of a half-baked idea in Slack, a PR gets shipped behind a flag before it’s “ready,” and a designer opens a ticket and just runs with it. Part of why people feel safe doing that is because we’ve invested in the foundations: quality code reviews, strong standards and patterns that hold up. That safety net is what makes moving fast feel sustainable rather than reckless. 

A lot of this flows directly from Timothy. In a recent company-wide message, he put it plainly: “Our biggest risk is no longer building the wrong thing — it’s timidity.” The question has shifted from, “Can we build this?” to “Is this worth building?” That reframe has genuinely changed how the team moves.