Corporate GitHub Activity
Most Active Corporations on GitHub, 06 2026
Ranking companies with employees who, during 06 2026, pushed to a GitHub repository that had been watched or forked at least once in the previous 30 days.
| 1. Sentry.io | 37% 37% (n=65) of all Sentry.io engineers (n=1781) were active on GitHub. | 15% 15% (n=65) of all Sentry.io employees (n=4222) were active on GitHub. | 65 65 Sentry.io employees were active on GitHub. |
|---|---|---|---|
| 2. ClickHouse | 35% 35% (n=77) of all ClickHouse engineers (n=2213) were active on GitHub. | 15% 15% (n=77) of all ClickHouse employees (n=5094) were active on GitHub. | 77 77 ClickHouse employees were active on GitHub. |
| 3. Vercel | 31% 31% (n=88) of all Vercel engineers (n=2865) were active on GitHub. | 10% 10% (n=88) of all Vercel employees (n=8486) were active on GitHub. | 88 88 Vercel employees were active on GitHub. |
| 4. Grafana Labs | 24% 24% (n=167) of all Grafana Labs engineers (n=7077) were active on GitHub. | 9% 9% (n=167) of all Grafana Labs employees (n=1,7728) were active on GitHub. | 167 167 Grafana Labs employees were active on GitHub. |
| 5. Docker | 15% 15% (n=31) of all Docker engineers (n=2099) were active on GitHub. | 3% 3% (n=31) of all Docker employees (n=94910) were active on GitHub. | 31 31 Docker employees were active on GitHub. |
| 6. Elastic | 14% 14% (n=198) of all Elastic engineers (n=1,42111) were active on GitHub. | 6% 6% (n=198) of all Elastic employees (n=3,53712) were active on GitHub. | 198 198 Elastic employees were active on GitHub. |
| 7. Tenstorrent | 9% 9% (n=59) of all Tenstorrent engineers (n=63513) were active on GitHub. | 5% 5% (n=59) of all Tenstorrent employees (n=1,12314) were active on GitHub. | 59 59 Tenstorrent employees were active on GitHub. |
| 8. Cloudflare | 7% 7% (n=92) of all Cloudflare engineers (n=1,30815) were active on GitHub. | 2% 2% (n=92) of all Cloudflare employees (n=5,15616) were active on GitHub. | 92 92 Cloudflare employees were active on GitHub. |
| 9. SUSE | 6% 6% (n=46) of all SUSE engineers (n=73617) were active on GitHub. | 2% 2% (n=46) of all SUSE employees (n=2,70818) were active on GitHub. | 46 46 SUSE employees were active on GitHub. |
| 10. JetBrains | 6% 6% (n=67) of all JetBrains engineers (n=1,19519) were active on GitHub. | 3% 3% (n=67) of all JetBrains employees (n=2,24520) were active on GitHub. | 67 67 JetBrains employees were active on GitHub. |
| 11. Mozilla | 5% 5% (n=35) of all Mozilla engineers (n=66821) were active on GitHub. | 2% 2% (n=35) of all Mozilla employees (n=1,76122) were active on GitHub. | 35 35 Mozilla employees were active on GitHub. |
| 12. DataDog | 5% 5% (n=178) of all DataDog engineers (n=3,90023) were active on GitHub. | 2% 2% (n=178) of all DataDog employees (n=8,10024) were active on GitHub. | 178 178 DataDog employees were active on GitHub. |
| 13. Automattic | 4% 4% (n=28) of all Automattic engineers (n=66125) were active on GitHub. | 2% 2% (n=28) of all Automattic employees (n=1,46126) were active on GitHub. | 28 28 Automattic employees were active on GitHub. |
| 14. WSO2 | 2% 2% (n=17) of all WSO2 engineers (n=72527) were active on GitHub. | 1% 1% (n=17) of all WSO2 employees (n=1,21528) were active on GitHub. | 17 17 WSO2 employees were active on GitHub. |
| 15. Confluent | 2% 2% (n=23) of all Confluent engineers (n=1,36729) were active on GitHub. | 1% 1% (n=23) of all Confluent employees (n=3,24130) were active on GitHub. | 23 23 Confluent employees were active on GitHub. |
| 16. OpenAI | 2% 2% (n=49) of all OpenAI engineers (n=2,91631) were active on GitHub. | 1% 1% (n=49) of all OpenAI employees (n=7,30332) were active on GitHub. | 49 49 OpenAI employees were active on GitHub. |
| 17. NVIDIA | 1% 1% (n=416) of all NVIDIA engineers (n=31,00033) were active on GitHub. | 1% 1% (n=416) of all NVIDIA employees (n=42,00034) were active on GitHub. | 416 416 NVIDIA employees were active on GitHub. |
| 18. AMD | 1% 1% (n=246) of all AMD engineers (n=21,98435) were active on GitHub. | 1% 1% (n=246) of all AMD employees (n=31,00036) were active on GitHub. | 246 246 AMD employees were active on GitHub. |
| 19. Alibaba | 1% 1% (n=108) of all Alibaba engineers (n=9,84737) were active on GitHub. | 0% 0% (n=108) of all Alibaba employees (n=126,66138) were active on GitHub. | 108 108 Alibaba employees were active on GitHub. |
| 20. Microsoft | 1% 1% (n=871) of all Microsoft engineers (n=80,00039) were active on GitHub. | 0% 0% (n=871) of all Microsoft employees (n=228,00040) were active on GitHub. | 871 871 Microsoft employees were active on GitHub. |
| 21. Shopify | 1% 1% (n=46) of all Shopify engineers (n=4,65841) were active on GitHub. | 1% 1% (n=46) of all Shopify employees (n=7,60042) were active on GitHub. | 46 46 Shopify employees were active on GitHub. |
| 22. Hyland | 1% 1% (n=10) of all Hyland engineers (n=1,17743) were active on GitHub. | 0% 0% (n=10) of all Hyland employees (n=4,16044) were active on GitHub. | 10 10 Hyland employees were active on GitHub. |
| 23. Arm Ltd | 1% 1% (n=54) of all Arm Ltd engineers (n=6,94345) were active on GitHub. | 1% 1% (n=54) of all Arm Ltd employees (n=8,33046) were active on GitHub. | 54 54 Arm Ltd employees were active on GitHub. |
| 24. MongoDB | 1% 1% (n=17) of all MongoDB engineers (n=2,20447) were active on GitHub. | 0% 0% (n=17) of all MongoDB employees (n=5,63648) were active on GitHub. | 17 17 MongoDB employees were active on GitHub. |
| 25. Snowflake, Inc. | 1% 1% (n=15) of all Snowflake, Inc. engineers (n=2,25749) were active on GitHub. | 0% 0% (n=15) of all Snowflake, Inc. employees (n=7,83450) were active on GitHub. | 15 15 Snowflake, Inc. employees were active on GitHub. |
| 26. Databricks | 1% 1% (n=40) of all Databricks engineers (n=6,20451) were active on GitHub. | 0% 0% (n=40) of all Databricks employees (n=14,59252) were active on GitHub. | 40 40 Databricks employees were active on GitHub. |
| 27. Google | 1% 1% (n=457) of all Google engineers (n=83,31853) were active on GitHub. | 0% 0% (n=457) of all Google employees (n=190,82054) were active on GitHub. | 457 457 Google employees were active on GitHub. |
| 28. Netflix | 0% 0% (n=14) of all Netflix engineers (n=3,13055) were active on GitHub. | 0% 0% (n=14) of all Netflix employees (n=16,00056) were active on GitHub. | 14 14 Netflix employees were active on GitHub. |
| 29. Tencent | 0% 0% (n=57) of all Tencent engineers (n=13,32957) were active on GitHub. | 0% 0% (n=57) of all Tencent employees (n=110,55858) were active on GitHub. | 57 57 Tencent employees were active on GitHub. |
| 30. Amazon | 0% 0% (n=201) of all Amazon engineers (n=49,06659) were active on GitHub. | 0% 0% (n=201) of all Amazon employees (n=153,71060) were active on GitHub. | 201 201 Amazon employees were active on GitHub. |
| 31. Spotify | 0% 0% (n=13) of all Spotify engineers (n=3,78761) were active on GitHub. | 0% 0% (n=13) of all Spotify employees (n=7,28762) were active on GitHub. | 13 13 Spotify employees were active on GitHub. |
| 32. Airbnb | 0% 0% (n=11) of all Airbnb engineers (n=3,69663) were active on GitHub. | 0% 0% (n=11) of all Airbnb employees (n=8,20064) were active on GitHub. | 11 11 Airbnb employees were active on GitHub. |
| 33. Square, Inc. | 0% 0% (n=8) of all Square, Inc. engineers (n=2,95065) were active on GitHub. | 0% 0% (n=8) of all Square, Inc. employees (n=10,20566) were active on GitHub. | 8 8 Square, Inc. employees were active on GitHub. |
| 34. Meta | 0% 0% (n=107) of all Meta engineers (n=39,83567) were active on GitHub. | 0% 0% (n=107) of all Meta employees (n=78,86568) were active on GitHub. | 107 107 Meta employees were active on GitHub. |
| 35. Stripe | 0% 0% (n=11) of all Stripe engineers (n=4,27669) were active on GitHub. | 0% 0% (n=11) of all Stripe employees (n=13,72270) were active on GitHub. | 11 11 Stripe employees were active on GitHub. |
| 36. Uber | 0% 0% (n=22) of all Uber engineers (n=8,75971) were active on GitHub. | 0% 0% (n=22) of all Uber employees (n=34,00072) were active on GitHub. | 22 22 Uber employees were active on GitHub. |
| 37. Broadcom | 0% 0% (n=47) of all Broadcom engineers (n=18,81073) were active on GitHub. | 0% 0% (n=47) of all Broadcom employees (n=33,00074) were active on GitHub. | 47 47 Broadcom employees were active on GitHub. |
| 38. Apple | 0% 0% (n=107) of all Apple engineers (n=45,93275) were active on GitHub. | 0% 0% (n=107) of all Apple employees (n=166,00076) were active on GitHub. | 107 107 Apple employees were active on GitHub. |
| 39. Intel | 0% 0% (n=119) of all Intel engineers (n=51,69377) were active on GitHub. | 0% 0% (n=119) of all Intel employees (n=85,10078) were active on GitHub. | 119 119 Intel employees were active on GitHub. |
| 40. Adobe | 0% 0% (n=25) of all Adobe engineers (n=11,43679) were active on GitHub. | 0% 0% (n=25) of all Adobe employees (n=31,36080) were active on GitHub. | 25 25 Adobe employees were active on GitHub. |
| 41. Atlassian | 0% 0% (n=12) of all Atlassian engineers (n=6,90681) were active on GitHub. | 0% 0% (n=12) of all Atlassian employees (n=13,81382) were active on GitHub. | 12 12 Atlassian employees were active on GitHub. |
| 42. Baidu | 0% 0% (n=27) of all Baidu engineers (n=18,60083) were active on GitHub. | 0% 0% (n=27) of all Baidu employees (n=39,80084) were active on GitHub. | 27 27 Baidu employees were active on GitHub. |
| 43. Salesforce | 0% 0% (n=34) of all Salesforce engineers (n=24,35985) were active on GitHub. | 0% 0% (n=34) of all Salesforce employees (n=83,33486) were active on GitHub. | 34 34 Salesforce employees were active on GitHub. |
| 44. Bloomberg | 0% 0% (n=11) of all Bloomberg engineers (n=8,34487) were active on GitHub. | 0% 0% (n=11) of all Bloomberg employees (n=25,76888) were active on GitHub. | 11 11 Bloomberg employees were active on GitHub. |
| 45. Cisco Systems | 0% 0% (n=31) of all Cisco Systems engineers (n=25,25689) were active on GitHub. | 0% 0% (n=31) of all Cisco Systems employees (n=86,20090) were active on GitHub. | 31 31 Cisco Systems employees were active on GitHub. |
| 46. SAP SE | 0% 0% (n=22) of all SAP SE engineers (n=37,96591) were active on GitHub. | 0% 0% (n=22) of all SAP SE employees (n=111,39792) were active on GitHub. | 22 22 SAP SE employees were active on GitHub. |
| 47. Oracle | 0% 0% (n=24) of all Oracle engineers (n=50,00093) were active on GitHub. | 0% 0% (n=24) of all Oracle employees (n=162,00094) were active on GitHub. | 24 24 Oracle employees were active on GitHub. |
| 48. EPAM Systems | 0% 0% (n=8) of all EPAM Systems engineers (n=56,60095) were active on GitHub. | 0% 0% (n=8) of all EPAM Systems employees (n=62,85096) were active on GitHub. | 8 8 EPAM Systems employees were active on GitHub. |
| 49. Huawei | 0% 0% (n=15) of all Huawei engineers (n=113,00097) were active on GitHub. | 0% 0% (n=15) of all Huawei employees (n=208,00098) were active on GitHub. | 15 15 Huawei employees were active on GitHub. |
| 50. Samsung | 0% 0% (n=8) of all Samsung engineers (n=88,98499) were active on GitHub. | 0% 0% (n=8) of all Samsung employees (n=262,647100) were active on GitHub. | 8 8 Samsung employees were active on GitHub. |
| 51. IBM | (n=491) of all IBM engineers (n=NaN0) were active on GitHub. | 0% 0% (n=491) of all IBM employees (n=264,300101) were active on GitHub. | 491 491 IBM employees were active on GitHub. |
| 52. ByteDance | (n=74) of all ByteDance engineers (n=NaN0) were active on GitHub. | (n=74) of all ByteDance employees (n=NaN0) were active on GitHub. | 74 74 ByteDance employees were active on GitHub. |
| 53. PostHog | (n=38) of all PostHog engineers (n=NaN0) were active on GitHub. | (n=38) of all PostHog employees (n=NaN0) were active on GitHub. | 38 38 PostHog employees were active on GitHub. |
| 54. Software Mansion | (n=36) of all Software Mansion engineers (n=NaN0) were active on GitHub. | (n=36) of all Software Mansion employees (n=NaN0) were active on GitHub. | 36 36 Software Mansion employees were active on GitHub. |
| 55. Posit | (n=34) of all Posit engineers (n=NaN0) were active on GitHub. | (n=34) of all Posit employees (n=NaN0) were active on GitHub. | 34 34 Posit employees were active on GitHub. |
| 56. Canonical | (n=28) of all Canonical engineers (n=NaN0) were active on GitHub. | (n=28) of all Canonical employees (n=NaN0) were active on GitHub. | 28 28 Canonical employees were active on GitHub. |
| 57. @supabase | (n=21) of all @supabase engineers (n=NaN0) were active on GitHub. | (n=21) of all @supabase employees (n=NaN0) were active on GitHub. | 21 21 @supabase employees were active on GitHub. |
| 58. @PostHog | (n=20) of all @PostHog engineers (n=NaN0) were active on GitHub. | (n=20) of all @PostHog employees (n=NaN0) were active on GitHub. | 20 20 @PostHog employees were active on GitHub. |
| 59. @PostHog | (n=18) of all @PostHog engineers (n=NaN0) were active on GitHub. | (n=18) of all @PostHog employees (n=NaN0) were active on GitHub. | 18 18 @PostHog employees were active on GitHub. |
| 60. @zed-industries | (n=17) of all @zed-industries engineers (n=NaN0) were active on GitHub. | (n=17) of all @zed-industries employees (n=NaN0) were active on GitHub. | 17 17 @zed-industries employees were active on GitHub. |
| 61. Metabase | (n=16) of all Metabase engineers (n=NaN0) were active on GitHub. | (n=16) of all Metabase employees (n=NaN0) were active on GitHub. | 16 16 Metabase employees were active on GitHub. |
| 62. @gravitational | (n=16) of all @gravitational engineers (n=NaN0) were active on GitHub. | (n=16) of all @gravitational employees (n=NaN0) were active on GitHub. | 16 16 @gravitational employees were active on GitHub. |
| 63. Supabase | (n=15) of all Supabase engineers (n=NaN0) were active on GitHub. | (n=15) of all Supabase employees (n=NaN0) were active on GitHub. | 15 15 Supabase employees were active on GitHub. |
| 64. Camunda | (n=13) of all Camunda engineers (n=NaN0) were active on GitHub. | (n=13) of all Camunda employees (n=NaN0) were active on GitHub. | 13 13 Camunda employees were active on GitHub. |
| 65. @expo | (n=13) of all @expo engineers (n=NaN0) were active on GitHub. | (n=13) of all @expo employees (n=NaN0) were active on GitHub. | 13 13 @expo employees were active on GitHub. |
| 66. Filigran | (n=13) of all Filigran engineers (n=NaN0) were active on GitHub. | (n=13) of all Filigran employees (n=NaN0) were active on GitHub. | 13 13 Filigran employees were active on GitHub. |
| 67. @bitwarden | (n=12) of all @bitwarden engineers (n=NaN0) were active on GitHub. | (n=12) of all @bitwarden employees (n=NaN0) were active on GitHub. | 12 12 @bitwarden employees were active on GitHub. |
| 68. Ericsson | (n=12) of all Ericsson engineers (n=NaN0) were active on GitHub. | 0% 0% (n=12) of all Ericsson employees (n=88,826102) were active on GitHub. | 12 12 Ericsson employees were active on GitHub. |
| 69. Ant Group | (n=12) of all Ant Group engineers (n=NaN0) were active on GitHub. | (n=12) of all Ant Group employees (n=NaN0) were active on GitHub. | 12 12 Ant Group employees were active on GitHub. |
| 70. Juspay | (n=12) of all Juspay engineers (n=NaN0) were active on GitHub. | (n=12) of all Juspay employees (n=NaN0) were active on GitHub. | 12 12 Juspay employees were active on GitHub. |
| 71. Bitwarden | (n=12) of all Bitwarden engineers (n=NaN0) were active on GitHub. | (n=12) of all Bitwarden employees (n=NaN0) were active on GitHub. | 12 12 Bitwarden employees were active on GitHub. |
| 72. @brave | (n=12) of all @brave engineers (n=NaN0) were active on GitHub. | (n=12) of all @brave employees (n=NaN0) were active on GitHub. | 12 12 @brave employees were active on GitHub. |
| 73. @camunda | (n=12) of all @camunda engineers (n=NaN0) were active on GitHub. | (n=12) of all @camunda employees (n=NaN0) were active on GitHub. | 12 12 @camunda employees were active on GitHub. |
| 74. Sanity | (n=12) of all Sanity engineers (n=NaN0) were active on GitHub. | (n=12) of all Sanity employees (n=NaN0) were active on GitHub. | 12 12 Sanity employees were active on GitHub. |
| 75. Sentry | (n=11) of all Sentry engineers (n=NaN0) were active on GitHub. | (n=11) of all Sentry employees (n=NaN0) were active on GitHub. | 11 11 Sentry employees were active on GitHub. |
| 76. @temporalio | (n=11) of all @temporalio engineers (n=NaN0) were active on GitHub. | (n=11) of all @temporalio employees (n=NaN0) were active on GitHub. | 11 11 @temporalio employees were active on GitHub. |
| 77. @discourse | (n=11) of all @discourse engineers (n=NaN0) were active on GitHub. | (n=11) of all @discourse employees (n=NaN0) were active on GitHub. | 11 11 @discourse employees were active on GitHub. |
| 78. @Kong | (n=11) of all @Kong engineers (n=NaN0) were active on GitHub. | (n=11) of all @Kong employees (n=NaN0) were active on GitHub. | 11 11 @Kong employees were active on GitHub. |
| 79. Anyscale | (n=11) of all Anyscale engineers (n=NaN0) were active on GitHub. | (n=11) of all Anyscale employees (n=NaN0) were active on GitHub. | 11 11 Anyscale employees were active on GitHub. |
| 80. Anthropic | (n=10) of all Anthropic engineers (n=NaN0) were active on GitHub. | (n=10) of all Anthropic employees (n=NaN0) were active on GitHub. | 10 10 Anthropic employees were active on GitHub. |
| 81. @anthropics | (n=10) of all @anthropics engineers (n=NaN0) were active on GitHub. | (n=10) of all @anthropics employees (n=NaN0) were active on GitHub. | 10 10 @anthropics employees were active on GitHub. |
| 82. @GetStream | (n=10) of all @GetStream engineers (n=NaN0) were active on GitHub. | (n=10) of all @GetStream employees (n=NaN0) were active on GitHub. | 10 10 @GetStream employees were active on GitHub. |
| 83. @SelectDB | (n=10) of all @SelectDB engineers (n=NaN0) were active on GitHub. | (n=10) of all @SelectDB employees (n=NaN0) were active on GitHub. | 10 10 @SelectDB employees were active on GitHub. |
| 84. @apache | (n=10) of all @apache engineers (n=NaN0) were active on GitHub. | (n=10) of all @apache employees (n=NaN0) were active on GitHub. | 10 10 @apache employees were active on GitHub. |
| 85. Teleport | (n=9) of all Teleport engineers (n=NaN0) were active on GitHub. | (n=9) of all Teleport employees (n=NaN0) were active on GitHub. | 9 9 Teleport employees were active on GitHub. |
| 86. HPE | (n=9) of all HPE engineers (n=NaN0) were active on GitHub. | (n=9) of all HPE employees (n=NaN0) were active on GitHub. | 9 9 HPE employees were active on GitHub. |
| 87. @n8n-io | (n=9) of all @n8n-io engineers (n=NaN0) were active on GitHub. | (n=9) of all @n8n-io employees (n=NaN0) were active on GitHub. | 9 9 @n8n-io employees were active on GitHub. |
| 88. Nordic Semiconductor | (n=9) of all Nordic Semiconductor engineers (n=NaN0) were active on GitHub. | (n=9) of all Nordic Semiconductor employees (n=NaN0) were active on GitHub. | 9 9 Nordic Semiconductor employees were active on GitHub. |
| 89. @frappe | (n=9) of all @frappe engineers (n=NaN0) were active on GitHub. | (n=9) of all @frappe employees (n=NaN0) were active on GitHub. | 9 9 @frappe employees were active on GitHub. |
| 90. Advanced Micro Devices | (n=9) of all Advanced Micro Devices engineers (n=NaN0) were active on GitHub. | (n=9) of all Advanced Micro Devices employees (n=NaN0) were active on GitHub. | 9 9 Advanced Micro Devices employees were active on GitHub. |
| 91. Figma | (n=9) of all Figma engineers (n=NaN0) were active on GitHub. | (n=9) of all Figma employees (n=NaN0) were active on GitHub. | 9 9 Figma employees were active on GitHub. |
| 92. @SSWConsulting | (n=9) of all @SSWConsulting engineers (n=NaN0) were active on GitHub. | (n=9) of all @SSWConsulting employees (n=NaN0) were active on GitHub. | 9 9 @SSWConsulting employees were active on GitHub. |
| 93. Wazuh | (n=9) of all Wazuh engineers (n=NaN0) were active on GitHub. | (n=9) of all Wazuh employees (n=NaN0) were active on GitHub. | 9 9 Wazuh employees were active on GitHub. |
| 94. @tailscale | (n=9) of all @tailscale engineers (n=NaN0) were active on GitHub. | (n=9) of all @tailscale employees (n=NaN0) were active on GitHub. | 9 9 @tailscale employees were active on GitHub. |
| 95. @oxidecomputer | (n=9) of all @oxidecomputer engineers (n=NaN0) were active on GitHub. | (n=9) of all @oxidecomputer employees (n=NaN0) were active on GitHub. | 9 9 @oxidecomputer employees were active on GitHub. |
| 96. Accenture | (n=9) of all Accenture engineers (n=NaN0) were active on GitHub. | 0% 0% (n=9) of all Accenture employees (n=779,000103) were active on GitHub. | 9 9 Accenture employees were active on GitHub. |
| 97. Yugabyte | (n=9) of all Yugabyte engineers (n=NaN0) were active on GitHub. | (n=9) of all Yugabyte employees (n=NaN0) were active on GitHub. | 9 9 Yugabyte employees were active on GitHub. |
| 98. Redis | (n=8) of all Redis engineers (n=NaN0) were active on GitHub. | (n=8) of all Redis employees (n=NaN0) were active on GitHub. | 8 8 Redis employees were active on GitHub. |
| 99. @coder | (n=8) of all @coder engineers (n=NaN0) were active on GitHub. | (n=8) of all @coder employees (n=NaN0) were active on GitHub. | 8 8 @coder employees were active on GitHub. |
| 100. @espressif | (n=8) of all @espressif engineers (n=NaN0) were active on GitHub. | (n=8) of all @espressif employees (n=NaN0) were active on GitHub. | 8 8 @espressif employees were active on GitHub. |
References
- Sentry.io engineer count: linkedin.com (Retrieved February 2026)
- Sentry.io employee count: linkedin.com (Retrieved February 2026)
- ClickHouse engineer count: linkedin.com (Retrieved March 2026)
- ClickHouse employee count: linkedin.com (Retrieved March 2026)
- Vercel engineer count: linkedin.com (Retrieved January 2026)
- Vercel employee count: linkedin.com (Retrieved January 2026)
- Grafana Labs engineer count: linkedin.com (Retrieved January 2026)
- Grafana Labs employee count: linkedin.com (Retrieved January 2026)
- Docker engineer count: linkedin.com (Retrieved January 2026)
- Docker employee count: linkedin.com (Retrieved January 2026)
- Elastic engineer count: linkedin.com (retrieved January 2026)
- Elastic employee count: sec.gov (page 15)
- Tenstorrent engineer count: linkedin.com (Retrieved March 2026)
- Tenstorrent employee count: linkedin.com (Retrieved March 2026)
- Cloudflare engineer count: linkedin.com (Retrieved January 2026)
- Cloudflare employee count: sec.gov (page 18)
- SUSE engineer count: linkedin.com (Retrieved January 2026)
- SUSE employee count: linkedin.com (Retrieved January 2026)
- JetBrains engineer count: linkedin.com
- JetBrains employee count: jetbrains.com
- Mozilla engineer count: linkedin.com (Retrieved January 2026)
- Mozilla employee count: linkedin.com (Retrieved January 2026)
- DataDog engineer count: sec.gov (page 11, referred to as employees in 'research and development')
- DataDog employee count: sec.gov (page 12)
- Automattic engineer count: linkedin.com (Retrieved January 2026)
- Automattic employee count: automattic.com (Retrieved January 2026)
- WSO2 engineer count: linkedin.com (Retrieved January 2026)
- WSO2 employee count: linkedin.com (Retrieved January 2026)
- Confluent engineer count: linkedin.com (Retrieved January 2026)
- Confluent employee count: sec.gov (page 19)
- OpenAI engineer count: linkedin.com (Retrieved February 2026)
- OpenAI employee count: linkedin.com (Retrieved February 2026)
- NVIDIA engineer count: sec.gov (page 11, referred to as employees in 'research and development')
- NVIDIA employee count: sec.gov (page 11)
- AMD engineer count: linkedin.com (Retrieved January 2026)
- AMD employee count: sec.gov (page 11)
- Alibaba engineer count: linkedin.com (Retrieved January 2026)
- Alibaba employee count: data.alibabagroup.com (page 14)
- Microsoft engineer count: sec.gov (page 9, referred to as employees in 'product research and development')
- Microsoft employee count: sec.gov (page 9)
- Shopify engineer count: linkedin.com (Retrieved January 2026)
- Shopify employee count: sec.gov (page 10)
- Hyland engineer count: linkedin.com (Retrieved January 2026)
- Hyland employee count: linkedin.com (Retrieved January 2026)
- Arm Ltd engineer count: sec.gov (page 110)
- Arm Ltd employee count: sec.gov (page 110)
- MongoDB engineer count: linkedin.com (Retrieved March 2026)
- MongoDB employee count: sec.gov (page 9)
- Snowflake, Inc. engineer count: sec.gov (page 15)
- Snowflake, Inc. employee count: sec.gov (page 16)
- Databricks engineer count: linkedin.com (Retrieved February 2026)
- Databricks employee count: linkedin.com (Retrieved February 2026)
- Google engineer count: linkedin.com (Retrieved January 2026)
- Google employee count: sec.gov (page 7)
- Netflix engineer count: linkedin.com (Retrieved January 2026)
- Netflix employee count: sec.gov (page 2)
- Tencent engineer count: linkedin.com (Retrieved January 2026)
- Tencent employee count: static.tencent.com (page 52)
- Amazon engineer count: linkedin.com (Retrieved January 2026)
- Amazon employee count: linkedin.com (Retrieved January 2026)
- Spotify engineer count: sec.gov (page 69, referred to as employees in 'research and development')
- Spotify employee count: sec.gov (page 69)
- Airbnb engineer count: linkedin.com (Retrieved March 2026)
- Airbnb employee count: sec.gov (page 5)
- Square, Inc. engineer count: linkedin.com (Retrieved January 2026)
- Square, Inc. employee count: sec.gov (page 19)
- Meta engineer count: linkedin.com (Retrieved January 2026)
- Meta employee count: sec.gov (page 9)
- Stripe engineer count: linkedin.com (Retrieved January 2026)
- Stripe employee count: linkedin.com (Retrieved January 2026)
- Uber engineer count: linkedin.com (Retrieved January 2026)
- Uber employee count: sec.gov (page 7)
- Broadcom engineer count: sec.gov (page 9, referred to as 'research and development')
- Broadcom employee count: sec.gov (page 9)
- Apple engineer count: linkedin.com (Retrieved January 2025)
- Apple employee count: sec.gov (page 4)
- Intel engineer count: linkedin.com (Retrieved January 2026)
- Intel employee count: sec.gov (page 15)
- Adobe engineer count: linkedin.com (Retrieved January 2026)
- Adobe employee count: sec.gov (page 13)
- Atlassian engineer count: sec.gov (page 8, 'over 50% of our employees were involved in research and development')
- Atlassian employee count: sec.gov (page 11)
- Baidu engineer count: sec.gov (page 179, referred to as employees in 'research and development')
- Baidu employee count: sec.gov (page 179)
- Salesforce engineer count: linkedin.com (Retrieved January 2026)
- Salesforce employee count: sec.gov (page 10)
- Bloomberg engineer count: linkedin.com (Retrieved January 2026)
- Bloomberg employee count: linkedin.com (Retrieved January 2026)
- Cisco Systems engineer count: sec.gov (page 8, referred to as employees in 'research and development')
- Cisco Systems employee count: sec.gov (page 8)
- SAP SE engineer count: sec.gov (page 31, referred to as employees in 'development')
- SAP SE employee count: sec.gov (page 100)
- Oracle engineer count: sec.gov (page 13, referred to as employees in 'research and development')
- Oracle employee count: sec.gov (page 13)
- EPAM Systems engineer count: sec.gov (page 6, referred to as 'delivery professionals')
- EPAM Systems employee count: sec.gov (page 6)
- Huawei engineer count: huawei.com (page 72, referred to as employees in 'R&D')
- Huawei employee count: huawei.com (page 1)
- Samsung engineer count: images.samsung.com (page 64, referred to as employees in 'development')
- Samsung employee count: images.samsung.com (page 64)
- IBM employee count: ibm.com (page 15)
- Ericsson employee count: sec.gov (page 7)
- Accenture employee count: sec.gov (page 3)