Skip to content

Developer relations · Developer experience · Product

Hire me

I’m Liran Tal. I help developers succeed with products: building trust through useful tools, education and community, and bringing their experience back into the product.

At Snyk I lead Developer Relations and Community, combining people leadership with hands-on research, open source, education and growth. I’m interested in bringing that mix to DevRel leadership, developer experience and product roles.

Numbers at a glance

A few signals of how I reach developers and build things they can use.

  • 37% of new visitors

    Snyk Advisor brought in 37% of Snyk’s new website visitors by Q1 2022, alongside 500+ monthly signups. I led it from launch through its growth phase.

  • Node Weekly top articles

    My Snyk articles ranked #3 among Node Weekly’s most-clicked links of 2024 and #7 among its most popular links of 2022.

  • 250+ speaking engagements

    From JSNation US to Open Source Summit Europe, I use live demos and practical stories to bring security to developer communities. Explore speaking archive.

Experience in practice

How I bring developer communities, useful education and product work together at Snyk.

  • Community-led security guidance: I worked with OWASP Cheat Sheet Series leaders Jim Manico and Jakub Maćkowski on the OWASP npm security cheat sheet, bringing into the community a guide I originally co-authored at Snyk with Verdaccio core maintainer Juan Picado. I also collaborated with Linux Foundation Director of Open Source Supply Chain Security David A. Wheeler on OpenSSF Secure Coding Labs, supporting hands-on security education.
  • Responsible disclosure across the ecosystem: As a volunteer in the Node.js Ecosystem Security Working Group, I helped triage hundreds of reports and work with maintainers and researchers. I advocated for Snyk to take on the ecosystem disclosure program, providing a path to verify, coordinate and disclose vulnerabilities.
  • Independent community reach: My JavaScript and Node.js articles and open-source projects, including npq, have regularly featured in Node Weekly over the years. My Snyk articles ranked #7 among its most popular links in 2022 and #3 in 2024. Across my time at Snyk I’ve published more than 322 articles, turning research and developer questions into practical guidance.
  • Tools developers can use: I build tools that turn security insights into practical workflows: lockfile-lint and is-website-vulnerable; anti-trojan-source and its ESLint plugin for detecting Trojan Source attacks; url-sheriff for URL validation and SSRF protection; and an AI-BOM visual viewer for exploring AI bills of materials.
  • From developer value to growth: I led Snyk Advisor from launch through its growth phase, and built an integration that brought security insights into WebPageTest. Both Growth Engineering initiatives met developers where they already worked and connected useful experiences to product discovery.
  • Research developers can act on: I architected Snyk VulnBench, co-authored ToxicSkills, and translated MCP security findings into practical guidance for building secure MCP servers. My Doris MCP disclosure showed how a read-only mode could be bypassed; I’ve also published a framework for evaluating MCP server security.

Questions from recruiters, hiring managers and future teammates

  • Tell me about yourself.

    I’m a developer advocate, open-source maintainer, author and security researcher. At Snyk, I lead Developer Relations and Community, combining people management with hands-on research, education and engineering. My work ranges from founding growth and community programs to building open-source tools and investigating AI security. I like working where a developer’s experience meets a product’s ambitions: getting hands-on, explaining what matters and bringing what I learn back to the people building it.

  • What roles are you looking for?

    I’m interested in roles where I can lead by example, contribute hands-on and make a tangible impact on the product and its developers. That could mean a leadership role such as VP of Developer Relations, a senior developer experience or advocacy role, or product management focused on developer and agentic experiences, grassroots adoption and product-led growth. I’m at my best when I can set direction, build alongside the team and help developers succeed.

  • What would you bring to a DevRel leadership role?

    I lead Developer Relations and Community at Snyk, managing and growing Staff Developer Advocates and Security Relations leads across the US, Europe and APJ while remaining hands-on. I’ve mentored and promoted advocates, founded programs and worked across product and field teams. I bring technical depth, developer empathy and an eye for business outcomes, with clear priorities and room for people to do their best work.

  • Are you still hands-on?

    Yes. My current role combines people management and individual contribution, roughly 60/40. I architected Snyk VulnBench end-to-end, from the agent harness and vulnerable code corpus to the reporting pipeline.

    I’ve published three technical books on Node.js secure coding and disclosed over 40 CVEs through my own bug bounty work and security research. I routinely build intentionally vulnerable educational apps to demonstrate MCP server weaknesses and Agent Skills attack vectors.

    I also build internal programs and engineering projects using coding agents including Claude Code, Cursor and Codex, and maintain open-source tools. Staying close to code makes the strategy and education better.

  • Tell me about a community program you built.

    I founded Snyk Ambassadors and SnykLIVE from zero. The ambassador program began with eight people selected from 96 applicants; it continues today under Snyk’s Customer Advocacy team, with ambassadors across major customer accounts and worldwide events.

    SnykLIVE started as the team’s first video-based community presence and grew into an established, high-output production on Snyk’s YouTube channel. I also contributed to The Big Fix, Snyk’s community security fix-a-thon, which won a DevRel Award for Best DevRel Initiative. In 2023, participants contributed more than 597,000 security fixes.

    The Big Fix results

  • Can you give an example of a developer-led growth initiative?

    I conceived and built a WebPageTest integration that brought Snyk vulnerability data and HTTP security header analysis into a tool developers already used. Within five months it became Snyk’s top referral traffic source; over two years it was the company’s second-largest referral source.

    I also pioneered Snyk Advisor through its growth phase. By Q1 2022 it drove 37% of Snyk’s new website visitors and more than 500 monthly signups. Its package-health insights have since reached more developer surfaces, including the API and the official Snyk MCP Server.

    We built Vuln Cost, a VS Code extension that surfaced dependency vulnerabilities as developers coded. It was available by April 2020; an archived Marketplace listing recorded 28,500 installs. Its capabilities carried into the official Snyk Security extension.

    Vuln Cost on GitHub · Package health in Snyk MCP

  • How have you used AI to improve a team’s work?

    In 2023 I built ContentGPT, an AI-assisted platform for outlines, drafting, keyword planning, FAQs and security-incident articles. It reduced production time and helped the team produce more than the external content agency it replaced. That approach carried into the team’s later Claude Code-based content tooling.

    I also built an internal tool using the Mastra AI framework to help evaluate hundreds of conference CFP submissions, filtering, prioritizing and moderating proposals to support the content program. Separately, I architected Snyk VulnBench to evaluate how reliably AI coding agents and LLMs find real vulnerabilities.

  • How do you turn technical research into developer value?

    My work on npm lockfile security is one example. I researched how lockfiles can be abused, explained the risk in a Snyk article and maintain lockfile-lint, a tool developers can use to check for untrusted sources. The point is to connect an insight to a practical action, not leave developers with a scary headline.

  • How do you approach developer experience and product management?

    I start by using the product and looking for friction from discovery through continued use. At Snyk, my hands-on research and user-zero feedback have helped improve Snyk Code detection, including secret-detection rules and false positives and false negatives in code analysis. I’ve also shared ongoing feedback on the Snyk CLI and its developer experience. I bring those observations together with developer feedback and product data, then work with engineering and design to prioritize improvements and check the results.

  • How do you think about product-led growth?

    I pioneered Snyk Advisor from launch through its breakout growth phase, then mentored the teammate who carried it forward. It became Snyk’s largest website traffic generator within three months and, by Q1 2022, drove 37% of new website visitors and more than 500 monthly signups before graduating into the core product. That experience shaped how I think about growth: make something genuinely useful, connect it to a clear path to value and measure what happens.

  • How would you measure DevRel?

    At Snyk, I measure programs against what each is trying to accomplish. For AI advocacy and community, we track meetup RSVPs and returning participants, as well as membership growth across meetups, events and newsletter sign-ups. For AI Security Engineer certification, we count certified developers and badges earned, and track whether they came through events, the online platform or virtual webinars.

    For forward research and security evaluations, we track citations, analyst mentions and LLM share of voice for our work. For Growth Engineering, we look at adoption, popularity and the signals those initiatives bring into the product. Snyk Advisor, for example, had targets for indexed pages, new visitors and acquired users.

    I use those measures alongside developer feedback to understand whether a program is earning attention, helping people and creating useful outcomes for the product.

  • How do you work with product, engineering and marketing?

    I see DevRel as a bridge. At Snyk, research and user-zero feedback informed the product, while competitive intelligence and positioning helped field teams in conversations with security and platform teams. I can work through technical details with engineering, bring developer feedback to product and turn research into useful stories with marketing. Shared goals and honest feedback make that work.

  • What does developer trust mean to you?

    Show your work, be truthful about limitations and make the material useful even when someone does not buy a product. As a maintainer and security researcher, I know developers notice when an example has not been tested or when a claim goes further than the evidence. Trust is earned in those details.

More questions people ask before hiring me

  • What kinds of developers and products do you know best?

    My work spans JavaScript and Node.js developers, open-source maintainers, application security practitioners and people building with AI agents and developer tools. I’m especially interested in products where technical depth and an accessible developer experience both matter.

  • Can you speak and teach to different audiences?

    Yes. I’ve taken part in more than 250 speaking engagements across conferences, meetups and podcasts, as well as webinars and workshops. I often use live demonstrations to make a technical problem concrete and adapt the explanation to the audience.

  • What would you focus on first in a new role?

    I’d listen to the team and its developers, use the product myself, review the existing data and learn what the business needs to achieve. From there I’d identify a small set of opportunities, agree on outcomes and build a plan with the people who will execute it.

  • How do you balance community needs with business goals?

    I look for the overlap: helping developers solve real problems can build the trust and adoption a business needs. When interests diverge, I think it is important to be transparent about the trade-off and bring evidence from the community into the decision.

  • Do you only work on security?

    I’m excited by the tools and platforms developers use to build: agentic coding and AI experiences, developer tooling, web infrastructure and cloud platforms. I enjoy getting hands-on with emerging technology, making it accessible to developers and helping shape products around their needs. Security is a deep area of expertise I bring to that work, alongside developer education, product thinking, community and technical storytelling.

Let’s build what developers and their AI agents will love

If you’re building for developers and think there could be a fit, I’d love to hear about the role, the team and the problem you’re solving.

Get in touch on LinkedIn · Other contact options