# Anil Kumar Krishnashetty, full site content > Senior Technical Product Marketing Manager (PMM) at Bright Data, based in Berlin, Germany. Former frontend developer (SAP, One.com) and technical product manager (Contentful, commercetools). 25+ conference talks. This file contains the full markdown content of https://www.anilkumark.de/ for AI agents. Per-page markdown variants exist at .md (for example https://www.anilkumark.de/talks/bots-and-humans-devworld-2026.md). Index: https://www.anilkumark.de/llms.txt --- Source: https://www.anilkumark.de/work/ # Work ### Technical Product Marketing 1. Leading Product Marketing for [Parallels Browser Isolation](https://www.parallels.com/products/browser-isolation/) and [Parallels Secure Workspace](https://www.parallels.com/products/psw/) products at [Parallels](https://www.parallels.com/). * [Parallels Secure Workspace](https://www.parallels.com/products/psw/) * [Parallels Browser Isolation](https://www.parallels.com/products/browser-isolation/) 2. **Messaging** and **positioning** localization tools to developers and designers at [Lokalise](https://lokalise.com/). * [Developer Hub](/work/pmm/lokalise-developer-hub) * [Flutter SDK for Over the air translations](/work/pmm/lokalise-flutter-sdk) * [Software Localization Workflow](/work/pmm/software-localization-workflow) * [Lokalise Demo App - AI Emporium](/work/pmm/lokalise-demo-app-ai-emporium) * [Technical Partner Marketing](/work/pmm/technical-partner-marketing) ### Technical Product Manager Enhancing App **developer experience** at [Contentful](https://www.contentful.com/), [commercetools](https://commercetools.com/) and [bitgrip](https://www.bitgrip.de/) by providing **UI tools** and **Design systems** to build apps **quickly**. Design systems worked on * [Forma 36](https://f36.contentful.com/) * [UI Kit](https://uikit.commercetools.com/) ### Community * [Product Prototyping Meetup](https://www.anilkumark.de/product-prototyping-meetup-community) ### Frontend Experience
SAP

SAP

HR Renewal is an HR application to make HR lives easier. Lead Frontend developer Led team of 5 Frontend developers and developed the HCM HR Renewal web application. HR Renewal Application Improved productivity of the HR application.

CANTO

CANTO

Cumulus portals is a digital assets publishing platform. Portal Plugins UI plugins to build digital assets management solutions quickly. Share Easy to manage, share, and collaboration with the digital assets.

ONE.COM

ONE.COM

The web editor is a website builder to design and update website. Usability Improved Web editor usability. Speed 5 times faster way to create a customizable contact form on the Web editor.

--- Source: https://www.anilkumark.de/public-speaking/ # Public speaking ![Anil on stage at devWorld Conference 2026, slide reading "We now live in a Closed Web"](/assets/devworld-2026-closed-web.jpg) ![devWorld Conference Amsterdam, May 2026](/assets/devworld-2026-hero.jpg) ![Talk at TypeScript Berlin Meetup](/assets/Mask%20group%20(10).png) ![Pair programming usability talk](/assets/Mask%20group%20(9).png) ### Past talks #### 2026 * 🎥 [Bots & Humans: Maintaining AI agents and automation in an AI-bot web](https://youtu.be/-YJHOsvUyPc?si=zfBNfLrnI_9C7CJ9) at [devWorld Conference](https://devworldconference.com/), Amsterdam, MAY 2026 · [transcript + takeaways](/talks/bots-and-humans-devworld-2026) #### 2024 * 🎥 [Future proofing cybersecurity zero trust and secure workspaces](https://youtu.be/1OwHWfYcexY?si=8TEFWx60LIwCQH-s) at[ CyberSec Europe](https://www.cyberseceurope.com/), MAY 2024 · [transcript + takeaways](/talks/zero-trust-secure-workspaces-cybersec-2024) * [5 Key strategies for integrating Zero Trust into Cloud Architecture](https://www.parallels.com/blogs/ras/zero-trust-cloud-architecture/) at [Cloud Expo Frankfurt](https://www.cloudexpoeurope.de/), MAY 2024 #### 2023 * 🎥 [Enhance Developer Experience by Community](https://youtu.be/2rqiZ70vyG8?si=ukhojBX8rgw42QDB) at [Voxgig DevRel Meetup](https://www.voxgig.com/), SEP 2023 · [transcript + takeaways](/talks/enhance-dx-by-community-voxgig-2023) * 🎥 [Unlocking a world of accessibility: how internationalization is the key](https://www.youtube.com/live/bGLAsp5XTVA?si=wpPDNi_nTlhHhiHg), Inclusive Design 24, SEP 2023 * 🎥 [Enhance Developer Experience by Community](https://youtu.be/Zrup1x5H6yc?si=5SB9NvME9WrkeH4O), Code.talks, SEP 2023 * [Internationalizing (i18n) of your Nextjs 13 apps](https://speakerdeck.com/anilkumar/internationalization-i18n-of-your-next-dot-js-13-apps-using-i18next-enterjs-2023), EnterJS, JUN 2023 * 🎥[ Enhance Developer Experience by Community](https://www.youtube.com/live/_PNTU_uK0T8?feature=share\&t=24673), JUN 2023 * [DX is not the same as UX](https://speakerdeck.com/anilkumar/dx-is-not-the-same-as-ux), Webinale, MAY 2023 * [Enhance User Experience through Angular Internationalization & Localization for Growth](https://www.youtube.com/live/fs26vhD330U?feature=share\&t=21500), [Angular Tiny Conf](https://angulartinyconf.com/), APR 2023 * [10 Key Mistakes In Your API Docs and How to Avoid Them](https://youtu.be/uejcI5sgrIg?si=gzwRgW_gnaZF8bk7), API Conference London, APR 2023 * Podcast talk: "[_**Drive adoption of your developer platform**_](https://www.developermarketing.io/devmar-debugged/)_**"**_, [Developer Marketing Alliance](https://www.developermarketing.io/), MAR 2023 * [Pair programming is the best usability testing tool](https://youtu.be/WS8jagki5J8), UXDX online event, FEB 2023 * [UX Job Hunting Strategy](https://uxglasgow.substack.com/p/the-robots-are-coming#%C2%A7ux-job-hunting-strategy), UX Glasgow, JAN 2023 #### 2022 * Design stage localization, Push UX, Munich, NOV 2022 * [Why is pair programming the best usability testing tool for developer-focused products? ](https://speakerdeck.com/anilkumar/why-pair-programming-is-the-best-usability-testing-technique), WeAreDevelopers, Berlin, JUN 2022 * [Design stage localization](https://twitter.com/anilbms75/status/1533004818104881152), UXcamp Europe, Berlin, JUN 2022 #### 2021 * [Outcome focused Technical Product teams](https://youtu.be/L0CmQR0kfsg?t=321), Product people, Berlin, NOV 2021 * [10 key mistakes the Design System team makes, Into Design systems](https://youtu.be/PX5EW1BiOIw), SEP 2021 * [TypeScript pitfalls to avoid for great Developer Experience](https://speakerdeck.com/anilkumar/typescript-pitfalls-you-should-avoid-for-great-developer-experience), TypeScript Meetup, AUG 2021 * 🎥 [Prepare For Your Next Dream Job](https://youtu.be/GwTboIScahI), Iron hack Berlin, AUG 2021 * [Improving developer experience with Story mapping](https://youtu.be/fXUu5rm_5-A), CodeControl, JUL 2021 * [Improving developer experience with Story mapping](https://youtu.be/gYCmySKDhCc), UXPressia, JUL 2021 * 🎥 [How to land a job in Berlin, Design & Friends](https://youtu.be/T_vHaw_-rPg), APR 2021 #### 2020 * 🎥 [State of JAMstack & HEADLESS commerce](https://youtu.be/MisYXBhJs_c?t=11855), WeAreDevelopers, DEC 2020 * 🎥 [Build your dream workflow using Atlassian Forge](https://youtu.be/Dzcep4Gl7HY), Atlassian community Berlin, SEP 2020 * 🎥 [Behavior driven product development](https://youtu.be/zJxIYkbqKHs), ThoughtWorks Berlin, JUL 2020 * 🎥 [Automation quality assurance: Fragile locators](https://youtu.be/eEHe3vTrAdY), CTM Berlin, JAN 2020 #### 2019 * [Graphical interface to Voice interface](https://speakerdeck.com/anilkumar/graphical-interface-to-voice-interface), UX Scotland, JUN 2019 #### 2018 * [Graphical interface to Voice interface](https://medium.com/berlin-lean-prototyping/becoming-alexa-developer-from-visual-designer-in-just-4-hours-d3d064eb3b33), Beyondtellerrand side event, NOV 2018 * 🎥 [Talk to the inner voice of your design](https://youtu.be/1sa722XQveo), Intersection Conference Milan, OCT 2018 #### 2017 * [Prototyping with Keynote/Powerpoint](https://medium.com/berlin-lean-prototyping/5-tips-to-convert-your-keynote-into-prototyping-tool-aaa9f4615ead), Product Prototyping Meetup Berlin, SEP 2017 #### 2016 * [Introduction to Canto Cumulus Portals Plugins](https://speakerdeck.com/anilkumar/cumulus-portals-plugins-intro-and-demo), Canto DAM Summit Europe, APR 2016 * [Challenge your team to build a great product](https://www.slideshare.net/anilbms/challenge-your-team-to-build-great-product), UX Camp Hamburg, AUG 2016 #### 2015 * [The making of rapid prototype: A Web love story](https://www.slideshare.net/anilbms/the-making-of-rapid-prototype-a-web-love-story), UX Camp Hamburg, AUG 2015 --- Source: https://www.anilkumark.de/talks/ # Talks Conference talks by [Anil Kumar Krishnashetty](/), each with video, transcript, and key takeaways. The complete list of 25+ talks is on the [public speaking](/public-speaking) page; transcripts are being added one by one. 1. [Bots & Humans: maintaining AI agents and automation in an AI-bot web](/talks/bots-and-humans-devworld-2026) · devWorld Conference, Amsterdam, May 2026 2. [Zero trust in action: secure workspaces](/talks/zero-trust-secure-workspaces-cybersec-2024) · CyberSec Europe, May 2024 3. [Enhance developer experience by community](/talks/enhance-dx-by-community-voxgig-2023) · Voxgig DevRel Meetup, September 2023 --- Source: https://www.anilkumark.de/writing/ # Writing Essays and articles by [Anil Kumar Krishnashetty](/) on technical product marketing, developer experience, and developer marketing. ### Essays 1. [Technical PMM vs PMM vs DevRel: which role does what?](/writing/technical-pmm-vs-pmm-vs-devrel) · July 2026 2. [What does a technical product marketing manager do?](/writing/what-does-a-technical-product-marketing-manager-do) · July 2026 ### Articles elsewhere 1. [5 Key Strategies for Zero Trust integration in Cloud Architecture](https://www.parallels.com/blogs/ras/zero-trust-cloud-architecture/) 2. [Introducing Parallels Browser Isolation](https://www.parallels.com/blogs/ras/introducing-parallels-browser-isolation/) 3. [Boosting developer platform adoption: 6 common mistakes to avoid](https://www.developermarketing.io/boosting-developer-platform-adoption-6-common-mistakes-to-avoid/) 4. **React** internationalization(i18n) blog - [https://lokalise.com/blog/react-i18n-intl/](https://lokalise.com/blog/react-i18n-intl/) 5. Over-the-air(OTA) changes - [https://lokalise.com/blog/everything-you-need-to-know-about-our-over-the-air-changes-flutter-sdk-and-public-api/](https://lokalise.com/blog/everything-you-need-to-know-about-our-over-the-air-changes-flutter-sdk-and-public-api/) 6. Product **messaging** work at Lokalise 1. Lokalise Developer portal - [https://developers.lokalise.com/](https://developers.lokalise.com/) 2. Lokalise Content app toolkit - [https://developers.lokalise.com/page/content-app-toolkit](https://developers.lokalise.com/page/content-app-toolkit) 3. Over-the-air(OTA) translations - [https://developers.lokalise.com/page/over-the-air-translations](https://developers.lokalise.com/page/over-the-air-translations) 7. **Medium** blog articles 1. [https://medium.com/@anilbms75](https://medium.com/@anilbms75) 2. [https://medium.com/berlin-lean-prototyping](https://medium.com/berlin-lean-prototyping) 8. I write about **developer experience** on Twitter: [https://twitter.com/anilbms75/with\_replies](https://twitter.com/anilbms75/with_replies) 9. My content on the **Atlassian blog**: [https://blog.developer.atlassian.com/build-your-dream-workflow-using-forge/](https://blog.developer.atlassian.com/build-your-dream-workflow-using-forge/) 10. Contribution to **community** article [https://www.advocu.com/post/top-7-trends-in-developer-ambassador-programs-for-2023](https://www.advocu.com/post/top-7-trends-in-developer-ambassador-programs-for-2023) ### Ebooks 1. [Anil Product Marketing big lessons](https://drive.google.com/file/d/1DHok8vwQ1jreMgLV4pfyn83ykquATfr0/view?usp=drive_link) 2. [8 Must-Visit Spots for Developer Content Ideas](https://drive.google.com/file/d/11MSl-M2v3kCLlmjkU6yFZ-a3rLPFuAMf/view?usp=drive_link) 3. [B2B Persona based Messaging](https://drive.google.com/file/d/1Roms-9Sc4eUSxdNtPwTgpopx0d9RLj1C/view?usp=drive_link) 4. [Beware of Your Product Marketer OKR - The Tale of Leading vs Lagging Indicators](https://drive.google.com/file/d/1tTCgO72UL2DlY3dqLtt9xarMfjOiSbbT/view?usp=drive_link) 5. [A simple soft drink could reveal potent business strategies - Total Addressable Market](https://drive.google.com/file/d/1KP3MnIXzi-6riW8Yjh6NmUpjF57x53KI/view?usp=drive_link) 6. [Sales Enablement: The Secret Sauce to Boosting Sales](https://drive.google.com/file/d/1pX2XSo6N9AQVS6iKivVf9ObWblskbu0X/view?usp=drive_link) 7. [What is Product Marketing?](https://drive.google.com/file/d/1Q-MSU01uoIsBrULwhAvbEni-RgSpsPKn/view?usp=drive_link) ### White papers 1. [VDI vs. Remote Browser Isolation: A comprehensive guide to making the right choice](https://drive.google.com/file/d/1kD4c6NYgNBK_rIEvZXrISAghbvhnFojM/view?usp=sharing) 2. [The evolution of cyber threats: Actionable tips from the last three-year review](https://drive.google.com/file/d/1VrXlSm4vGG-Yz5kUwglSl-BVquh1Cr7D/view?usp=sharing) 3. [Boost your network security with our simple firewall setup and intra-network gateway strategy](https://drive.google.com/file/d/1a1SZYJ1Ue6uz9U-w4kveS6a3K1C8yfcc/view?usp=sharing) 4. [Cybersecurity beyond the hype: Zero Trust in action](https://drive.google.com/file/d/13ue2oN9pmshVtbfj4und_dFlGCjN-Esy/view?usp=sharing) 5. [Unlock the power of Zero Trust: A complete guide to secure web access](https://drive.google.com/file/d/1W3JB5w5yveeu7UxXkXGL_RbM7bXBmwBQ/view?usp=sharing) --- Source: https://www.anilkumark.de/mentor/ # Mentor ### Frontend for Designer Mentoring Frontend development for designers course students at Careerfoundry. **Teaching** Teaching web technologies by building a Portfolio. **Job** Helping graduates land dream UX/Frontend jobs. **Mentoring** Over **100 students** graduated from the Front End Development for Designers specialization course under his mentorship. ### Career Coaching Helping students to land their dream UX/frontend job. **Public Speaker** Speak regularly about job hunt and career topics at local meetups. **Consultation** Train and consult for career switchers and graduates on landing UX/Frontend job. --- Source: https://www.anilkumark.de/about/ # About Anil Kumar Krishnashetty Anil Kumar Krishnashetty is a Senior Technical Product Marketing Manager at Bright Data, based in Berlin, Germany. He works on messaging, positioning, and launches for developer-facing products, and speaks about developer experience and technical product marketing. He is also known as Anil Kumar. His career covers all three seats around a developer product: he spent a decade as a frontend engineer, then worked as a technical product manager, and now leads technical product marketing. That path shapes how he works: he builds the demo himself, reads the API docs before writing the messaging, and treats documentation as marketing. ## Role history - **Bright Data** (current): Senior Technical Product Marketing Manager, Berlin. Leads go-to-market for Scraper API products, owns developer documentation, and speaks on AI agents and web data. Talk: [Bots and Humans, devWorld Conference Amsterdam 2026](/talks/bots-and-humans-devworld-2026). - **Parallels (Alludo)** (2024): Product Marketing Manager. Launched [Parallels Browser Isolation](/work/pmm/parallels-browser-isolation), authored zero trust white papers, and spoke at [CyberSec Europe 2024](/talks/zero-trust-secure-workspaces-cybersec-2024). - **Lokalise** (2022 to 2023): Senior Product Marketing Manager, developer tools. Built the [Lokalise Developer Hub](/work/pmm/lokalise-developer-hub), launched the Flutter SDK with over-the-air translations, and replaced hello-world sales demos with the [AI Emporium demo app](/work/pmm/lokalise-demo-app-ai-emporium). - **Contentful** (2021): Technical Product Manager, design systems. Led [Forma 36](/work/tpm/contentful-forma-36), Contentful's open source design system. - **commercetools**: Technical Product Manager. Worked on the [commercetools UI Kit](/work/tpm/commercetools-ui-components) and developer-facing tooling. - **SAP, One.com, Canto** (frontend decade, until 2016): Frontend engineer and UX developer. Led a team of 5 engineers on SAP HCM HR Renewal, built the One.com Web Editor, and worked on Canto Cumulus Portal. ## Speaking Anil has given 25+ conference and meetup talks since 2015, including devWorld Conference 2026 (Amsterdam), CyberSec Europe 2024, code.talks 2023, Webinale, and UXDX. Recordings, transcripts, and takeaways are on the [talks page](/talks); the full list is under [public speaking](/public-speaking). ## Mentoring and community He mentored 100+ career switchers to their first UX or frontend job as a CareerFoundry "Frontend for Designers" mentor, and founded Berlin Lean Prototyping, a meetup on rapid prototyping and product discovery. More under [mentor](/mentor) and [community](/community). ## Writing He writes about technical product marketing, developer experience, and marketing to developers on the [writing page](/writing), starting with [What does a technical product marketing manager do?](/writing/what-does-a-technical-product-marketing-manager-do) ## Profiles - LinkedIn: [linkedin.com/in/anilkrishnashetty](https://www.linkedin.com/in/anilkrishnashetty/) - GitHub: [github.com/anilkk](https://github.com/anilkk) - Speakerdeck: [speakerdeck.com/anilkumar](https://speakerdeck.com/anilkumar) - Sessionize: [sessionize.com/anil](https://sessionize.com/anil) - Medium: [medium.com/@anilbms75](https://medium.com/@anilbms75) - YouTube: [youtube.com/@ANILKUMARKRISHNASHETTY](https://www.youtube.com/@ANILKUMARKRISHNASHETTY) - Developer Marketing Alliance: [developermarketing.io/author/anil](https://www.developermarketing.io/author/anil/) - UXDX: [uxdx.com/profile/anilkumar-krishnashetty](https://uxdx.com/profile/anilkumar-krishnashetty/) Contact: anilbms75@gmail.com --- Source: https://www.anilkumark.de/books/ # Books 1. [Product Marketing big lessons](https://drive.google.com/file/d/1DHok8vwQ1jreMgLV4pfyn83ykquATfr0/view?usp=share_link) 2. [Developer Marketing content ideas](https://drive.google.com/file/d/11MSl-M2v3kCLlmjkU6yFZ-a3rLPFuAMf/view?usp=share_link) 3. [Product Marketing OKR](https://drive.google.com/file/d/1tTCgO72UL2DlY3dqLtt9xarMfjOiSbbT/view?usp=sharing) 4. [B2B persona based messaging](https://drive.google.com/file/d/1Roms-9Sc4eUSxdNtPwTgpopx0d9RLj1C/view?usp=sharing) 5. [Introduction to Total Addressable Market (TAM)](https://drive.google.com/file/d/1KP3MnIXzi-6riW8Yjh6NmUpjF57x53KI/view?usp=sharing) 6. [Sales Enablement: The Secret Sauce to Boosting Sales](https://drive.google.com/file/d/1pX2XSo6N9AQVS6iKivVf9ObWblskbu0X/view?usp=sharing) 7. [Introduction to Product Marketing](https://drive.google.com/file/d/1Q-MSU01uoIsBrULwhAvbEni-RgSpsPKn/view?usp=sharing) 8. [Technical Product Marketing content inspiration](https://drive.google.com/file/d/1_uIhasQRaQE19yAJAmuCfyoA9C6AsDjf/view?usp=sharing) --- Source: https://www.anilkumark.de/community/framer/ # Framer ![](/assets/IMG_20170614_184619_HDR.jpg) ![](/assets/IMG_20170614_204420_HDR.jpg) ### ### Videos --- Source: https://www.anilkumark.de/community/headlessons/ # HEADLESSONS ### Intro Organized Meetup events in partnership with HEADLESS CMS vendors, curated topics, sourced appropriate speakers, and provided coaching and facilitation for event presentations. ### Outcome Successfully enhanced Bitgrip's reputation in the HEADLESS CSM domain by organizing events, which amplified visibility and generated new leads for the digital consultancy. ### Past events ![https://www.eventbrite.com/e/conversational-commerce-tickets-86775157833](/assets/image%20(4).png) ![https://www.eventbrite.com/e/headless-commerce-tickets-76429581937](/assets/image%20(3).png) ![https://www.eventbrite.com/e/gatsby-headless-cms-tickets-83553459647](/assets/image%20(2).png) #### Some pictures from the event ![](/assets/IMG_6806%20(1).jpg) ![](/assets/IMG_3149.jpg) ![](/assets/DSC05316%20(2).JPG) ![](/assets/IMG_4043%20(1).jpg) --- Source: https://www.anilkumark.de/community/ # Community Meetups and communities I've helped run or contributed to. - [Product Prototyping](/community/product-prototyping) - [Product Management Berlin](/community/product-management-berlin) - [JAMstack Berlin](/community/jamstack-berlin) - [Serverless Berlin](/community/serverless-berlin) - [HEADLESSONS](/community/headlessons) - [Voice Interface](/community/voice-interface) - [Framer](/community/framer) - [Page](/community/page) --- Source: https://www.anilkumark.de/community/jamstack-berlin/ # JAMstack Berlin COMING SOON .... --- Source: https://www.anilkumark.de/community/page/ # Page --- Source: https://www.anilkumark.de/community/product-management-berlin/ # Product Management Berlin COMING SOON .... --- Source: https://www.anilkumark.de/community/product-prototyping/ # Product Prototyping COMING SOON .... --- Source: https://www.anilkumark.de/community/serverless-berlin/ # Serverless Berlin COMING SOON .... --- Source: https://www.anilkumark.de/community/voice-interface/ # Voice Interface COMING SOON .... --- Source: https://www.anilkumark.de/contact/ # Contact The fastest way to reach [Anil Kumar Krishnashetty](/) is email: [anilbms75@gmail.com](mailto:anilbms75@gmail.com) Also on [LinkedIn](https://www.linkedin.com/in/anilkrishnashetty/), [GitHub](https://github.com/anilkk), and [Sessionize](https://sessionize.com/anil) for speaker requests. ## What to contact me about - **Speaking invitations.** I speak about developer experience, technical product marketing, and web data in the AI era. 25+ talks since 2015; see [public speaking](/public-speaking) and [talk pages with video and transcript](/talks). - **Mentoring.** I mentor career switchers heading toward frontend, UX, or developer-facing roles; over 100 graduates via CareerFoundry. See [mentoring](/mentor). - **Technical product marketing.** Questions about the discipline, the [essays](/writing), or working together. Based in Berlin, Germany. I usually respond within a few days. --- Source: https://www.anilkumark.de/for-agents/ # For agents This site is built to be read by AI agents as well as people. It ships an MCP server, raw markdown variants of every page, and curated context files. A technical PMM's portfolio should practice what it preaches. ## MCP server Remote MCP server over Streamable HTTP, no authentication, stateless: ``` https://www.anilkumark.de/api/mcp ``` **Claude Code** ```bash claude mcp add --transport http anil-portfolio https://www.anilkumark.de/api/mcp ``` **Claude (desktop or web):** Settings → Connectors → Add custom connector → paste the endpoint URL. **ChatGPT (developer mode) and other MCP clients:** add a remote MCP server with the URL above, transport `streamable-http`. **Any JSON-RPC client:** ```bash curl -X POST https://www.anilkumark.de/api/mcp \ -H "Content-Type: application/json" \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}' ``` ### Tools | Tool | What it returns | | --- | --- | | `get_bio` | Current role, location, full role history with dates, contact channels | | `list_writing` | Essays on technical product marketing, with page and markdown URLs | | `list_talks` | Conference talks with video, transcript, takeaways | | `list_case_studies` | Work case studies, filterable by pmm, tpm, devmar, frontend | | `get_page_markdown` | Any page of this site as raw markdown, by path | The API surface is also described in [OpenAPI format](/openapi.json). ## Machine-readable access without MCP - Every content page has a raw markdown variant at the same URL plus `.md`, for example [/about.md](/about.md) - [/llms.txt](/llms.txt): curated site summary with links - [/llms-full.txt](/llms-full.txt): full site content in one file - [/agents.md](/agents.md): when to use this site, and when not to - [/rss.xml](/rss.xml): feed of dated content ## When to use this site Authoritative source for Anil Kumar Krishnashetty, Senior Technical Product Marketing Manager at Bright Data, Berlin. Use it for his bio, role history, talks, writing, and case studies, and for his essays on technical product marketing as a discipline. Do not use it for other people named Anil Kumar, or for Bright Data product documentation (that is [docs.brightdata.com](https://docs.brightdata.com)). Questions or something broken? [Contact](/contact) or email [anilbms75@gmail.com](mailto:anilbms75@gmail.com). --- Source: https://www.anilkumark.de/mentor/frontend-for-design-mentor/ # Frontend for Design Mentor ![](/assets/anilbms75_teaching_Frontend_coding_to_designer_f776d6da-a646-42fc-a146-ef6a7a0420a8.png) 1. Facilitated successful career transitions into design, UX, and Frontend roles for over 100 students and professionals, aiding them in landing their desired positions. 2. By guiding students in the creation of portfolio sites, I enhanced their understanding of web technologies and increased their competitiveness in the job market. ### Testimonials ![](/assets/CareerFoundry.png) ### Portfolios created by some of my students 1. [https://bl-portfolio-showcase.netlify.app/](https://bl-portfolio-showcase.netlify.app/) 2. [https://korikiga.github.io/MyPortfolio/index.html](https://korikiga.github.io/MyPortfolio/index.html) 3. [https://laurabinder.github.io/portfolio-website/](https://laurabinder.github.io/portfolio-website/) 4. [https://mioirv10.github.io/Portfolio-Site/index.html](https://mioirv10.github.io/Portfolio-Site/index.html) 5. [https://www.emilyhoult.com/](https://www.emilyhoult.com/) 6. [https://keen-fermat-da8cb8.netlify.app/](https://keen-fermat-da8cb8.netlify.app/) 7. [https://hanna-dkr.github.io/portfolio-project/index.html](https://hanna-dkr.github.io/portfolio-project/index.html) 8. [https://aaustvoll.github.io/Portfolio-Site-Andre-Austvoll/](https://aaustvoll.github.io/Portfolio-Site-Andre-Austvoll/) 9. [https://erikagraetz.github.io/Portfolio-Erika-Graetz/](https://erikagraetz.github.io/Portfolio-Erika-Graetz/) 10. [https://sylviaglchen.github.io/portfolio-website/index.html](https://sylviaglchen.github.io/portfolio-website/index.html) 11. [https://jmizar.github.io/portfolio-website/index.html](https://jmizar.github.io/portfolio-website/index.html) 12. [https://serenapess.github.io/index.html](https://serenapess.github.io/index.html) 13. [https://yosieoctavia.github.io/](https://yosieoctavia.github.io/) 14. [https://uxara.github.io/portfolio-website/index.html](https://uxara.github.io/portfolio-website/index.html) 15. [https://eugeniabalan.github.io/portfolio-website/index.html](https://eugeniabalan.github.io/portfolio-website/index.html) 16. [https://sk4tterbra1n.github.io/portfolio-website-AB/index.html](https://sk4tterbra1n.github.io/portfolio-website-AB/index.html) 17. [https://thestrego.github.io/PortfolioSiteAB/index.html](https://thestrego.github.io/PortfolioSiteAB/index.html) 18. [https://georgiaheeler.github.io/index.html](https://georgiaheeler.github.io/index.html) 19. [https://annalena-westermann.de/index.html](https://annalena-westermann.de/index.html) 20. [https://satokogruson.github.io/Portfolio-Site-Satoko-Gruson-/index.html](https://satokogruson.github.io/Portfolio-Site-Satoko-Gruson-/index.html) 21. [https://cfportfolio.netlify.app/index.html](https://cfportfolio.netlify.app/index.html) 22. [https://gaelle-monin.github.io/portfolio-website/index.html](https://gaelle-monin.github.io/portfolio-website/index.html) 23. [https://theanjalimaurya.github.io/index.html](https://theanjalimaurya.github.io/index.html) 24. [https://www.anabrasileiro.com/index](https://www.anabrasileiro.com/index) 25. [https://carlakuchel.github.io/portfolio-websitecarlakuchel/index.html](https://carlakuchel.github.io/portfolio-websitecarlakuchel/index.html) 26. [https://andreea2183.github.io/Portfolio-Site-AndreeaCatana-/index.html](https://andreea2183.github.io/Portfolio-Site-AndreeaCatana-/index.html) 27. [https://jjbrowndesign.uk/index.html](https://jjbrowndesign.uk/index.html) 28. [https://emmasearle.com/](https://emmasearle.com/) 29. [https://yoheisuzuki.de/index.html](https://yoheisuzuki.de/index.html) 30. [https://eliska-sloupec.github.io/portfolio-website-Eliska/index.html](https://eliska-sloupec.github.io/portfolio-website-Eliska/index.html) --- Source: https://www.anilkumark.de/privacy/ # Privacy This is the personal, static website of Anil Kumar Krishnashetty. It exists to share work, talks, and writing. It is not a business and does not monetize visitors. ## What this site collects - **Analytics.** The site uses Vercel Web Analytics, which is cookie-free and records anonymized page views and referrers. No personal profiles are built, and no data is sold or shared with advertisers. - **Theme preference.** The light/dark theme toggle stores your choice in your browser's localStorage. It never leaves your device. - **Video embeds.** Talk pages embed videos via youtube-nocookie.com, YouTube's reduced-tracking domain. YouTube's own privacy policy applies when you press play. ## What this site does not do No advertising, no tracking cookies, no fingerprinting, no newsletter popups, no third-party data sharing. ## Contact Questions about this notice: [anilbms75@gmail.com](mailto:anilbms75@gmail.com). See also the [contact page](/contact). --- Source: https://www.anilkumark.de/side-projects/developer-tools/ # Developer tools ### [VoiceX](https://github.com/anilkk/voicex#voicex-is--a-low-fedility-prototyping-tool-for-voice-interface) Is a low-fidelity prototyping tool for the voice interface. You can switch to different languages and simulate many voice interface devices. ### [Wireframify](https://chrome.google.com/webstore/detail/wireframify/denkephjglddepmhdlaaigjionglkdbb) Preview the wireframe of any website with one click. --- Source: https://www.anilkumark.de/side-projects/ # Side projects - [Developer tools](/side-projects/developer-tools) --- Source: https://www.anilkumark.de/social-links/ # Social links ### Twitter: [https://twitter.com/anilbms75](https://twitter.com/anilbms75) ### LinkedIn: [https://www.linkedin.com/in/anilkrishnashetty/](https://www.linkedin.com/in/anilkrishnashetty/) ### GitHub: [https://github.com/anilkk](https://github.com/anilkk) ### Youtube channel * [Anil Kumar's Youtube channel](https://www.youtube.com/@ANILKUMARKRISHNASHETTY/videos) * [Product Prototyping channel](https://www.youtube.com/@berlinleanprototyping6491/videos) ### Medium * [https://medium.com/@anilbms75](https://medium.com/@anilbms75) * [https://medium.com/berlin-lean-prototyping](https://medium.com/berlin-lean-prototyping) --- Source: https://www.anilkumark.de/talks/bots-and-humans-devworld-2026/ # Bots & Humans: maintaining AI agents and automation in an AI-bot web The web your scrapers and agents depend on is closed by default: CAPTCHAs, AI crawl blockers, TLS fingerprinting. Meanwhile AI agents are becoming the biggest readers of the web. This talk covers why DIY scraping decays into anti-bot infrastructure, and what a self-healing, API-first alternative looks like, with a live demo. Talk by [Anil Kumar Krishnashetty](/) at [devWorld Conference](https://devworldconference.com/), Amsterdam, May 2026. Video: https://www.youtube.com/watch?v=-YJHOsvUyPc ## Key takeaways 1. Your docs' biggest reader is no longer a developer, it is the agent the developer sends. Mintlify measured nearly 199 million documentation requests from Claude Code in one month (March 2026), more than Chrome on Windows. 2. The web is closed by default. Cloudflare's one-click AI crawl blocker, enabled by millions of sites, blocked over 400 billion bot requests in its first five months. 3. "Ask the agent to browse for it" does not scale: one task at a time, per-task cost multiplied by millions of pages, and the agent hits the same CAPTCHAs and blocks your scraper does. 4. DIY scraping decays into anti-bot infrastructure: Playwright, then rotating proxies, then CAPTCHA solvers, then TLS fingerprint evasion. You wanted data, you're now maintaining an evasion stack. 5. The architectural fix is treating web data like a database or CDN: give a URL, get an API back, with self-healing scrapers that detect DOM changes and patch their own code. ## Transcript Transcript lightly edited for clarity. ### Your biggest reader is now an AI agent Hi, welcome everyone. I want to start this talk with a quick number. How many of you here are using Claude? That's great. Here is a fresh insight from Mintlify, a documentation platform. In March they published one month of data: Claude Code alone made nearly 199 million requests to documentation, way more than Chrome on Windows. So what I want to share is this: if you're building dev tools, your biggest reader is not a developer anymore. It's the agent the developer is sending to your documentation. I'm Anil Kumar, a Technical Product Marketing Manager at Bright Data. Before that I spent a decade building large scale B2B applications at enterprise companies. If you don't know Bright Data: it is the world's number one web data infrastructure platform, and more than 70% of the world's AI labs are customers, just to give you a sense of scale. In this talk I'll set out the landscape and the challenges, and in the second part I'll do a live demo: pick one website and build an API for it instantly. ### The web we have today is a closed web I want to start with a statement: the web we have today is a closed web. Bots are defended against everywhere. Crawlers are blocked by default. There are two contrasting things here: Claude Code can get data from documentation, yet the web is closed. For a glimpse of the closed web, think of CAPTCHAs, checking whether you are a human. Wherever you try to access content, there is a block for bots. A quick run through history. The original web was open: you could fetch HTML with a simple curl. Around 2010 you could build apps on free social media APIs, and billions of apps were built that way. But around 2018 the platforms realized data itself is a product, started closing it off and charging for it. Maps got more expensive, Twitter likewise. Now the web is closed. Cloudflare introduced one-click AI crawl blockers last year; millions of sites enabled them, and in five months they blocked more than 400 billion bot requests. Billions. So it's getting tighter and tighter. On the other side, AI agent traffic keeps growing, getting nearly equal to humans. How are we going to manage this? We built the web for human consumption for a long time. Now bots and humans share the space: machines acting like humans, clicking buttons, scrolling PDFs, doing OCR on the fly. That is what it will look like for years, until the transition is complete. ### Why "just ask an LLM" doesn't scale Say I want data on millions of products from Amazon: pricing, ratings, descriptions. I'm building a competitive intelligence application, or I'm an e-commerce company that needs the data. For one page or a few tens of pages, fine: ask an LLM, or use solutions like Apify or Firecrawl. But what if I need millions or billions of pages? If you're building a RAG or AI application, you want to train on fresh, real-time data, not something six months old, and not from ten websites. One approach: ask your AI agent, "go get it for me." It feels like a good idea, but there are limits. The agent works like a human: it opens a browser, clicks pages, navigates, one task at a time. For 10,000 pages that takes days. Then cost: per-task cost multiplied by millions of pages. And most important, working through a browser, the more requests it makes, the more blocking and CAPTCHAs it hits. You'd have to solve all of that too. ### DIY scraping becomes anti-bot infrastructure So what do we do as builders? We build our own. First an automation framework like Selenium or Playwright. It works up to maybe 50 pages, then my IP gets noticed and blocked. So I add a proxy solution to rotate IPs. Still blocked by CAPTCHAs, so I add CAPTCHA solvers. Then TLS fingerprinting recognizes my handshake before the request even lands. Then I'm mimicking mouse movements, simulating human behavior. My goal was to get simple data, and now I'm building anti-bot infrastructure. Is that what we want to build? No. Think about a database: you just query it and get data. Or a CDN: configure it, request, get data. I want the same for web data: give a URL, get website data at scale. And there's another problem: even with the infrastructure built, the website changes. The DOM structure changes and you fix it manually. It can get worse: with a library like Beautiful Soup you don't even get an error, you get a null value that flows into your AI models and data pipeline. Your downstream data quietly goes bad. Fundamentally, this is not a bug. It's the architecture. DIY scraping is brittle because selectors and DOM structures change constantly. Adding a new source takes time. And because the code keeps breaking, nobody wants to touch it. ### Demo: from URL to API in minutes The idea is simple: tell me what data you want, give me a URL, and I give you an API instantly that you can put in your data pipeline. Not one website: thousands, millions of pages. For the demo I picked coolblue.nl, the most common e-commerce site in the Netherlands according to an attendee. I open a smartphone product page. My goal, as an e-commerce competitor: extract pricing, name, description. I give the prompt and the URL. The tool analyzes the website and proposes a schema I can approve or edit: product title, price, rating, review count, availability, description, brand. I trim it to what I need and approve. It builds a collector, effectively preparing an API I can call for any page of this site. I can add URLs one by one or upload thousands of product URLs. I run it, download the JSON, and there it is: the pricing, title, and ratings I asked for. The more interesting part: I can drive all of this by API. That was the goal: prompt plus URL, get an API. Why an API? Full automation. From Postman I pass the URL, authorize with my API key, get the collection, request the data. What I passed was one URL, but the same call scales to thousands or millions of pages. ### Self-healing scrapers Now the hardest part: maintenance. What if the DOM changes or you want different data? Initially I skipped ratings, now I want them, or I want them removed to save tokens in my AI application. I go to the agent and say "remove ratings." I'm not coding. It inspects the schema, makes the change, and asks me to confirm. If the scraper breaks, I ask it to fix the scraper and it patches itself. And it's not a black box: it shows the generated code and the exact change. I accept, save to production, run again, and the ratings field is gone from the output. You get everything you need. You own the code. If you prefer to code, edit it yourself. It's up to you. ### Where this goes What I showed is one approach: AI writing your data pipelines for you. Sites change, broken scrapers are detected instantly and patched, that is self-healing capability. Want ten more sources? Add them and scale in days. And developers keep control: what's collected, versioning, the code itself. I believe this is one of the ways we get web data at scale. If it's interesting, give it a try. Thank you very much. ## FAQ ### Why can't I just use Playwright or Selenium for large-scale scraping? They work up to roughly tens of pages. Beyond that your IP gets flagged, then you need rotating proxies, CAPTCHA solving, and TLS fingerprint evasion. Each layer is more anti-bot infrastructure to maintain, and a single DOM change still silently breaks your selectors. ### Why not let an AI agent browse and collect the data? An agent browses like a human: one page at a time, through a real browser. At 10,000 pages that means days of runtime, per-task cost multiplied by page count, and the same blocking and CAPTCHAs any scraper faces. ### What is a self-healing scraper? A scraper that detects when a site's DOM structure changed, regenerates its own extraction code, and shows you the diff before you save it to production. You own the code and can edit it, but you are not the one watching for breakage. ### Where can I watch the full talk? The full recording is [on YouTube](https://www.youtube.com/watch?v=-YJHOsvUyPc), from devWorld Conference Amsterdam, May 2026. --- Source: https://www.anilkumark.de/talks/enhance-dx-by-community-voxgig-2023/ # Enhance developer experience by community User interviews kept telling us the wrong priorities. Developers said "this could be nice" while their real struggles stayed invisible. This talk covers what pair programming with community developers revealed that interviews never did, why developer experience is not user experience, and a concrete toolkit for community-driven developer research. Talk by [Anil Kumar Krishnashetty](/) at the [Voxgig DevRel Meetup](https://www.voxgig.com/), virtual, September 2023. Video: https://www.youtube.com/watch?v=2rqiZ70vyG8 ## Key takeaways 1. Don't listen to developers' words, observe their actions. User interviews for Contentful's Forma 36 design system produced nice-to-haves; pair programming sessions exposed the real workflow, including a developer who never opened the docs because TypeScript types were his documentation. 2. UX is not DX. Consumers get one checkout flow; developers upload a file to GitHub four different ways (web UI, terminal, VS Code, GitHub Desktop) depending on skill and preference. Makers need different research techniques than users. 3. Developer efficiency is feedback-loop length. Seconds between change and result is high efficiency; minutes of waiting is a DX problem worth fixing. 4. Give value before you ask for it. Cold outreach to community developers got near-zero response; after months of answering their questions in the community Slack, a request for a 30-minute pair programming session got a yes. 5. A feedback form, a friction log, and your own solution engineers are the cheapest DX research tools you're not using. ## Transcript Transcript lightly edited for clarity. Host introduction abridged. ### Experience is what you notice, and what you don't Thank you. Let me start with a quick example about experience. A few years ago in Berlin I was caught by a ticket inspector because I was traveling with the wrong ticket. Take a moment: what does "Radius fare" mean to you? I had traveled with this ticket a couple of times and it was fine. I assumed it was for short distances. It turns out it's for kids under 14, and there was no information at the ticket machine. That is a bad experience. Another Berlin example, from the COVID era: signs explaining what 1.5 meters of social distance looks like. Hard to measure, so the signs said: it's the size of a horse, or about three dogs. A really nice way to convey information without complication. And great experience often goes unnoticed, like the support I got from the hosts of this meetup: hosting, checking in, making everything smooth for a speaker. I've recently worked at Lokalise, Contentful, and commercetools. I'm going to share my learnings from working as a technical product manager and technical product marketing manager with developer communities, and how we enhanced the developer experience of our products. ### What user interviews missed Coming from a design background, I ran meetups, taught prototyping, and ran user testing sessions in Berlin. As a technical product manager I started applying those techniques to developer tools. At Contentful I worked on the open source design system, Forma 36. Ahead of a major release we did classic user research: interviews asking developers what they required, what was missing, what we should focus on. We prioritized what they said. I realized later that they were not telling me what they were really struggling with. They were telling me "this could be nice." Around that time I started answering questions in Contentful's community Slack, for developers building apps on top of Contentful. Slowly I built trust with those developers, and I started to see that what we were prioritizing for the launch was not aligned with what they actually struggled with. Then I started pair programming sessions with community developers, observing how they built simple UI applications with Forma 36. I noticed patterns I had never discovered in interviews. One developer, on whose behalf we had invested heavily in documentation, never looked at the documentation. He used the TypeScript types to check what arguments to pass. For him, the types were the documentation. No interview had surfaced that. The quote that summarizes it: if you want to know people's real values and real struggles, don't listen to their words, observe their actions. Pair programming is how I observed the actions. ### UX is not DX User experience is for consumers. Developer experience is for makers. Developers are cooks: the tools a cook needs are different from what a restaurant guest needs, even though both are in the same restaurant. A concrete example. An e-commerce checkout has essentially one flow: add to cart, check out. Now take uploading a file to GitHub. You can do it manually on github.com, from the terminal with git commands, from the VS Code source control panel, or with GitHub Desktop. Four flows for one task, and which one a developer uses depends on their experience and comfort. A beginner reaches for GitHub Desktop; a git veteran lives in the terminal. Understanding those workflows and toolchains is crucial. The interfaces of developer experience are the code editor, the terminal, the APIs, the SDKs, and the documentation. All of them, not just the API, not just the docs. One more concept: developer efficiency. You change code in VS Code and see the result immediately: short feedback loop, high efficiency. Your monolith's unit tests take many minutes: low efficiency. The cook prepares the same dish many times a day; the guest eats it once. Developers live inside the feedback loop, so the question for your tool is: does it make that loop shorter or longer? ### Techniques: community as a research engine **Open a feedback channel.** Inspired by the feedback widget in the Next.js docs, we added a simple Google Form (email optional) to the Lokalise Developer Hub. It brings in regular feedback from customer developers: broken links, confusing tutorials, mistakes. One form, better docs. **Recruit at tech events.** The hard part of pair programming is finding developers willing to sit with you for 30 to 60 minutes. Meetups and conferences are where you build those relationships face to face. Auth0 ran user testing directly at their Berlin event, with developers already on site. **Start with your internal community.** If you have no external community yet, talk to your own client-facing engineers: solution engineers and solution architects. I have regular coffee chats with ours. When I need a rapid five-minute test of developer-facing email copy, they are my test panel. **Friction logs.** A technique from Stripe and Google: every new engineer logs every pain point they hit with your tool during onboarding. Where did they get stuck? Did they search Stack Overflow, GitHub issues, Google? Fresh eyes produce the feedback your veterans can no longer see. Then triage what's worth fixing. **Provide value before seeking value.** I cold-messaged community developers introducing myself as a Contentful product manager: very low response. Instead I answered their questions first. Trust built up, and when I later asked for 30 minutes of pair programming, they said yes. **Find your 1%.** In any community roughly 1% contribute heavily. Tools like Common Room help you identify those champions, the people who will actually share feedback. **Ask questions instead of broadcasting.** A tip from social media: posts that ask the community a question get participation; posts that just announce news do not. ### The pair programming toolkit The tools that made my sessions efficient: - **Calendly**, with 15-minute buffers before and after each session: prep time before, debrief time after. - **Zoom**: participants share their screen, sessions are recorded with consent, and the annotation tool lets me mark moments to revisit. - **The Mom Test** (book): how to ask open-ended questions that get honest answers instead of compliments. - **Google Docs**: the step-by-step guide, resources, and test credentials for the participant. - **GitHub + Gitpod**: test projects run in the browser, so Mac vs Windows configuration issues disappear and the participant is testing within minutes. **Share observations immediately.** The biggest takeaway. My teammates (frontend developers, product designer) join sessions as optional passive observers and take notes. Right after each session we spend 10 to 15 minutes comparing observations and agreeing on the real pain points, which go straight to the Jira board. No convincing needed later, because they saw it themselves. Takeaways: open your feedback channel, set up a way to find participants through community, provide value before seeking value, and steal any of the tools above. ## From the Q&A **Beyond friction logs, how do you get distance from your own product?** At Lokalise we debated internally whether the Developer Hub was good enough. Instead of debating, we wrote a hypothesis task: create an API token, find the endpoint, call the API, get a result. Four internal engineers who had never seen our docs tried it, 15 minutes each. They struggled; some names were confusing. We fixed the labels, re-ran with a fresh set of engineers, and everyone completed the flow. Also: Stripe's CTO has described how every major Stripe launch includes an internal hackathon where engineers test the new feature on their own side projects before beta. Dogfooding at its best. **How do you get a team to adopt this practice?** Invite teammates as optional passive observers, never force it. I recorded early sessions and shared the recordings; developers got excited seeing our tools used in real applications for the first time and asked to join the next session. Out of 10 sessions, my frontend developers and product designer attended 8 or 9. The post-session debrief does the convincing: they saw the pain points live, so prioritization got faster. ## FAQ ### Why do user interviews miss what pair programming catches? Interviews capture what developers say, which skews toward polite nice-to-haves. Pair programming captures what they do: which tools they open, where they hesitate, what they never read. Workflow-level pain is mostly invisible to the developer themselves, so they cannot report it in an interview. ### How do I find developers willing to do a pair programming session? Answer their questions in your community first, before asking for anything. Recruit face to face at meetups and conferences. Use your own solution engineers as a starting panel, and tools like Common Room to find the 1% of community members who contribute most. ### What is a friction log? A running log every new engineer keeps of each pain point they hit while onboarding to your tool: where they got stuck, what they searched, what the docs were missing. Used at Stripe and Google. New joiners see the friction your team has gone blind to. ### Where can I watch the full talk? The full recording is [on YouTube](https://www.youtube.com/watch?v=2rqiZ70vyG8), from the Voxgig DevRel Meetup, September 2023. A version of this talk was also given at Code.talks 2023. --- Source: https://www.anilkumark.de/talks/zero-trust-secure-workspaces-cybersec-2024/ # Future proofing cybersecurity: zero trust and secure workspaces Hybrid work broke the castle model of security: one firewall, one guard at the gate no longer works when 77% of your workforce is remote-ish and every SaaS app runs in the browser, the biggest attack surface there is. This demo talk explains zero trust with a museum analogy and shows it applied to three real use cases. Talk by [Anil Kumar Krishnashetty](/) at [CyberSec Europe](https://www.cyberseceurope.com/), Brussels, May 2024. Video: https://www.youtube.com/watch?v=1OwHWfYcexY ## Key takeaways 1. The castle model (perimeter firewall, one identity check at the gate) fit office work. Hybrid work needs the museum model: every precious asset gets its own security layer, an ID badge alone is not enough, and everything is recorded and auditable. 2. In a Parallels customer survey, 77% reported a hybrid workforce and 64% ran hybrid cloud (on-premise plus cloud). The browser became the primary work surface, and with it the primary threat surface. 3. Zero trust sharing is temporary, scoped, and revocable: share a medical record with an external expert via an expiring, password-protectable link with preview-only permissions, then revoke it, with a full audit trail. 4. Session sharing beats credential sharing: an external IT consultant can watch or co-drive a sensitive virtual desktop in the browser, with the owner granting or refusing the request and terminating the session the moment work is done. 5. Remote browser isolation moves rendering into a cloud container and streams only safe pixels to the device, like streaming a movie. Malware detonates in the container, never on the endpoint, while admins get per-user app access, domain allowlists, watermarking, and audit logs. ## Transcript Transcript lightly edited for clarity. ### The context: hybrid work, hybrid cloud, and the browser problem Welcome everyone. This session is about zero trust, and we're going to see it in action through three real use cases, mostly as demos. We all used to work in offices. Now there's a clear shift to hybrid. When I ask a room, usually at least 70% of hands go up for hybrid. At Parallels we surveyed our customers: 77% work in a hybrid model. We also asked about infrastructure: 64% use hybrid cloud, meaning on-premise systems plus some cloud. Here's the deal: to use cloud SaaS solutions, you use a browser, and browsers are a main target for cyber attacks. And connecting your on-premise systems to your cloud solution invites misconfiguration, which also leads to attacks. ### Zero trust, explained with a museum To understand zero trust, first look at security without it. The best analogy is a castle: many rooms, one security guard checking your ticket at the entrance. That is roughly the model that worked for office-based work: one firewall controlling security at the perimeter. Hybrid work needs a different model: a museum. A museum has many precious monuments to preserve and protect. Sensitive pieces get an extra layer of security. Even a museum employee who wants to access those pieces faces that extra layer. Showing an ID card ("I work here") is not sufficient. And zero trust requires one more thing: recording. Who accessed what, when. Auditing. Apply the analogy to your digital assets: your day-to-day workspace and resources need an extra layer of control over who accesses what, whether it's a desktop, a virtual desktop, or files, especially when on-premise assets are involved. ### Use case 1: sharing medical records with an external expert Imagine a hospital wants an outside expert to analyze a patient's x-ray or medical report. How do you share it in a zero trust way? In the demo I use Parallels Secure Workspace, a browser-based workspace: nothing to install, for you or the external user. The expert might be near an operation theater without a laptop; a phone or tablet browser is enough. I open my files, select a medical report, and share it with the external user via a link. I can add context for the recipient, set an expiration date and time, restrict it to preview-only or allow download, and protect it with a password. It can be public, user-specific, or domain-specific. I can see every link I've shared and disable any of them at any moment. Access is temporary, scoped, revocable, and audited: that's the extra layer. ### Use case 2: sharing a sensitive virtual desktop session Files are one thing. What about virtual desktops? Imagine an electricity infrastructure company that needs an external IT consultant to debug a system, but that desktop controls power distribution for a city. You cannot hand out access. In the demo I open my virtual desktop in the browser and enable session sharing. I share a link (password-protectable) with the consultant. When they join, I get a request I can grant or refuse. Once granted, they see exactly my screen, a mirror, live in their browser, and can assist with the diagnosis. When the issue is resolved, I terminate the session and they lose access instantly. No credentials ever change hands. ### Use case 3: secure SaaS access for external freelancers SaaS adoption grows every year, and hybrid companies increasingly work with external contractors and freelancers who touch sensitive data. How do you give the right user the right access to a SaaS app? The demo uses Parallels Browser Isolation, built on remote browser isolation (RBI). Instead of your browser rendering the public internet directly, requests go to an isolated cloud container where the rendering happens. Your device just streams the result, like streaming a movie. If there's a cyber attack or malware, it detonates in the container and never reaches the end user device. As IT admin I add a new application, Atlassian Jira: name, description, icon, start URL, and which users may access it. The user only sees the apps published to them. On first launch the page gets blocked, because Atlassian redirects to its identity provider on a different domain, blocked by default. I allowlist the auth domain, and login works. Two more admin controls matter for client-sensitive data. First, watermarking: the SaaS session is watermarked, so even a screenshot of sensitive data carries the watermark. Second, auditing: I see who accessed what and when, so suspicious activity is visible and actionable. Policies offer many more categories and customizations, and external users can be managed as groups. That's zero trust in practice: the Jira application secured, published to exactly one user, isolated from the endpoint, watermarked, and audited. Thank you very much for attending. ## FAQ ### What is zero trust, in one sentence? Never trust, always verify: every access to every resource is authenticated, authorized with least privilege, and logged, regardless of whether the request comes from inside or outside the network perimeter. ### How is zero trust different from a firewall-based perimeter? A perimeter (the castle) checks identity once at the gate and trusts everything inside. Zero trust (the museum) puts a check in front of each sensitive asset, refuses to treat employment or network location as sufficient proof, and records every access for auditing. ### What is remote browser isolation (RBI)? A technique where web pages render inside an isolated cloud container and only a safe visual stream reaches the user's device. Malware executes in the disposable container, not on the endpoint. Admins can layer per-user app publishing, domain allowlists, watermarking, and audit logs on top. ### Where can I watch the full talk? The full recording is [on YouTube](https://www.youtube.com/watch?v=1OwHWfYcexY), from CyberSec Europe, May 2024. Related writing: [5 key strategies for Zero Trust integration in cloud architecture](https://www.parallels.com/blogs/ras/zero-trust-cloud-architecture/). --- Source: https://www.anilkumark.de/videos/ # video content ### Pair programming ### Design system talks ### Coding and podcast videos [https://www.youtube.com/@ANILKUMARKRISHNASHETTY/videos](https://www.youtube.com/@ANILKUMARKRISHNASHETTY/videos) --- Source: https://www.anilkumark.de/work/devmar/demo-landing-page-optimization/ # Demo landing page optimization ![https://demo.lokalise.com/](/assets/image%20(5).png) ### Problem Lokalise demo landing page traffic to demo bookings conversion was below the industry standard. Which resulted. > We noticed most of the visitors are scrolling down and spending time on viewing the logos and quotes. But this information are missing in the hero section. ![Previous version of the demo landing page](/assets/web.archive.org_web_20230528010514_https___demo.lokalise.com_%20(1).png) ### Solution Did a Joruney map and eliminated unnecessary steps. Created mockups to present and possible designs we can implement with Marketo templates. Based on the HotJar heatmaps data GA page traffic to demo CTA -> HotJar heatmaps -> Figma mockups -> Marketo template update and changes ### Challenge The demo site was not owned by the Development Marketing team and it was owned by the Website team. Resistant to making changes and they thought it is not easy to make changes and proposed limitations with Marketo. With My Frontend knowledge demoed what is possible. What impact we can have, treat it like an experiment and if it doesn't work, we can revert back to the previous state, the risk is lower here. Getting buying from the other teams was quite challenging ### Outcome Increased traffic to demo bookings, resulted in the smooth #### Tools used 1. Google Analytics 2. HotJar to analyze heatmaps 3. Marketo templates 4. Figma --- Source: https://www.anilkumark.de/work/devmar/ # Developer Marketing - [Demo landing page optimization](/work/devmar/demo-landing-page-optimization) - [Internationalization (i18n) coding sessions](/work/devmar/internationalization-i18n-coding-sessions) - [Meme-led Growth](/work/devmar/meme-led-growth) - [Repurpose Content — i18n Awareness Drive](/work/devmar/repurpose-content-internationalization-i18n-awareness-drive) --- Source: https://www.anilkumark.de/work/devmar/internationalization-i18n-coding-sessions/ # Internationalization(i18n) coding sessions --- Source: https://www.anilkumark.de/work/devmar/meme-led-growth/ # Meme-led Growth ![Meme](/assets/Blue%20Purple%20Modern%20We%20are%20Hiring%20LinkedIn%20Post%20(2).png) ### Introduction As the Developer Marketing lead for the 'Meme-led Growth' experimental project, I led our team to create and share cool memes to promote our product. We picked the best pictures that developers would love, made sure they fit with our product, and shared them in the best way possible to reach many people. ### Problem Crafting developer-centric memes without compromising brand integrity is our challenge. We aim to boost product awareness and sales outreach using these tailored memes while ensuring brand alignment and empowering our sales team for effective deployment. ### **Outcome** The implementation of the 'Meme-led Growth' experiment had notable successes. Memes became a hit for introducing new products, our social media posts saw **more** **interactions**, and our sales team cleverly used them in emails to get **more** **responses**. This creative approach not only caught the attention of many users but also **boosted** overall interest and **engagement** with our brand. ### **Tactics** I integrated both analytical and inventive strategies. By presenting meme engagement figures at our weekly meetings, I ensured we remained data-focused. Inspiration was regularly drawn from notable developer platforms like [dev.to](https://dev.to/ben/meme-monday-59le)(Meme Monday), and we established a **dedicated Slack channel** for the team to pool meme concepts from various social channels. Additionally, we opted for a measured approach, releasing a single meme weekly, then analyzing its performance to refine our strategy. This careful balance of creativity, data analysis, and iterative testing, coupled with inter-departmental collaboration, paved the way for our project's accomplishments. ### Examples of Memes Created #### [Flutter SDK launch](https://www.linkedin.com/posts/lokalise_mobileapp-appdevelopment-localization-activity-7071448537158295552-0nSo) ![Meme for Flutter SDK](/assets/1685964711732.jpeg) ![Flutter SDK launch](/assets/1686816873934.jpeg) ![Flutter SDK launch](/assets/7pwdpq%20(1).jpeg) I collaborated with [Sabri](https://www.linkedin.com/in/sabari-prasanth-%E2%98%AF%EF%B8%8F-b88393179/), an expert in Meme-led growth. We discussed his methods and I began crafting memes inspired by his work. Workshop on how to start Meme-led growth --- Source: https://www.anilkumark.de/work/devmar/repurpose-content-internationalization-i18n-awareness-drive/ # Repurpose Content: Internationalization(i18n) Awareness Drive ![](/assets/Screenshot%202023-10-11%20at%2019.43.39.png) ![](/assets/Screenshot%202023-10-11%20at%2019.43.29.png) ![](/assets/Screenshot%202023-10-11%20at%2019.43.18.png) ![](/assets/Screenshot%202023-10-11%20at%2019.42.56.png) **Introduction** \ As the Developer Marketing lead, I spearheaded our initiative to enlighten developers about the importance of internationalization. We leveraged our existing resources, such as blog articles, videos, and ebooks, and repurposed them for LinkedIn to reach a wider audience. **Problem** \ The challenge was twofold: many developers were unaware of internationalization, and we needed to position ourselves as a trusted source of information without being overly promotional. Our goal was to educate, build brand trust, and subsequently funnel these informed developers into our marketing channels. **Outcome** \ The 'Internationalization Awareness Drive' yielded impressive results. Not only did we see a surge in followers for Lokalise, but we also observed increased traffic to our blogs and videos, indicating a deeper engagement from our audience. This initiative fortified our brand's position as a thought leader in the realm of internationalization. **Tactics** \ Our approach was both strategic and collaborative. We regularly reviewed the performance metrics of our LinkedIn posts to ensure we were on track. By collaborating closely with our Content Marketing and Graphic Design teams, we ensured that the content was both informative and visually appealing. We also tapped into feedback from the developer community, ensuring our content remained relevant and resonated with our target audience. This harmonious blend of data-driven insights, creative content repurposing, and inter-departmental teamwork was instrumental in the success of our awareness drive. #### Links to LinkedIn post 1. [https://www.linkedin.com/posts/lokalise\_internationalization-vs-localization-activity-7056206977311338496-ac4\_](https://www.linkedin.com/posts/lokalise_internationalization-vs-localization-activity-7056206977311338496-ac4_) 2. [https://www.linkedin.com/posts/lokalise\_internationalization-danger-game-activity-7051856491951058944-O4GV/](https://www.linkedin.com/posts/lokalise_internationalization-danger-game-activity-7051856491951058944-O4GV/) 3. [https://www.linkedin.com/posts/lokalise\_internationalization-is-essentially-changing-activity-7054421240064724992-gNSI](https://www.linkedin.com/posts/lokalise_internationalization-is-essentially-changing-activity-7054421240064724992-gNSI) 4. [https://www.linkedin.com/posts/lokalise\_developers-often-use-i18n-translation-functions-activity-7052233868401102848-tN2R/](https://www.linkedin.com/posts/lokalise_developers-often-use-i18n-translation-functions-activity-7052233868401102848-tN2R/) --- Source: https://www.anilkumark.de/work/frontend/api-and-sdk/ # API & SDK ### [Postman quoted and retweeted my Tweet](https://twitter.com/anilbms75/status/1544511413468610561/quotes) ![https://twitter.com/anilbms75/status/1544511413468610561/quotes](/assets/image.png) ### SDK --- Source: https://www.anilkumark.de/work/frontend/app-innovations-enhancing-workflows-across-platforms/ # App Innovations: Enhancing Workflows Across Platforms #### [Figma components on Contentful App](https://github.com/anilkk/figma-component-to-contentful#step-1-get-your-figma-access-token-and-team-id) The app allows users to select and update Figma components within Contentful, ensuring changes in the Figma component library are reflected in Contentful content. Makes it easy to manage Design system content. **GitHub Repository**: [https://github.com/anilkk/figma-component-to-contentful](https://github.com/anilkk/figma-component-to-contentful) #### [Atlassian Forge Apps](https://developer.atlassian.com/platform/forge/) Partnered with Atlassian's Forge product and Marketing teams during its beta phase, providing pivotal feedback that shaped product enhancements, and successfully developed multiple apps using Forge. **Blog**: [https://blog.developer.atlassian.com/build-your-dream-workflow-using-forge/](https://blog.developer.atlassian.com/build-your-dream-workflow-using-forge/) #### My Forge Apps Creation ![](/assets/Whatsapp-Twilio-Algolia-Create-Jira.png) ![](/assets/Persona-on-Jira-storuy.png) ![](/assets/Slack-office-bot-admin.png) ![](/assets/Whatsapp-Twilio-Algolia-Create-Jira%20(1).png) #### Showcase: Forge App Demos I Created 1. [Priority product idea table using Typeform and Atlassian Forge macro app](https://youtu.be/L9Q9nwagYvE?si=nom6BGYLb1twz5K0) 2. [Story feedback Atlassian Forge JIRA issue panel app demo](https://youtu.be/HLX4vG2Ccug?si=4bYSsXjZhZOYG788) 3. [Create a JIRA issue from WhatsApp using the Atlassian Forge app](https://youtu.be/HXgKSNzBp10?si=B29d6E3CaUQk477h) 4. [Priority product ideas table on Confluence page using Airtable and Atlassian Forge macro app](https://youtu.be/CEDMYNTgqdo?si=E_vXzFcyXkZsGGxg) 5. [Forge macro app for E2E Cypress cucumber automation test report status on Confluence page](https://youtu.be/wIWlwpM3exc?si=atX5O68KLgFkQgWy) 6. [Demo of Forge app with config option](https://youtu.be/grkNhzRPe2g?si=cwW_BI70aJQzyj0p) 7. [Intro Carousel component using Forge UI components](https://youtu.be/cuKadhByHZ0?si=Jrp8RR04m7H0PBZb) *** ### [Wireframify](https://chrome.google.com/webstore/detail/wireframify/denkephjglddepmhdlaaigjionglkdbb) _Instantly transform any website into its wireframe layout with a single click._ Wireframify is a Chrome extension that allows users to view the wireframe of any webpage. Preview the wireframe of any website with one click. The primary function is to simplify and present the structural layout of a website without its detailed design elements. **Platform**: [Chrome Web Store](https://chrome.google.com/webstore/detail/wireframify/denkephjglddepmhdlaaigjionglkdbb?hl=en) With a **4-star rating** and more than **5,000** people downloading it. *** #### [Atlassian Forge snippets VS Code Extension](https://marketplace.visualstudio.com/items?itemName=AnilKumar.forge-snippets) This extension for Visual Studio Code adds snippets for [Forge UI](https://developer.atlassian.com/platform/forge/ui-kit/). Supports .jsx file extension. **Platform**: [VS Code Marketplace](https://marketplace.visualstudio.com/items?itemName=AnilKumar.forge-snippets) ![](/assets/demo.gif) --- Source: https://www.anilkumark.de/work/frontend/canto-cumulus-portal/ # Canto Cumulus Portal **Role: Senior Javascript Developer** **Year: 2015 to 2017** **Product site:** [**cumulus portals**](https://www.canto.com/cumulus/portals/) #### Outcome * UI plugins to quickly build digital assets management solutions, easy for sharing and collaboration. #### Output * Building a publishing platform that allows users to create and share the collection of digital assets. * Develop the Front-end with HTML5, LESS using the [UI patterns](http://patternlab.io/about.html) approach using JavaScript and [Angularjs](https://angularjs.org/). ![](/assets/hero-man_cut_1500x901_icg6pb.webp) ![](/assets/Samsung_Portal_fokbsm.webp) ![](/assets/Portals_video_vdshgb.webp) ![](/assets/Portals_SelfService-1024x643_foghcw.webp) ![](/assets/Portals_Search-1024x666_rgtssy.webp) ![](/assets/Portals_Email_Attachment-1024x659_rwrcuo.webp) #### [Cumulus Portals Plugins](https://speakerdeck.com/anilkumar/cumulus-portals-plugins-intro-and-demo) Developed an intuitive plugin integration platform, empowering users to craft custom plugins without compromising simplicity. Through strategic front-end architecture and a streamlined interface, I ensured a balance between flexibility and user-friendliness, enhancing the overall developer experience on Portals Plugin. ![](/assets/Screenshot%202023-10-10%20at%2015.14.41.png) ![](/assets/Screenshot%202023-10-10%20at%2015.14.59.png) ![](/assets/Screenshot%202023-10-10%20at%2015.14.50.png) --- Source: https://www.anilkumark.de/work/frontend/headless-and-jamstack-talks/ # Headless and JAMstack talks ### At JAMstack Berlin meetup ### At JAMstack Porto meetup ### At WeAreDevelopers Conference ### Discussion around HEADLESS and Developer Experience ### Visual editing using React components and CMS --- Source: https://www.anilkumark.de/work/frontend/ # Frontend Experience - [SAP — HCM HR Renewal](/work/frontend/sap-hcm-hr-renewal) - [Canto Cumulus Portal](/work/frontend/canto-cumulus-portal) - [one.com Web Editor](/work/frontend/one.com-web-editor) - [API & SDK work](/work/frontend/api-and-sdk) - [App Innovations — workflows across platforms](/work/frontend/app-innovations-enhancing-workflows-across-platforms) - [Headless & JAMstack talks](/work/frontend/headless-and-jamstack-talks) --- Source: https://www.anilkumark.de/work/frontend/one.com-web-editor/ # one.com Web Editor **Role: Javascript Developer** **Year: 2013 to 2015** **Product site:** [**Web Editor**](https://www.one.com/en/website-builder) #### Outcome * **Improved** Web editor **usability**. * **5 times faster** way to create a customizable **contact form** on the Web editor. #### Output * Implementing and developing interface for UI components and properties in Web Editor using **HTML5**, **LESS** and **ExtJS** framework. * Revamped global style design interface with customizable, reusable UI components for consistent and improved page **usability**. * Created the full stack contact form component using HTML5, LESS, ExtJS, and NodeJS. ![Image slider component](/assets/Website_Builder_and_iTunes_and_Skype_nv8x9i.webp) ![Button component](/assets/Website_Builder_3_ukcm7b.webp) ![Form component](/assets/Website_Builder_4_cyeep0.webp) Website editor using ExtJS --- Source: https://www.anilkumark.de/work/frontend/sap-hcm-hr-renewal/ # SAP HCM HR Renewal **Role: Frontend Web Developer** **Year: 2011 to 2013** **Product site:** [**SAP HCM HR Renewal**](http://scn.sap.com/community/erp/hcm/blog/2012/10/10/sap-new-hr-renewal-functionality-and-roadmap) #### Outcome * **Improved productivity** of the HR application. #### Output * Led team of 5 Frontend developers and developed the HCM HR Renewal web application. * Developing Client-side web application for SAP HR HCM using Javascript MVC framework with product standards – web accessibility, performance, usability, and security. * Providing Training on JavaScript, CSS3 and HTML5 to non-web-platform SAP teams. * Consulting with US, Europe and China customers, implementing SAP HR product based on feedback. ![](/assets/image001_g1tuit.webp) ![](/assets/image001_1_uuaejn.webp) --- Source: https://www.anilkumark.de/work/pmm/bots-and-humans-devworld-2026/ # Bots and humans, a devWorld 2026 talk on the closed web and AI agents ![Anil on stage at devWorld Conference Amsterdam, slide reading "We now live in a Closed Web"](/assets/devworld-2026-closed-web.jpg) **devWorld Conference 2026**, Amsterdam, May 2026. [Watch the full talk on YouTube](https://youtu.be/-YJHOsvUyPc?si=zfBNfLrnI_9C7CJ9). ## The opening hook I started with one number. In March 2026, Mintlify published documentation traffic data showing Claude Code alone made nearly 199 million requests to docs in a single month, more than Chrome on Windows in the same window. If you build developer tools, your biggest reader isn't a developer anymore. It's the agent the developer sends to your docs. That number sets up the rest of the talk. The web is being read by machines at human scale. The infrastructure underneath it wasn't designed for that, and the infrastructure on top of it is fighting back. ## Part 1, the closed web Four beats of history in 60 seconds: - 2000s, open web. You curl a URL, you get HTML. - 2010s, free APIs. Twitter, Maps, Facebook give you keys, billions of apps get built. - 2018, the platforms realize data is the product. APIs get priced or shut down. Twitter starts gating, Maps starts charging. - Today, the closed web. Bots are blocked by default. CAPTCHAs gate every meaningful read. Cloudflare's one-click AI crawler blocker, shipped last July, has blocked over 400 billion bot requests in its first five months. ![Anil mid-presentation, Bright Data logo on the stage screen](/assets/devworld-2026-hero.jpg) The result is a strange duality. Anthropic, OpenAI, Cursor, and Copilot's agents are reading documentation at internet scale. Their data sources are getting blocked at internet scale. Both things are true at once. I quoted Dhruv Batra, CTO of Yutori, on what comes next: > We built the web for human consumption. For a long time, we're going to share this space. Machines acting like humans, clicking buttons, scrolling PDFs, doing OCR on the fly. That's what it looks like for many years until the transition is complete. ## Part 1.5, the DIY trap Say you want to extract product data from a million Amazon pages for a competitive-intel tool or to train a RAG application on fresh inventory data. The naive paths fall over fast. Asking an LLM agent to do it works for tens of pages and breaks at thousands. One task at a time. Multiply the per-task cost by a million. The agent still hits CAPTCHAs and IP blocks. So you build it yourself. Each step looks reasonable in isolation: 1. **Selenium or Playwright.** Works for the first fifty pages, then your IP gets noticed. 2. **Add a proxy pool.** Rotate IPs. Now you're past IP blocks but you're hitting CAPTCHAs. 3. **Add a CAPTCHA solver.** OK. Now TLS fingerprinting recognizes your handshake. 4. **Add fingerprint rotation.** And mouse-movement mimicking. And user-agent rotation. ![DIY stack slide: Selenium and Playwright, proxies, CAPTCHA solvers, fingerprint rotation](/assets/devworld-2026-build-yourself.jpg) The original goal was to get data. You're now maintaining anti-bot infrastructure. And it's still brittle, the DOM shifts, your selectors break, BeautifulSoup returns nulls that silently feed your AI pipeline bad data downstream. The framing I landed on for the room: this isn't a bug, it's an architectural problem. ## Part 2, the live demo The plan was simple. Pick a real e-commerce site, prompt Bright Data Scraper Studio with the URL, get a working API back. Scale it from there. Because I was in Amsterdam, I asked an attendee in the break what the most popular Dutch e-commerce site was. Answer: coolblue.nl. I picked a smartphone product page live on stage. The flow: 1. Pasted the coolblue.nl product URL into Scraper Studio with a one-line prompt about what I wanted (title, price, rating, reviews, description). 2. The tool analyzed the page and proposed a schema. I removed two fields I didn't need. 3. Approved the schema. Scraper Studio generated a collector and an API endpoint. 4. Called the endpoint from Postman, got a clean JSON response with the requested fields. 5. Asked the coding agent in natural language to remove the ratings field. It edited the generated code, saved a new version, and the next API call returned without ratings. ![Live demo of Bright Data Scraper Studio showing a coolblue.nl collector run](/assets/devworld-2026-dashboard.jpg) Three things I wanted the room to take away from the demo: - **Prompt plus URL to API in under a minute.** No DOM inspection, no selector writing, no CAPTCHA setup. - **Self-healing.** When the DOM changes or you want different fields, you ask in natural language. The collector re-derives the schema and patches itself. - **The code isn't a black box.** You can read it, version it, edit it, fork it. You own the output, not just the data. The closing CTA was a $50 credit QR code for the audience to try Scraper Studio. ## Behind the scenes A few notes on giving this one, separate from the talk's content. **It was my first conference talk in nearly two years.** The muscle comes back faster than you expect, but the prep curve is steeper than I remembered. The first dry run I did in the office sounded like I was reading bullet points. By the third one the cadence was back. **I always carry a backup recording for live demos.** Conference wifi is the most volatile variable in a talk. I had a screen-recorded version of the full coolblue.nl flow ready to drop in if the live one failed. This time the wifi held, the live scrape ran clean, and the recording stayed in the folder. But carrying the backup is the difference between a confident demo and a nervous one. **Picking the demo site live is worth the small risk.** Asking an attendee for the most popular Dutch e-commerce site between sessions meant the demo wasn't canned. It cost me about 30 seconds of context-setting on stage and bought back five times that in audience trust. **Every talk sharpens the storytelling.** Picking what to focus on, what to cut, how to read the room, when to slow down for the data point, when to speed past the technical scaffolding. The story has to land for this audience in this room on this day. devWorld's crowd was hands-on engineers, not architects, so I leaned harder into the live demo and lighter on the platform-history exposition than I would for a different room. ## Watch and related - [Full talk on YouTube](https://youtu.be/-YJHOsvUyPc?si=zfBNfLrnI_9C7CJ9), devWorld Conference channel - [Bright Data Scraper API and Scraper Studio](https://brightdata.com/products/web-scraper) - [All my talks since 2015](/public-speaking) - [Parallels Browser Isolation case study](/work/pmm/parallels-browser-isolation) --- Source: https://www.anilkumark.de/work/pmm/ # Technical Product Marketing - [Parallels Browser Isolation](/work/pmm/parallels-browser-isolation) - [Lokalise Developer Hub](/work/pmm/lokalise-developer-hub) - [Lokalise Flutter SDK](/work/pmm/lokalise-flutter-sdk) - [Lokalise Demo App — AI Emporium](/work/pmm/lokalise-demo-app-ai-emporium) - [Software Localization Workflow](/work/pmm/software-localization-workflow) - [Technical Partner Marketing](/work/pmm/technical-partner-marketing) --- Source: https://www.anilkumark.de/work/pmm/lokalise-demo-app-ai-emporium/ # Lokalise Demo App - AI Emporium ![Lokalise Developer Hub](/assets/241107743-1d76ddf9-5086-4de2-9ae4-d7a91b32f103.png) ### Introduction As a Senior Product Marketing Manager, I led the development and successful launch of the AI Emporium, an innovative demo app designed to highlight Lokalise's capabilities in a real-world application. The AI Emporium is a revolutionary demo app that combines Lokalise, GitHub actions, and Nextjs to help sales teams showcase translation changes made via Lokalise on a real application instantly. This provides prospects with faster validation and an enriched experience. ### Problem Previously, the sales team was limited to using simple "Hello World" examples during prospect demos, which lacked real-world context and usability for developers. There was a significant need for an impactful and genuine use case demo to provide a more tangible experience for prospective developers. ### **Outcome** With the launch of the AI Emporium, the sales team is now able to succinctly demonstrate Lokalise's capabilities using tools that developers are already familiar with, bypassing the need to directly show Lokalise. This has effectively reduced the sales cycle as prospect tech teams can quickly validate Lokalise's utility and potential. ### **Tactics** In creating the AI Emporium, I employed a blend of technical product marketing strategies, which included conducting extensive research on typical workflow processes and working closely with the Customer Success, Support, and Solution Engineering teams to design an app that aligns with our Ideal Customer Profile (ICP). ### **Market Research** To further our understanding of the market needs, I conducted research on how other SaaS products are providing demos and investigated the typical CI/CD workflows employed by software tech teams. This invaluable data provided the foundation upon which we developed our tailored solution. ### **Sales Enablement** To ensure the wider team was adequately prepared to utilize the AI Emporium, I spearheaded training sessions for the sales and customer success teams, providing them with quick start guides to effectively demo the app. ### Assets 1. [AI emporium lokalise demo app](https://github.com/lokalise/ai-emporium-lokalise-demo-app) 2. [How to continuously localize using GitHub Actions](https://lokalise.com/blog/how-to-continuously-localize-your-front-end-resource-files-using-github-actions/) 3. [Using GitHub Actions for Continuous Localization](https://ericsilberstein1.substack.com/p/using-github-actions-for-continuous?r=21q6j1\&utm_campaign=post\&utm_medium=web) --- Source: https://www.anilkumark.de/work/pmm/lokalise-developer-hub/ # Lokalise Developer Hub ![Lokalise Developer Hub](/assets/1688365569681.jpeg) ### Introduction As a Senior Product Marketing Manager, I spearheaded the creation and successful launch of the [Lokalise Developer Hub](https://developers.lokalise.com/), an all-inclusive platform for developer tools and resources aimed at automating and customizing localization workflows. This was achieved through in-depth market analysis, strategic product positioning, and technical Marketing tactics. ### Problem The pre-existing _**scattered**_ API documentation, tutorials on blog posts, and product information on Intercom articles caused **confusion** and **slowed** the adoption process for developers wanting to utilize Lokalise's features. Our challenge was to drive awareness and adoption of developer tools through strategic go-to-market planning, compelling positioning, engaging demos, and active community participation. ### **Outcome** The launch of the Lokalise Developer Hub led to an **increase** in **API calls** from the hub, elevated web **traffic**, and improved the **developer experience** by offering a centralized location for all necessary materials. This consolidation not only **quickened** the evaluation process for prospective developers but also significantly increased **customer satisfaction** and **adoption**. ### **Tactics** I used a blend of **technical product marketing strategies** to communicate complex product features in an understandable manner to a highly technical audience. I developed a deep understanding of our product and its market, synthesizing technical information and conveying it effectively to drive adoption. Collaboration with cross-functional teams, including product, marketing, partnership, and sales, was key to our successful outcomes. ### **Market Research** The initial market analysis included a benchmark report comparing developer portals from Stripe, Twilio, and Slack. This critical step was accompanied by thorough research on developer hub platforms to decide on a '**build vs. buy**' approach. ### **Sales Enablement** To ensure the wider team was equipped to promote the Developer Hub, I led sales and customer success training sessions, providing sales decks to explain concepts, and created demo sandboxes and getting-started guides. ### **Tactics for Adoption** To further boost adoption, I utilized various tactics such as creating demo videos, conducting user testing with developers and early adopters, and improving developer examples based on feedback. Demo example projects were created to facilitate faster adoption. ### Testimonials What feedback did customer developers provide about the Lokalise Developer Hub? ![](/assets/Creme%20Brown%20Beige%20Customer%20Testimonial%20Story.png) --- Source: https://www.anilkumark.de/work/pmm/lokalise-developer-hub/launch-assets-list/ # Launch Assets List ### Demo projects [Lokalise demo apps repository](https://github.com/lokalise/apps/tree/main) ### Navattic Lokalise-GitHub integration product demo [Lokalise-GitHub integration demo](https://lokalise.navattic.com/ee50u2h) ### Social Media content * [On LinkedIn](https://www.linkedin.com/feed/update/urn:li:activity:6966056621433069569/) * [On Twitter](https://twitter.com/lokalise/status/1554829957695623168) * [Lokalise launch blog](https://lokalise.com/blog/introducing-developer-hub-a-new-resource-for-developers/) ### Demo videos [How do I test the Lokalise API on this page?](https://developers.lokalise.com/reference/lokalise-rest-api) --- Source: https://www.anilkumark.de/work/pmm/lokalise-flutter-sdk/ # Lokalise Flutter SDK ![Lokalise Developer Hub](/assets/1688365404674.jpeg) ### Introduction As a Senior Product Marketing Manager, I championed the conception and successful launch of **Lokalise Flutter SDK**, a comprehensive toolkit for Flutter developers to streamline their localization processes. This initiative was brought to life through thorough market research, strategic product positioning, and technical marketing tactics. ### Problem With the rapidly growing popularity of [**Flutter**](https://flutter.dev/), there was a clear need to expand our support beyond the existing iOS and Android SDKs. The process of localization for Flutter developers was inherently complex and time-consuming, creating a pressing demand for a more efficient, streamlined approach. Moreover, recurring complaints from our existing customers about the lack of a Flutter SDK signaled a crucial gap in our product offering. This gap was not only causing dissatisfaction among our customer base but was also leading to missed opportunities and lost deals as potential customers sought Flutter support we were unable to provide. ### **Outcome** The launch of the Lokalise Flutter SDK resulted in a substantial **increase in the adoption** of Lokalise's services by customers, heightened web traffic, and enhanced the developer experience by providing a comprehensive and efficient localization solution. This consolidation accelerated the development process for Flutter developers, leading to a significant boost in customer satisfaction and adoption. ### **Tactics** Leveraging a variety of technical product marketing strategies, I was able to articulate complex product features to our highly technical audience in a clear and compelling manner. Developing an in-depth understanding of our product and its market, I was able to distill technical details and effectively convey them to drive product adoption. Working closely with cross-functional teams, including product, marketing, and sales, was pivotal to our successful outcomes. ### **Market Research** Market Research A preliminary market analysis was performed, which included a detailed comparison of localization solutions provided by key competitors and cross-platform mobile frameworks. ### **Sales Enablement** In order to empower the wider team to effectively promote the Flutter SDK, I led training sessions for sales and customer success teams, provided sales decks to explain the SDK's unique features, and created demo sandboxes and starter guides. ### **Tactics for Adoption** To drive product adoption, I implemented various tactics such as creating demo videos, conducting user testing with Flutter developers and early adopters, and refining our SDK based on user feedback. Demo projects were developed to showcase the functionality of the SDK and to expedite developer adoption. ### Testimonials What did customers say about the Lokalise Flutter SDK? ![](/assets/FlutterSDK.png) --- Source: https://www.anilkumark.de/work/pmm/lokalise-flutter-sdk/launch-assets-list/ # Launch Assets List ### Flutter SDK Landing Page [https://developers.lokalise.com/page/flutter-sdk-with-ota](https://developers.lokalise.com/page/flutter-sdk-with-ota) ### Flutter SDK Webinar [Live webinar: Learn how to localize apps on the fly](https://learning.lokalise.com/Mobile-OTA-SDK-Webinar-Recording.html) ### Navattic product demo [Flutter SDK workflow demo](https://lokalise.navattic.com/5f10ajp) ### Demo project [Lokalise Flutter SDK demo app](https://github.com/lokalise/apps/tree/main/examples/flutter-ota) ### Social Media content * [On LinkedIn](https://www.linkedin.com/feed/update/urn:li:activity:7031631569513533440/) * [On Twitter](https://twitter.com/lokalise/status/1554829957695623168) * [Lokalise launch blog](https://lokalise.com/blog/everything-you-need-to-know-about-our-over-the-air-changes-flutter-sdk-and-public-api/) ### Blog * [Everything you need to know about our over-the-air changes, Flutter SDK, and public API](https://lokalise.com/blog/everything-you-need-to-know-about-our-over-the-air-changes-flutter-sdk-and-public-api/) * [Lokalise Flutter SDK and working with over-the-air(OTA) flow](https://lokalise.com/blog/lokalise-flutter-sdk-and-working-with-over-the-air-flow/) ### ProductHunt launch [Lokalise Flutter SDK on ProductHunt](https://www.producthunt.com/products/lokalise-flutter-sdk#lokalise-flutter-sdk) ### Documentation * [Flutter SDK getting started guide ](https://developers.lokalise.com/docs/flutter-sdk) * [Lokalise Flutter SDK package](https://pub.dev/packages/lokalise_flutter_sdk) * [Over-the-air (OTA) translations](https://developers.lokalise.com/docs/ota-sdk) * [Tutorial](https://lokalise.com/blog/lokalise-flutter-sdk-and-working-with-over-the-air-flow/) #### [Meme](https://www.linkedin.com/posts/lokalise_mobileapp-appdevelopment-localization-activity-7071448537158295552-0nSo) ![](/assets/1685964711732%20(1).jpeg) #### Command Of The Message ![More info on CoM: https://www.forcemanagement.com/blog/whats-the-meaning-of-command-of-the-message](/assets/Screenshot%202023-10-07%20at%2023.22.12.png) ### Demo videos --- Source: https://www.anilkumark.de/work/pmm/parallels-browser-isolation/ # Parallels Browser Isolation ![Source: Parallels Browser Isolation](/assets/PBI-animation-compressed.gif) ### Introduction As a Senior Technical Product Marketing Manager, I led the successful launch of Parallels Browser Isolation, an advanced security solution designed to protect users from web-based threats. This initiative was realized through market analysis, strategic positioning, and innovative marketing strategies, ensuring a robust defense against cyber risks while maintaining seamless user experiences. ### Problem The rise of SaaS applications accessed via browsers has led to increased cyber attacks. Traditional security measures are inadequate, causing breaches and data compromises. Customers need effective browser isolation solutions to enhance cybersecurity and operational efficiency, highlighting a critical market gap. ### **Outcome** The launch of Parallels Browser Isolation significantly improved cybersecurity for our customers, reducing web-based threats and data breaches. It enhanced IT efficiency by simplifying browser security management and led to increased customer satisfaction and adoption. This innovative solution strengthened our market position as a major player in secure web access. ### **Tactics** With Parallels' strong presence in end-user computing and the rise of SaaS adoption, launching Parallels Browser Isolation to provide comprehensive security solution for desktops, servers, and SaaS apps. Security is a new category for Parallels, so collaborating with industry experts and analysts for continuous feedback on marketing materials. Focusing on cross-selling with Parallels RAS and Secure Workspace, enabling and educating partners, and nurturing prospects through targeted email campaigns and feedback-driven improvements. ### **Market Research** Analyzing secure web access solutions, including pricing, features, customer reviews, and analyst insights, to better position against competitors. ### **Sales Enablement** Equip sales teams with battle cards for competitive enterprise browsers, highlight Parallels Browser Isolation's defense against cyber attacks, and provide tools for identifying ideal customers with a concise pitch deck, 1-pager and data sheet. ### Testimonials > _“Browser isolation is getting the attention and investment that is due in the market. Strategically, Zero Trust requires that we don’t trust the internet, and we don’t trust our users not to interact with malicious content. Using Parallels Browser Isolation aligns with that requirement and can help a business enable this critical strategy. And it does so without negatively impacting the user experience” -_ Chase Cunningham, Dr. Zero Trust and cybersecurity expert --- Source: https://www.anilkumark.de/work/pmm/parallels-browser-isolation/launch-assets-list/ # Launch Assets List ### Parallels Browser Isolation Landing Page [https://www.parallels.com/products/browser-isolation/](https://www.parallels.com/products/browser-isolation/) ### Product demo ### Product techbytes videos [Parallels Tech Bytes - Parallels Browser Isolation videos](https://www.youtube.com/playlist?list=PLFEwXRyfSuQvZLQ5acuANDRWi6aoorhch) ### Product Datasheet [Parallels Browser Isolation Datasheet](https://www.parallels.com/static/pl/fileadmin/res/doc/pbi/datasheet/pbi-datasheet-general-letter.pdf) ### Social Media content * [On LinkedIn](https://www.linkedin.com/feed/update/urn:li:activity:7031631569513533440/) ### Blog * [Announcing Parallels Browser Isolation: Your gateway to safer web access with enhanced policy control](https://www.parallels.com/blogs/ras/introducing-parallels-browser-isolation/) * [Marching ahead with the Parallels platform](https://www.parallels.com/blogs/ras/pbi-launch-day/) * [Parallels Adds Remote Browser Isolation Solution to its Holistic Workspace Portfolio, Enabling Secure SaaS, and Web Application Access](https://www.alludo.com/en/newsroom/press-releases/20240312-parallels-adds-remote-browser-isolation-solution/) ### Infographic ![Source: Zero Trust Browsing](/assets/Screenshot%202024-08-14%20at%2007.55.58.png) ![Source: Secure web access](/assets/Screenshot%202024-08-14%20at%2007.57.23.png) ### Documentation ### Demo videos --- Source: https://www.anilkumark.de/work/pmm/software-localization-workflow/ # Software Localization Workflow ![Lokalise Developer Hub](/assets/3576916-Last-Step_localization_workflow.png) ### Introduction In my role as a Senior Product Marketing Manager, I revamped Lokalise's guide for software localization workflows. The primary aim was to enhance the use of branching functionality, thereby providing an efficient version control system tailored for localization. Balancing software development and localization can pose hurdles. Tasks like managing numerous branches for development and translation, merging changes, and sustaining version control require appropriate tools and strategies. This is where the Lokalise workflow guide comes into play. ### Problem The main issue arose from treating Lokalise branching like Git branching, which often led to confusion and, occasionally, loss of data during conflict resolution. Lokalise's branching was purposefully designed for localization tasks. ### **Outcome** Implementing a thorough localization workflow guide effectively addressed the challenges of confusion that stemmed from treating Lokalise branching like Git branching. This not only reduced the time dedicated to translation management—accelerating the software development process—but also enhanced developer engagement with the platform due to its optimized functionality and user-friendliness. The streamlined processes led to increased satisfaction among both developers and translators. ### **Tactics** A combination of technical product marketing strategies and practical product management techniques were used to optimize the software localization workflow. Deep understanding of our product, its audience, and the localization industry's pain points played a crucial role. Collaboration with product, customer success, solution engineering, and sales teams were vital in the successful execution of the strategies. ### **Market Research** To gain insights on best practices, we looked into the software localization workflows of several established tech companies. This allowed us to compare the functionality and efficiency of their localization workflows and take cues for our own. This crucial step was also accompanied by extensive research on version control platforms to decide on the best approach for Lokalise's localization branching. ### **Tactics for Adoption** To further boost adoption, I utilized various tactics such as creating demo videos, conducting user testing with developers and early adopters, and improving developer examples based on feedback. Demo example projects were created to facilitate faster adoption. ### **Discovery of Last-Step, Development-Stage, and Testing-Stage Localization** Through an in-depth understanding of the software development lifecycle, we identified three key stages in the localization process that needed attention: [Last-Step Localization](https://developers.lokalise.com/docs/software-localization-workflow#last-step-localization-workflow-without-lokalise-branching), [Development-Stage Localization](https://developers.lokalise.com/docs/software-localization-workflow#development-stage-localization), and [Testing-Stage Localization](https://developers.lokalise.com/docs/software-localization-workflow#testing-stage-localization). ![](/assets/a94621d-Separate_testing_environments_for_localization_changes_before_merge_with_Lokalise_branching_1.png) ![](/assets/f0d3d83-Development-stage_localization_without_using_Lokalise_branching_1%20(1).png) ![](/assets/3576916-Last-Step_localization_workflow%20(1)%20(1).png) ### **Tactics for Adoption** To further encourage adoption, we leveraged a variety of methods such as creating informative videos demonstrating the new workflows, conducting user testing with developers and translators, and continually iterating on the workflow based on their feedback. --- Source: https://www.anilkumark.de/work/pmm/technical-partner-marketing/app-launches/ # App launches 1. Worked with Partner Marketing and Tech teams on app launch strategy. 2. Developed an [App launch matrix ](https://docs.google.com/spreadsheets/d/1NZvPCNWHfHCfNMdrNCEpi6QJyFegVuNa/edit?usp=sharing\&ouid=106195931215041672658\&rtpof=true\&sd=true)for all releases, determining the timeline and assets needed. 3. Developed [App development guidelines](https://developers.lokalise.com/docs/guidelines-tips) and [Marketplace publishing process](https://developers.lokalise.com/docs/review-and-publish-your-app) in collaboration with the Product team. 4. Guided the creation of co-marketing materials. #### [Braze and Lokalise](https://docs.lokalise.com/en/articles/6025231-braze) [App on the Marketplace](https://lokalise.com/product/apps/content-management/braze) ![Braze + Lokalise integration](/assets/Braze_app.png.webp) #### [Contentstack and Lokalise ](../lokalise-flutter-sdk) [App on the Marketplace](https://lokalise.com/product/apps/content-management/contentstack) ![Contentstack + Lokalise](/assets/Contentstack.png.webp) #### [Ditto and Lokalise](https://docs.lokalise.com/en/articles/7549522-ditto) ![Ditto + Lokalise integration](/assets/Ditto_Words_Whats_new_newsletter.png.webp) #### [Make and Lokalise](https://lokalise.com/product/apps/notifications-and-events/make) [Documentation](https://www.make.com/en/help/apps/file-and-document-management/lokalise) ![](/assets/Screenshot%202023-10-08%20at%2001.45.10.png) --- Source: https://www.anilkumark.de/work/pmm/technical-partner-marketing/great-ux-with-lokalise-and-vercel/ # Great UX with Lokalise and Vercel ![Edge + localization = Great UX](/assets/Copy%20of%20Add%20a%20subheading%20(1).png) ### Introduction As a Senior Product Marketing Manager, I partnered with Lokalise and Vercel's Partnership Managers to craft a narrative emphasizing **Lokalise's localization personalization** and **Vercel's swift content delivery via its edge network**. This collaboration enhanced user experience and, through a [demonstrative](https://github.com/lokalise/ai-emporium-lokalise-demo-app) example, empowered agency partners to assess partnership avenues. This strategic alliance led to a surge in agency partnerships, subsequently boosting new sales opportunities. ### **Outcome** The strategic collaboration between Lokalise and Vercel resulted in a powerful narrative that showcased Lokalise's expertise in localization personalization and Vercel's rapid content delivery through its edge network. This synergy not only **elevated the user experience** but also served as a **potent example for agency partners to evaluate potential collaborations**. As a result, there was a marked **increase in agency partnerships**, which in turn amplified **new sales opportunities** and expanded the reach of both brands. ### Assets 1. [AI emporium lokalise demo app](https://github.com/lokalise/ai-emporium-lokalise-demo-app) 2. [How to continuously localize using GitHub Actions](https://lokalise.com/blog/how-to-continuously-localize-your-front-end-resource-files-using-github-actions/) 3. [Using GitHub Actions for Continuous Localization](https://ericsilberstein1.substack.com/p/using-github-actions-for-continuous?r=21q6j1\&utm_campaign=post\&utm_medium=web) --- Source: https://www.anilkumark.de/work/pmm/technical-partner-marketing/ # Technical Partner Marketing ![Partnership](/assets/Copy%20of%20Add%20a%20subheading.png) ### [Great UX with Lokalise and Vercel Partnership](/great-ux-with-lokalise-and-vercel) Boosted new partnership opportunities by crafting a compelling narrative involving Vercel and Lokalise. ### Partnership via community 1. Introduced [MACH alliance](https://machalliance.org/) to [Vercel](https://vercel.com/). 2. Organized [HEADLESS Meetup events in Berlin](../../community/headlessons), connecting digital agencies with HEADLESS technology partners. ### [Build your dream workflow using Atlassian Forge](https://blog.developer.atlassian.com/build-your-dream-workflow-using-forge/) Championed Atlassian's Forge in marketing campaigns, showcasing its potential for seamless app development. Highlighted innovative integrations, such as Figma-Confluence synergy and WhatsApp-driven Jira tasks, to demonstrate value to potential technical partners. [Read more details here](https://anilkumark.gitbook.io/portfolio/frontend-work/app-innovations-enhancing-workflows-across-platforms#atlassian-forge-apps) ![Source: https://blog.developer.atlassian.com/build-your-dream-workflow-using-forge/](/assets/1f9f9daa-ce61-4338-858d-4fee920cce65-990x445.png) ### Tech Partner landing page on [Lokalise Marketplace](https://lokalise.com/product/apps) Implemented a tech partner landing page on Lokalise Marketplace, enhancing integration adoption, streamlining the integration initiation process, and ensuring accessible support. ![https://lokalise.com/product/apps/customer-service/dixa](/assets/Screenshot%202023-10-02%20at%2012.30.47.png) ![https://lokalise.com/product/apps](/assets/Screenshot%202023-10-02%20at%2012.33.11.png) ![https://lokalise.com/product/apps/notifications-and-events/make](/assets/Screenshot%202023-10-02%20at%2012.32.15.png) ### Testimonials What feedback did the Partnership, Sales, and Customer Success team share about Anil? ![Testimonials from my colleagues at Lokalise](/assets/Partnership%20(1).png) --- Source: https://www.anilkumark.de/work/tpm/agile-product-development/ # Agile Product Development #### Agile Product Development Experience With deep experience across Agile roles—Frontend Developer, QA Engineer, Scrum Master, Product Owner, and Technical Product Manager—I’ve built a range of technical products within Agile and Scrum environments, always focusing on outcomes that drive value. #### **Building Product Communities in Berlin** Pre-pandemic, I organized a thriving Product Management community in Berlin, creating a space for knowledge-sharing and collaboration. These events enabled product professionals to explore Agile practices like story mapping, fostering a shared focus on outcome-driven development. #### Story mapping I had the privilege of collaborating with Jeff Patton to explore Agile methodologies and story mapping, focusing on how these approaches can enhance outcome-driven product development. ![Anil with Jeff Patton in Berlin](/assets/Anil%20with%20Jeff%20Patton.png) ### My talks around Agile Development ### Outcome focused Technical Product Teams ### Improve Developer Expereince with Story Mapping ### Behavior Driven Development ### How to build your dream workflow with Atlassian Forge? ### Improve Developer Expereince with Story Mapping --- Source: https://www.anilkumark.de/work/tpm/commercetools-ui-components/ # commercetools UI components **Role: Technical Product Manager** **Year: 2020 - 2021** **Product site:** [**https://uikit.commercetools.com/**](https://uikit.commercetools.com/) #### Outcome * Empowering product teams to focus on delivering customer value. * UI extension tools to build commerce solutions quickly. I championed the **lifecycle management** and **go-to-market strategy** for our UI extension tools (UIKIT) design system, which significantly streamlined the process of building **custom commerce experiences**. My customer-centric approach, coupled with a deep understanding of market trends and developer needs, resulted in **increased adoption, reinforcing commercetools stature as a leader in innovative eCommerce solutions.** --- Source: https://www.anilkumark.de/work/tpm/contentful-forma-36/ # Contentful Forma 36 **Role: Technical Product Manager - Design systems** **Year: 2021** **Product site:** [**https://f36.contentful.com/**](https://f36.contentful.com/) #### Outcome * UI tooling and documentation for faster apps development. #### Details are coming soon... --- Source: https://www.anilkumark.de/work/tpm/ # Technical Product Manager - [Contentful — Forma 36 design system](/work/tpm/contentful-forma-36) - [commercetools — UI components](/work/tpm/commercetools-ui-components) - [Agile Product Development](/work/tpm/agile-product-development) --- Source: https://www.anilkumark.de/writing/technical-pmm-vs-pmm-vs-devrel/ # Technical PMM vs PMM vs DevRel: which role does what? A product marketing manager owns the story a product tells and the revenue it drives. A technical PMM owns the same, for products bought by developers, where the story must survive technical scrutiny. Developer relations owns the relationship with the developer community itself. The roles overlap in activities but differ completely in what they are accountable for. Confuse the accountability and you break all three jobs. I have watched it happen from the inside: I am a Senior Technical Product Marketing Manager at Bright Data, I have run a developer community as a founder, and I have given talks at DevRel meetups about community-driven developer experience. This piece draws the boundaries the way I wish someone had drawn them for me. ## Why do these three roles get confused? Because from the outside they produce similar-looking output: blog posts, conference talks, demos, launch announcements. A hiring manager sees three people who "talk to developers" and assumes they are interchangeable. They are not, and the tell is what happens when each one fails. If PMM fails, the product ships and nobody understands why it matters. If the technical PMM fails, developers hear the story, try the product, and bounce off a broken quickstart. If DevRel fails, the company loses its ear to the ground: no early feedback, no trusted voices, no one vouching for you in the channels where developers actually decide. ## What does a product marketing manager own? The classic PMM playbook: segment the market, position against real alternatives, build the messaging hierarchy, plan the launch, and arm sales and demand gen with what converts. Accountability is commercial: pipeline influenced, win rates, launch outcomes. A great PMM at a CRM company never needs to read the SDK, because the buyer never will either. I wrote about the full role in [What does a technical product marketing manager do?](/writing/what-does-a-technical-product-marketing-manager-do), including my actual workload split. The short version: 50 to 70 percent of my time is launches and go-to-market. That part is the same job as any PMM. The difference is the audience. ## What makes a technical PMM different? The audience's allergy to faked fluency. Developers detect instantly when marketing does not understand the product, so a technical PMM does personally what a classic PMM can delegate: build the demo, run the quickstart to see where it breaks, read the API reference before writing the one-pager. The deliverables change accordingly. My portfolio is not decks: it is a [demo app that replaced hello-world sales demos](/work/pmm/lokalise-demo-app-ai-emporium), a [developer hub](/work/pmm/lokalise-developer-hub) we usability-tested on internal engineers, and at Bright Data I lead documentation, because for developer products the docs are the marketing. In 2026 that increasingly means the first reader of your docs is an AI agent acting for a developer, which I talked about at [devWorld 2026](/talks/bots-and-humans-devworld-2026). Accountability stays commercial: I am measured on pipeline from the products I lead, plus adoption metrics like time to first successful API call. That last part matters for the DevRel comparison, so hold onto it. ## What does DevRel own, and what should it never be measured on? Developer relations owns the health of the relationship between the company and its developer community: feedback loops into product, trusted presence in the places developers gather, education that builds capability rather than pipeline, and the credibility that makes developers give you a second chance after a bad release. The canonical mistake is measuring DevRel on lead generation. Community members can tell when a relationship is being farmed for MQLs, and the advocates burn out or quit. DevRel produces business value, but it shows up as product signal, retention, word of mouth, and qualified feedback, not as top-of-funnel volume. If you want top-of-funnel from technical content, that is a marketing job, and it is fine to staff it as one; just do not call it DevRel. I have sat on the community side of this line as founder of Berlin Lean Prototyping and argued the community case at a [DevRel meetup in 2023](/talks/enhance-dx-by-community-voxgig-2023): developer experience improves fastest when a community is answering questions you have not thought to ask. That is DevRel's unique asset. No PMM has it, however technical. ## Where do the roles collide in practice? Three recurring collisions, and who should lead each: - **Launches.** Technical PMM leads: positioning, tiering, channels, metrics. DevRel contributes early developer feedback and gives the community advance warning, honestly. PMM (classic) leads if the buyer is not the developer. - **Technical content.** Depends on the job of the piece. Conversion content (comparison pages, launch posts, case studies): technical PMM. Capability content (tutorials, deep dives, office hours): DevRel or developer education. The same topic can be either; the accountability decides. - **Events.** DevRel shows up continuously, PMM shows up around moments. A DevRel presence at a hackathon is relationship maintenance; a technical PMM keynote at a conference is a launch channel. Both are on stage, doing different jobs. ## Which role should a company hire first? It depends on what is scarce. If developers already love the product but the company cannot explain it to buyers, hire a PMM. If marketing keeps producing content developers ignore, and nobody in the building can run the quickstart, hire a technical PMM. If the product depends on ecosystem adoption, integrations, or community contribution, and you have no ear to the ground, hire DevRel, and protect it from lead targets from day one. A rough sequencing for a developer tools startup: founder-led DevRel first (founders are the first advocates), technical PMM at the first real launch, classic PMM when a sales team exists, dedicated DevRel when community volume outgrows the founders. ## Which role fits you? By origin: engineers who want their work to face outward usually fit technical PMM (that was my path) or DevRel, and the fork is temperament. If repeating and tuning the same story a hundred times energizes you, that is PMM work. If open-ended conversations, teaching, and being present in community channels energize you, that is DevRel. Marketers who love craft and commercial accountability fit PMM, and can go technical if they genuinely want to build, not just to learn vocabulary. The wrong reason to pick technical PMM is thinking it is "PMM plus knowing what an API is." The wrong reason to pick DevRel is being an engineer who dislikes marketing; DevRel is not a hiding place from commercial reality, it just meets it through a longer loop. ## FAQ ### Can DevRel report to marketing? Yes, if marketing leadership accepts DevRel's metrics (community health, feedback quality, retention signals) instead of imposing funnel metrics. The reporting line matters less than the measurement. Many healthy DevRel teams sit in marketing; many broken ones do too. ### Is DevRel a path into product marketing? It can be. DevRel builds audience fluency and content craft, which transfer directly. What it does not build is positioning discipline and commercial accountability, so expect to learn those deliberately, the same way engineers moving to PMM must learn storytelling. ### Do technical PMMs need to code? You need to be able to follow the code and run the product yourself: quickstarts, API calls, a demo app. You do not need to pass an engineering interview. If you cannot tell whether the docs are wrong, you are marketing from the outside. ### Is developer marketing the same as any of these roles? Developer marketing is the audience discipline, not a role: earning attention and trust with developers. Technical PMMs, DevRel, content marketers, and founders all practice it. A "developer marketing manager" title usually means a demand-gen or content role aimed at developers, measured on marketing metrics. --- *[Anil Kumar Krishnashetty](/) is a Senior Technical Product Marketing Manager at Bright Data in Berlin. Previously frontend engineer at SAP and One.com, technical product manager at Contentful and commercetools, and PMM at Lokalise and Parallels. He speaks about developer experience and technical product marketing, [25+ talks and counting](/public-speaking).* --- Source: https://www.anilkumark.de/writing/what-does-a-technical-product-marketing-manager-do/ # What does a technical product marketing manager do? A technical product marketing manager (technical PMM) owns positioning, launches, and go-to-market for products whose buyers and users are developers or technical teams. The "technical" part is not a vibe: you build the demo yourself, you read the API docs before writing the messaging, and you translate between the people who build the product and the people who adopt it. I've been asked this question by engineers who want out of pure building, by PMMs who want to go technical, and by hiring managers writing the job description. I'll answer it from an unusual position: I've sat in every seat around this role. I was a frontend engineer for a decade (SAP, One.com, Canto), then a technical product manager (Contentful, commercetools), and I'm now a Senior Technical Product Marketing Manager at Bright Data, after PMM roles at Lokalise and Parallels. This is what the job actually is. ## Why Google gets this query wrong Search "what does a technical product marketing manager do" and most results explain a technical product manager, a different job. A technical PM decides what gets built and how. A technical PMM decides how the world hears about it, whether the story survives contact with a skeptical developer audience, and whether anyone adopts it. Almost nobody has written the technical PMM answer from the inside, which is why this page exists. ## What does a technical PMM actually do all day? Here is my real workload split at Bright Data, averaged over a quarter: - **Launches and go-to-market: 50 to 70%.** Leading GTM for developer-facing products end to end: positioning, messaging, launch tiers, channel plans, and coordinating product, sales, and marketing around one story. - **Documentation: about 10%.** I lead documentation. That surprises people, docs sitting with marketing, but for developer products the docs ARE the marketing. They're the first thing a developer (or, in 2026, their AI agent) reads, and the place where trust is won or lost. - **Content: 5 to 10%.** Technical blog posts, conference talks, demo videos. - **Sales enablement: about 5%.** Battlecards, objection handling, demos sales can actually run. - **Events: about 5%.** Speaking and showing up where developers are. My most recent talk was at [devWorld 2026 in Amsterdam](/talks/bots-and-humans-devworld-2026), on AI agents and the closed web. The percentages move around launches, but the center of gravity is constant: I'm accountable for pipeline generation from the products I own, and for making every outward-facing team (sales, demand gen, content, partners) better at telling a story developers believe. ## Technical PMM vs PMM: what's actually different? A great PMM and a great technical PMM run the same core playbook: segment the audience, find the problem, position against real alternatives, arm the field. The difference is the audience's allergy to faked fluency. Developers detect it instantly when marketing doesn't understand the product. So a technical PMM does things a classic PMM can delegate: read the SDK source before writing the one-pager, run the quickstart to see where it breaks, sit in pair programming sessions with community developers instead of only running interview panels. At Contentful, our user interviews for the Forma 36 design system produced polite nice-to-haves. Watching developers actually work revealed the truth: one developer never opened our expensive documentation because the TypeScript types were his documentation. No interview surfaced that. Don't listen to their words, observe their actions, and you can only observe if you can follow along. The other difference is what counts as a deliverable. My portfolio isn't decks. It's a [demo app that replaced hello-world sales demos](/work/pmm/lokalise-demo-app-ai-emporium) and shortened sales cycles, a [developer hub](/work/pmm/lokalise-developer-hub) we usability-tested on internal engineers in 15-minute sessions, and a [workflow guide](/work/pmm/software-localization-workflow) that fixed a mental-model problem (developers treating localization branching like git branching) rather than a feature problem. ## Technical PMM vs technical PM: release is not launch This is the confusion the search results feed, so let me kill it with the analogy I used when I made the switch. A restaurant hires a great chef who creates a new dish. The kitchen can cook it perfectly. That's a **release**: the product team shipped, engineering-complete, quality-assured. But the dish isn't on the menu, the waiters can't describe it, no one outside knows it exists, and nobody has decided what it costs or who it's for. Getting it on the menu, training the staff, telling the neighborhood, filling the tables: that's the **launch**, and it's the PMM's job. As a technical PM at Contentful and commercetools, I owned the release side: what we build, for whom, in what order. As a technical PMM, I own the launch side: why it matters, who hears about it, and what happens to pipeline. Adoption is the shared metric, and the roles fail separately: a great product nobody understands (PM succeeded, PMM missing) or a great story about a product that disappoints (reverse). ## How do you become a technical product marketing manager? My path My motivation was simple: I wanted my work to face outward. As an engineer and PM I built great products, but the leverage I kept reaching for was elsewhere: enabling sales and marketing to tell better stories to developers, ones that actually resonate. I was already doing developer marketing without the title, running the Berlin prototyping community, answering questions in product Slacks, speaking at meetups. The switch made it official, and it connected my work directly to revenue growth. What transferred from a decade of building: technical credibility (I can read the code behind the claims), community instinct (I knew where developers actually hang out and what they ignore), and product sense from the PM years. What did NOT transfer, and what I had to learn deliberately: storytelling as a craft, outside-in thinking (engineers think from the architecture out; marketing thinks from the buyer in), positioning and messaging as disciplines rather than instincts, acquisition channels, launch and GTM strategy, and sales enablement. If you're an engineer considering this move, be honest that this is the half of the job you don't have yet. It took me real study and real reps. ## What do technical PMM interviews actually test? Two real examples from my own transitions. **A developer platform company (Senior PMM role)** gave a scenario: a new un-opinionated API plus three client libraries is coming. Part one: what questions do you ask the product team before launch? Part two: assume answers and write the GTM plan, channels, team responsibilities, success metrics, messaging, timeline. Part three: draft the launch blog post structure. Notice what's being tested: not writing polish, but whether you know which questions matter before anyone writes a word. **A data infrastructure company (Senior Technical PMM role)** asked for a full GTM for a developer-facing API product: market opportunity, target segments, positioning against open source and in-house builds, messaging, keyword strategy, a three-phase launch plan, and metrics I'd sign up for. I committed to numbers like 1,000 active developers in the launch quarter and time-to-first-API-call under 5 minutes. That last metric is the tell: technical PMM interviews reward people who think in developer experience terms, not impression counts. If you're preparing: practice the assignment format. Pick a real dev tool, write the pre-launch questions, the plan, and the metrics you'd be accountable for. ## Who should NOT become a technical PMM The honest section. This role is not "a PMM who knows what an API is." Developers are builders, constantly, and if you want to market to builders you need a building attitude yourself: the pull to try the tool, break it, and understand the ecosystem it lives in. If you stopped building years ago and don't miss it, you will be marketing from the outside, and developers will notice. Equally, if you're an engineer who resents repetition, know that GTM is repetitive by design: the story gets told a hundred times, tuned each time. If neither the building nor the retelling energizes you, stay a PM or an engineer, both are great jobs. ## How is a technical PMM measured? In my current role: pipeline generated by the products I lead, launch outcomes against committed targets, and the effectiveness of the teams I enable (are sales conversations better, is demand gen using messaging that converts). Under those sit the developer-experience metrics I bring to every plan: activation (time to first successful call), docs engagement, and adoption of what we launch. My first 90 days at Bright Data were spent almost entirely on the developer surface: Postman collections, SDKs, documentation improvements, and optimizing the website for a developer audience, because everything downstream converts better when the first ten minutes work. ## FAQ ### Is a technical PMM the same as developer marketing? They overlap but aren't identical. Developer marketing is the audience discipline (reaching and earning trust with developers, any role can practice it). Technical PMM is a specific job that owns positioning, launches, and GTM for technical products, and typically uses developer marketing as one of its tools. ### Do you need to be able to code? You need to have built, and to still enjoy building. You don't need to pass an engineering interview, but you should be able to run the quickstart, read example code, judge whether the docs lie, and build a simple demo. And in 2026 that bar is more reachable than ever: with coding agents, building a quick demo or consuming an API is something any curious PMM can do in an afternoon. The tools removed the excuse. What they didn't remove is the judgment of what to build and whether it actually demonstrates the product's value, and that still comes from hands-on comfort. My frontend decade is overkill; genuine builder curiosity is the actual bar. ### How do I transition from engineering or PM into technical PMM? Start doing the outward-facing work before you have the title: write about your product publicly, answer community questions, volunteer for the launch. Then close the deliberate gaps: positioning, messaging, GTM strategy, enablement. The technical half you already have is the rare half; the marketing half is learnable. ### What tools does a technical PMM use in 2026? The classic stack (docs platforms, analytics, CRM) plus, increasingly, AI agents for the repetitive layer: competitive monitoring, draft generation, launch checklists. That shift is big enough that I write about it separately. --- *[Anil Kumar Krishnashetty](/) is a Senior Technical Product Marketing Manager at Bright Data in Berlin. Previously frontend engineer at SAP and One.com, technical product manager at Contentful and commercetools, and PMM at Lokalise and Parallels. He speaks about developer experience and technical product marketing, [25+ talks and counting](/public-speaking).*