There's so much more to a company than its LinkedIn profile, employee count or funding announcements.
Its engineering ecosystem can tell you what it's building, what technologies it's adopting, what it's moving away from and where potential opportunities might exist.
A few places worth exploring -
- GitHub
What are they building? Which repositories are active? What frameworks and technologies are they using? Are they contributing to open source? What direction is their engineering team moving towards?
- Package registries
Look at npm, PyPI and other package ecosystems. What are they publishing, installing, maintaining or depending on? These can reveal a lot about their actual technology choices.
- Docker Hub and container registries
What images are they pushing? What infrastructure are they running? Are they adopting new tools or changing their existing stack?
- Engineering job openings
What roles are they hiring for? Are they looking for Kubernetes engineers, AI infrastructure specialists, DevOps engineers or people with experience in a particular technology?
Hiring often gives you a glimpse of what's coming next.
- Developer communities
Look at Dev.to, Reddit, Stack Overflow, technical blogs and engineering discussions. What problems are they talking about? What tools are they evaluating? What are their developers experimenting with?
- Technology adoption and migrations
Are they adopting a new technology? Moving away from an existing infrastructure? Replacing a solution? Building something internally?
These movements can tell you much more than a company description ever will.
The interesting part is that none of these signals, on their own, tells the complete story.
But when you start connecting them, you get a much better picture of what is happening inside a company.
And that's probably a much more interesting way to research an account than just looking at its LinkedIn profile.
Something worth exploring if you're in technical GTM.
