Guy Podjarny on Snyk, Product-Market Fit and Building Durable Advantage

Harry Stebbings welcomes Guy Podjarny, founder of developer-security company Snyk and an angel investor. Podjarny says he would rather risk failure than abandon the goal of engaging developers in security. His discussion of Snyk and his investments reflects his financial and professional interests.

Podjarny describes working in Israeli military cyber units before joining an application-security startup that was acquired, ultimately by IBM. He moved to Canada, then founded web-performance company Blaze, which was acquired by Akamai. He served as Akamai's CTO and moved to London.

His experience in application security and the early DevOps movement came together in Snyk. He wanted to bring the ethos of independent development teams and fast iteration into security. His account connects the new company to lessons from his earlier startup and angel investing.

Asked why Israeli military units produce entrepreneurs, Podjarny suggests they select capable people, expose them to intense challenges and create networks that persist afterward. He also attributes a willingness to question conventions to Israeli culture. These are his generalizations and personal interpretation, not a study of outcomes.

He contrasts the technical strength he found in Tel Aviv with product discipline and developer thought leadership in London. Speculating about open-source participation, he mentions language, working habits and patience in collaboration. He acknowledges that his comments about national styles are stereotypes and do not describe everyone.

Podjarny rejects the idea that serial entrepreneurship is overrated. He considers entrepreneurship a profession, with lessons in fundraising, first hires and finding product-market fit that are difficult to acquire elsewhere. Repeatedly entering uncomfortable situations can accelerate learning, although he does not claim every repeat founder succeeds.

Fundraising matters if a company needs outside money, he says, but investors should prize company-building ability over fundraising alone. He separates selling an idea and persuading people of its value from negotiating the terms of a deal. Founders can delegate parts of deal-making, but someone on the founding team must communicate the vision.

He describes his own strengths as a combination of empathy and analysis: understanding what others need, breaking a problem into components and explaining the result. He does not claim to be the best programmer or mathematician; he values combining disciplines and extending his impact.

Stebbings asks how he anticipates change. Podjarny says he breaks developments into first principles, asking why they happen rather than merely noticing them. For DevOps, he identifies independent teams, continuous processes and a blameless culture as concepts that help him reason about implications for security.

Reducing complexity to components allows a team to build a larger picture, then drill into details as needed. He also asks product managers and founders whether a capability will be more or less necessary in five years. The answer need not prohibit a tactical product, but it should shape the investment and expectations around it.

For a new company's core proposition, he wants a reason to believe demand will grow by the time the company reaches scale. Stebbings notes how difficult forecasting is in fast-moving AI. Podjarny agrees, describing uncertainty around LLM limits and suggesting that even a two-year timing error can determine a startup's fate; these are his 2023 judgments.

His approach is “big vision, small steps”: identify a meaningful destination, choose the next step and have a tentative idea of the one after it. Ideally each step creates value even if progress takes longer or the path changes. He does not suggest that timing can be predicted precisely.

On market size, Podjarny distinguishes a research firm's current category estimate from the potential value a product could create. With Snyk he considered the number of developers and the importance of secure software, rather than treating an existing application-security category as a permanent ceiling. That is his founder's thesis, not an independent market estimate.

Investors still need a market-size argument, so founders should explain their reasoning instead of dismissing the question. Podjarny suggests starting with the value for customers, the number of people who need it and the dollars they might pay, while acknowledging uncertainty about how the market will evolve.

He compares possible markets for Blaze. Quality assurance could use similar technology, but he perceived limited spending there, whereas web performance had an existing market. Snyk could later add quality-related capabilities, but an initial business needs either present spending or a credible explanation of why spending will emerge.

Being first to market is ambiguous, he says: Snyk was not first in application security. What matters more is leadership and meaningful differentiation. Being early with a new approach may help create those advantages, but timing alone is not enough.

Messaging forces founders to distill what they do into a customer need. Podjarny sees two common errors: loving a narrow technical feature without understanding the whole use case, and promising a broad platform before solving a specific problem. Customers care about the problem solved, not the product's architecture for its own sake.

Brevity forces prioritization. He argues that writing a clear message is not just simplifying for an audience; it helps the team focus and can change what it builds. At Snyk, the central idea was enabling developers to address security, with open-source security as the initial product market.

Messaging evolves as a team learns to express itself, the product changes and the market matures. Snyk moved from “use open source, stay secure” toward “develop fast, stay secure.” He says an early need to convince companies that developers could own security later shifted toward questions of implementation and scale.

For a horizontal product serving many kinds of customers, Podjarny advises choosing an initial group and serving it exceptionally well. The slice should be large enough to sustain the company and provide a path to adjacent markets, but small enough to become a force within that community.

A community whose members talk to one another can generate momentum: users hear about a product at events or carry it to a new employer. The same principle can apply to a developer ecosystem, HR leaders or finance professionals. He sees a focused use case as both a product and a go-to-market choice.

Snyk's developer focus went too far in one early detail: for a period, a security professional without a GitHub account could not register. Podjarny says the company was so focused on winning developer adoption that it did not adequately account for the other audience.

Developer adoption arrived, but revenue did not automatically follow. Podjarny had believed security was close enough to an existing budget that it could eventually monetize, yet underestimated the gap between user enthusiasm and a commercial business. Opening online payments initially produced only a tiny trickle.

He recalls that roughly two years in, after millions of dollars spent and tens of thousands of users, Snyk was at about $100,000 in annual recurring revenue. An adviser warned that it might be another developer tool loved by users but unable to earn money. The figures are his recollections, not independently audited results.

The warning made him reconsider his conviction. He decided that winning developers over to security was the problem he wanted to solve, rather than pivoting to a conventional security-only product. His persistence was tied to a particular thesis, not a rule that every struggling startup should continue.

A wave of investor interest led him into a preemptive fundraising process, but many investors declined when they saw usage without revenue. He cautions founders that unsolicited interest can be flattering and that approaching everyone too quickly may leave few options. He recalls the period was also personally difficult because his father-in-law died.

Podjarny credits Ed Sim and Boldstart with providing a smaller bridge on the best valuation offered, allowing Snyk more time. He recalls that after reaching $100,000 ARR, it grew to $650,000 four months later and $4.5 million a year after that. These are his retrospective company figures and involve a continuing investor relationship.

When deciding whether to persist, he recommends a theory of why the current approach is not working and what will change it. A list of isolated missing features is not enough. At Snyk, he came to understand that developers wanted depth in a technology stack while security teams needed breadth and governance across an organization.

The company expanded support across technology stacks and addressed security buyers' needs while maintaining developer adoption. Podjarny argues that founders should test the underlying theory—whether the issue is reach, the product or the distinction between buyer and user—rather than simply trying random directions.

Stebbings observes that tighter budgets were shifting purchasing power toward finance leaders. Podjarny calls the period difficult for product-led companies but expects the longer-term need for empowered teams to remain. This was his 2023 market view, and he notes that founders have to make case-by-case decisions.

A company can emphasize cost savings in the near term, but he warns against being pulled entirely away from a product-led model if that is how the market is best served. Users need help explaining a use case and its value to buyers. Features and return-on-investment calculations matter insofar as they communicate customer value.

The pair discuss bundling versus specialized tools. Podjarny says a broad platform may offer greater aggregate value, while a specialist can win when it is sufficiently better at a specific job. He discloses that Snyk benefited from consolidation after developing broader coverage; his comparison reflects that business position.

He cautions that a product only modestly better than a bundled alternative must justify the overhead of another vendor. A much larger improvement can make a specialist compelling, but the relevant threshold depends on the customer and how clearly value is demonstrated.

On “painkillers” and “vitamins,” he says the distinction depends on the primary value proposition. A productivity tool that credibly saves substantial resources may be an urgent purchase, while a small, hard-to-prove improvement can feel optional. Automation can be easier to demonstrate than an indirect analytics benefit.

He uses a matrix of pain and frequency. High-pain, infrequent problems require being present when the need arises; frequent, low-pain problems require low adoption friction. Frequent, high-pain problems already have some solution, so differentiation matters, while low-pain, infrequent problems are unlikely to support a product on their own.

Podjarny values Hamilton Helmer's Seven Powers framework for thinking about value that is superior, significant and sustainable. His concern is a company that becomes somewhat valuable but gets stuck at a modest revenue level because the product is easy to copy or depends entirely on execution.

He says a very early startup usually has little defensibility, aside perhaps from unusually scarce knowledge or counter-positioning against incumbents. Founders should devote most early attention to product-market fit, but investors can still ask what defensibility might emerge if the company succeeds.

Possible sources include networks, accumulated data, switching costs or an approach an incumbent is reluctant to adopt because it threatens its existing position. Podjarny uses Snyk's developer-first approach as a counter-position to traditional security selling. He treats these as theories to test, not automatic moats.

Once a product works and begins to scale, priorities can shift toward strengthening the relevant advantage—for example through data rights, viral mechanisms or stickiness. He cautions against letting an abstract defensibility exercise displace the immediate work of making something valuable.

Stebbings describes an investment with $1.4 million in ARR but slow growth and asks whether it has product-market fit. Podjarny defines fit as demand exceeding the company's capacity to satisfy it. He acknowledges the term is imprecise and distinguishes Snyk's early product-user fit from its later product-buyer fit.

He returns to the questions: who receives value, are there enough such customers, and will they pay? Stebbings asks whether some powers are stronger than others. Podjarny says terms such as brand and process power can be claimed too loosely unless they represent a real, significant and durable advantage.

He identifies Snyk's developer-first counter-positioning and a product-led process as potential strengths against traditional security vendors. He argues that the process is embedded across culture, product and go-to-market and would be hard to copy. He also says that advantage may not hold against developer-tool competitors; this is the founder's assessment.

Snyk's team compared categories of competitors and assessed its capabilities against the tests of superiority, significance and sustainability. Podjarny says even the discussion can sharpen judgment. The difficult part is selecting one or two priorities instead of declaring everything important.

As a company expands, he asks which existing strengths will help it enter the next product or audience. If none apply, he recommends pausing: otherwise the company may be competing on operational execution alone. The framework is a tool for understanding differentiation, not a substitute for judgment.

Stebbings says speed of execution is a key difference he sees among his investments. Podjarny frames speed as iteration: faster learning helps a team approach fit, provided it is learning in the right direction. He rejects the assumption that a team can work in isolation for a year and emerge with a perfect product.

Feedback must match the intended go-to-market model. A team hoping to build a self-service, community-led product may learn the wrong lessons if all its feedback comes from a few top-down conversations with CTOs. He supports early customers who help shape a product and says they should receive an appropriate benefit for their time.

Asked whether Snyk's growth ever flattened after fit, Podjarny says its major flat period came earlier, followed by acceleration until the more difficult market of 2023. He describes Snyk as well positioned with cash and a security need, while acknowledging changed numbers. This is the founder's account, not independently verified financial reporting.

As an angel investor, he warns against assuming a venture firm's small seed check carries the same conviction or context as an angel's principal investment. He values the diligence of co-investors but interprets it in light of their incentives and his own objectives.

He invests for a financial return but also for learning and enjoyment, asking whether he wants to spend time with the founder and whether the area interests him. He says he had made close to 100 investments over roughly a decade, with time being his main constraint. These are his personal practices, not investment advice.

Podjarny says much of his wealth remains tied to Snyk, so his exposure to venture risk is already high. He limits overall exposure and has reduced some fund allocations, while acknowledging that he enjoys risk and direct investing. This is a material financial interest in the topics discussed.

His biggest investing mistake, he says, has been choosing ideas that appear too obvious and leave little room for differentiation. He counts the leaps of faith a thesis requires: too many are unattractive, but none may indicate many competitors and an investment dependent on execution alone.

Stebbings describes avoiding investments that require a second major leap beyond an initial market expansion. Podjarny agrees that multiple uncertain transitions compound risk. Both are expressing personal investment criteria rather than a formula for predicting returns.

He sees only a modest relationship between high entry prices and eventual quality. Raising too much too early can encourage a company to accelerate before it knows what works. In the 2023 funding environment, he says founders with earlier high valuations might need to work for years before raising at the same price again.

On retaining employees through a flat round, he suggests ensuring competitive financial incentives, potentially including additional equity, along with a shared belief in the mission. The right arrangement depends on the company and investor context.

He recalls angel investor Amit Patel joining during a difficult fundraising period and credits him as an impactful supporter of Snyk. Asked about a fund he would back, Podjarny names Boldstart, which he previously identified as a Snyk investor. These are relationships relevant to his endorsements.

In quick-fire questions, he says a good idea is rarely yours alone: other smart people may notice the same changes, so there is less time to act than founders imagine. His hiring mistake was bringing in people oriented toward a much larger future company before they could meet current needs.

A painful lesson was that when someone consistently cannot succeed in a role, letting them go can be better for both the person and the company. He describes this as particularly difficult in fast-growing leadership teams. It is his managerial judgment, not a substitute for a fair process.

Handing the CEO role to Peter was hard, but Podjarny calls it a good decision. He wanted to devote more time to anticipating product direction while another leader focused on scaling the organization. He says the partnership continues to require work and was not driven by a failure to perform.

Fatherhood taught him that not everyone can be pleased when needs conflict. He applies that lesson to decisions for the broader organization while recognizing employees are adults. He calls a company a team rather than a family, while acknowledging that close working relationships make departures emotional.

Asked about angel returns, he names SecurityScorecard and Cloudinary among investments he considers strong, and mentions stakes in Synthesia and Lightdash. He does not provide a complete realized-return calculation, so the examples should not be read as verified fund performance.

He would like venture firms to use more technology to help portfolio companies succeed, rather than focusing tools primarily on sourcing deals. He thinks more systematic support could change the industry, while acknowledging uncertainty about how far existing efforts have progressed.

Looking toward 2033, he hopes to devote more time to a family foundation focused on social inequality. He describes its work in the UK and Israel as a pilot and a learning process. The stated future role is an aspiration, not a completed commitment.

Podjarny says he is motivated against tribalism and describes inclusion as a thread connecting his company-building and charitable work. He expresses disagreement with the Israeli army's conduct in occupied territory and concern about deglobalization. These are his personal political views in the 2023 conversation.

He says his relationship with money is uncomfortable: he enjoys comfort and helping family and friends but dislikes status symbols. He and his wife plan to give away their Snyk wealth, he says, while recognizing that responsible large-scale giving requires effort. Stebbings thanks him and the interview ends.