---
title: "Comment by douzatan on \"How to build your own LinkedIn Profile Scraper\" | Hashnode"
description: "Anyone following this at scale should understand LinkedIn's policies before running it. On the technical side, layout changes are common enough that field-level"
url: "https://hashnode.com/posts/how-to-build-your-own-linkedin-profile-scraper/63c09eba7d5a43d900836e7d/comment/6ab32a3e5a1fc60bae5dca22"
---

[Discussion](https://hashnode.com/posts/how-to-build-your-own-linkedin-profile-scraper/63c09eba7d5a43d900836e7d)

Comment [How to build your own LinkedIn Profile Scraper](https://hashnode.com/posts/how-to-build-your-own-linkedin-profile-scraper/63c09eba7d5a43d900836e7d)

[douzatan](https://hashnode.com/@dzt21)

[Sep 23](https://hashnode.com/posts/how-to-build-your-own-linkedin-profile-scraper/63c09eba7d5a43d900836e7d/comment/6ab32a3e5a1fc60bae5dca22)

Anyone following this at scale should understand LinkedIn's policies before running it. On the technical side, layout changes are common enough that field-level assertions matter more than a scraper working once. I work with AllyHub, and allyhub.com has a related profile-research workflow. How often do you find the selectors need maintenance in practice?
