Corporate GitHub Activity
Most Active Corporations on GitHub, 04 2026
Ranking companies with employees who, during 04 2026, pushed to a GitHub repository that had been watched or forked at least once in the previous 30 days.
| 1. Sentry.io | 42% 42% (n=75) of all Sentry.io engineers (n=1781) were active on GitHub. | 18% 18% (n=75) of all Sentry.io employees (n=4222) were active on GitHub. | 75 75 Sentry.io employees were active on GitHub. |
|---|---|---|---|
| 2. ClickHouse | 37% 37% (n=82) of all ClickHouse engineers (n=2213) were active on GitHub. | 16% 16% (n=82) of all ClickHouse employees (n=5094) were active on GitHub. | 82 82 ClickHouse employees were active on GitHub. |
| 3. Vercel | 32% 32% (n=92) of all Vercel engineers (n=2865) were active on GitHub. | 11% 11% (n=92) of all Vercel employees (n=8486) were active on GitHub. | 92 92 Vercel employees were active on GitHub. |
| 4. Grafana Labs | 29% 29% (n=208) of all Grafana Labs engineers (n=7077) were active on GitHub. | 12% 12% (n=208) of all Grafana Labs employees (n=1,7728) were active on GitHub. | 208 208 Grafana Labs employees were active on GitHub. |
| 5. Automattic | 22% 22% (n=148) of all Automattic engineers (n=6619) were active on GitHub. | 10% 10% (n=148) of all Automattic employees (n=1,46110) were active on GitHub. | 148 148 Automattic employees were active on GitHub. |
| 6. Elastic | 21% 21% (n=300) of all Elastic engineers (n=1,42111) were active on GitHub. | 8% 8% (n=300) of all Elastic employees (n=3,53712) were active on GitHub. | 300 300 Elastic employees were active on GitHub. |
| 7. Docker | 20% 20% (n=41) of all Docker engineers (n=20913) were active on GitHub. | 4% 4% (n=41) of all Docker employees (n=94914) were active on GitHub. | 41 41 Docker employees were active on GitHub. |
| 8. Kitware | 15% 15% (n=14) of all Kitware engineers (n=9615) were active on GitHub. | 9% 9% (n=14) of all Kitware employees (n=15116) were active on GitHub. | 14 14 Kitware employees were active on GitHub. |
| 9. SUSE | 13% 13% (n=97) of all SUSE engineers (n=73617) were active on GitHub. | 4% 4% (n=97) of all SUSE employees (n=2,70818) were active on GitHub. | 97 97 SUSE employees were active on GitHub. |
| 10. Mozilla | 12% 12% (n=83) of all Mozilla engineers (n=66819) were active on GitHub. | 5% 5% (n=83) of all Mozilla employees (n=1,76120) were active on GitHub. | 83 83 Mozilla employees were active on GitHub. |
| 11. Tenstorrent | 11% 11% (n=71) of all Tenstorrent engineers (n=63521) were active on GitHub. | 6% 6% (n=71) of all Tenstorrent employees (n=1,12322) were active on GitHub. | 71 71 Tenstorrent employees were active on GitHub. |
| 12. JetBrains | 10% 10% (n=116) of all JetBrains engineers (n=1,19523) were active on GitHub. | 5% 5% (n=116) of all JetBrains employees (n=2,24524) were active on GitHub. | 116 116 JetBrains employees were active on GitHub. |
| 13. Cloudflare | 8% 8% (n=107) of all Cloudflare engineers (n=1,30825) were active on GitHub. | 2% 2% (n=107) of all Cloudflare employees (n=5,15626) were active on GitHub. | 107 107 Cloudflare employees were active on GitHub. |
| 14. PingCAP | 7% 7% (n=15) of all PingCAP engineers (n=20727) were active on GitHub. | 3% 3% (n=15) of all PingCAP employees (n=46728) were active on GitHub. | 15 15 PingCAP employees were active on GitHub. |
| 15. DataDog | 7% 7% (n=260) of all DataDog engineers (n=3,90029) were active on GitHub. | 3% 3% (n=260) of all DataDog employees (n=8,10030) were active on GitHub. | 260 260 DataDog employees were active on GitHub. |
| 16. WSO2 | 6% 6% (n=46) of all WSO2 engineers (n=72531) were active on GitHub. | 4% 4% (n=46) of all WSO2 employees (n=1,21532) were active on GitHub. | 46 46 WSO2 employees were active on GitHub. |
| 17. Odoo | 2% 2% (n=23) of all Odoo engineers (n=1,07433) were active on GitHub. | 0% 0% (n=23) of all Odoo employees (n=7,81834) were active on GitHub. | 23 23 Odoo employees were active on GitHub. |
| 18. Confluent | 2% 2% (n=29) of all Confluent engineers (n=1,36735) were active on GitHub. | 1% 1% (n=29) of all Confluent employees (n=3,24136) were active on GitHub. | 29 29 Confluent employees were active on GitHub. |
| 19. Microsoft | 2% 2% (n=1,671) of all Microsoft engineers (n=80,00037) were active on GitHub. | 1% 1% (n=1,671) of all Microsoft employees (n=228,00038) were active on GitHub. | 1,671 1,671 Microsoft employees were active on GitHub. |
| 20. Shopify | 2% 2% (n=89) of all Shopify engineers (n=4,65839) were active on GitHub. | 1% 1% (n=89) of all Shopify employees (n=7,60040) were active on GitHub. | 89 89 Shopify employees were active on GitHub. |
| 21. MongoDB | 2% 2% (n=42) of all MongoDB engineers (n=2,20441) were active on GitHub. | 1% 1% (n=42) of all MongoDB employees (n=5,63642) were active on GitHub. | 42 42 MongoDB employees were active on GitHub. |
| 22. Alibaba | 2% 2% (n=165) of all Alibaba engineers (n=9,84743) were active on GitHub. | 0% 0% (n=165) of all Alibaba employees (n=126,66144) were active on GitHub. | 165 165 Alibaba employees were active on GitHub. |
| 23. NVIDIA | 2% 2% (n=504) of all NVIDIA engineers (n=31,00045) were active on GitHub. | 1% 1% (n=504) of all NVIDIA employees (n=42,00046) were active on GitHub. | 504 504 NVIDIA employees were active on GitHub. |
| 24. OpenAI | 2% 2% (n=44) of all OpenAI engineers (n=2,91647) were active on GitHub. | 1% 1% (n=44) of all OpenAI employees (n=7,30348) were active on GitHub. | 44 44 OpenAI employees were active on GitHub. |
| 25. Snowflake, Inc. | 1% 1% (n=30) of all Snowflake, Inc. engineers (n=2,25749) were active on GitHub. | 0% 0% (n=30) of all Snowflake, Inc. employees (n=7,83450) were active on GitHub. | 30 30 Snowflake, Inc. employees were active on GitHub. |
| 26. AMD | 1% 1% (n=283) of all AMD engineers (n=21,98451) were active on GitHub. | 1% 1% (n=283) of all AMD employees (n=31,00052) were active on GitHub. | 283 283 AMD employees were active on GitHub. |
| 27. Okta | 1% 1% (n=20) of all Okta engineers (n=1,66653) were active on GitHub. | 0% 0% (n=20) of all Okta employees (n=6,36654) were active on GitHub. | 20 20 Okta employees were active on GitHub. |
| 28. Databricks | 1% 1% (n=65) of all Databricks engineers (n=6,20455) were active on GitHub. | 0% 0% (n=65) of all Databricks employees (n=14,59256) were active on GitHub. | 65 65 Databricks employees were active on GitHub. |
| 29. Arm Ltd | 1% 1% (n=68) of all Arm Ltd engineers (n=6,94357) were active on GitHub. | 1% 1% (n=68) of all Arm Ltd employees (n=8,33058) were active on GitHub. | 68 68 Arm Ltd employees were active on GitHub. |
| 30. Amazon | 1% 1% (n=471) of all Amazon engineers (n=49,06659) were active on GitHub. | 0% 0% (n=471) of all Amazon employees (n=153,71060) were active on GitHub. | 471 471 Amazon employees were active on GitHub. |
| 31. Netflix | 1% 1% (n=30) of all Netflix engineers (n=3,13061) were active on GitHub. | 0% 0% (n=30) of all Netflix employees (n=16,00062) were active on GitHub. | 30 30 Netflix employees were active on GitHub. |
| 32. Google | 1% 1% (n=791) of all Google engineers (n=83,31863) were active on GitHub. | 0% 0% (n=791) of all Google employees (n=190,82064) were active on GitHub. | 791 791 Google employees were active on GitHub. |
| 33. Adobe | 1% 1% (n=104) of all Adobe engineers (n=11,43665) were active on GitHub. | 0% 0% (n=104) of all Adobe employees (n=31,36066) were active on GitHub. | 104 104 Adobe employees were active on GitHub. |
| 34. Tencent | 1% 1% (n=120) of all Tencent engineers (n=13,32967) were active on GitHub. | 0% 0% (n=120) of all Tencent employees (n=110,55868) were active on GitHub. | 120 120 Tencent employees were active on GitHub. |
| 35. Square, Inc. | 1% 1% (n=26) of all Square, Inc. engineers (n=2,95069) were active on GitHub. | 0% 0% (n=26) of all Square, Inc. employees (n=10,20570) were active on GitHub. | 26 26 Square, Inc. employees were active on GitHub. |
| 36. Unity Technologies | 1% 1% (n=24) of all Unity Technologies engineers (n=2,88771) were active on GitHub. | 1% 1% (n=24) of all Unity Technologies employees (n=4,41272) were active on GitHub. | 24 24 Unity Technologies employees were active on GitHub. |
| 37. Stripe | 1% 1% (n=32) of all Stripe engineers (n=4,27673) were active on GitHub. | 0% 0% (n=32) of all Stripe employees (n=13,72274) were active on GitHub. | 32 32 Stripe employees were active on GitHub. |
| 38. ESRI | 1% 1% (n=15) of all ESRI engineers (n=2,28775) were active on GitHub. | 0% 0% (n=15) of all ESRI employees (n=7,16576) were active on GitHub. | 15 15 ESRI employees were active on GitHub. |
| 39. Spotify | 1% 1% (n=23) of all Spotify engineers (n=3,78777) were active on GitHub. | 0% 0% (n=23) of all Spotify employees (n=7,28778) were active on GitHub. | 23 23 Spotify employees were active on GitHub. |
| 40. Airbnb | 1% 1% (n=20) of all Airbnb engineers (n=3,69679) were active on GitHub. | 0% 0% (n=20) of all Airbnb employees (n=8,20080) were active on GitHub. | 20 20 Airbnb employees were active on GitHub. |
| 41. ThoughtWorks | 0% 0% (n=20) of all ThoughtWorks engineers (n=4,00881) were active on GitHub. | 0% 0% (n=20) of all ThoughtWorks employees (n=10,50082) were active on GitHub. | 20 20 ThoughtWorks employees were active on GitHub. |
| 42. Meta | 0% 0% (n=185) of all Meta engineers (n=39,83583) were active on GitHub. | 0% 0% (n=185) of all Meta employees (n=78,86584) were active on GitHub. | 185 185 Meta employees were active on GitHub. |
| 43. Broadcom | 0% 0% (n=87) of all Broadcom engineers (n=18,81085) were active on GitHub. | 0% 0% (n=87) of all Broadcom employees (n=33,00086) were active on GitHub. | 87 87 Broadcom employees were active on GitHub. |
| 44. Intel | 0% 0% (n=201) of all Intel engineers (n=51,69387) were active on GitHub. | 0% 0% (n=201) of all Intel employees (n=85,10088) were active on GitHub. | 201 201 Intel employees were active on GitHub. |
| 45. Autodesk | 0% 0% (n=18) of all Autodesk engineers (n=4,88389) were active on GitHub. | 0% 0% (n=18) of all Autodesk employees (n=15,30090) were active on GitHub. | 18 18 Autodesk employees were active on GitHub. |
| 46. Yandex | 0% 0% (n=38) of all Yandex engineers (n=11,02091) were active on GitHub. | 0% 0% (n=38) of all Yandex employees (n=29,00092) were active on GitHub. | 38 38 Yandex employees were active on GitHub. |
| 47. Bloomberg | 0% 0% (n=28) of all Bloomberg engineers (n=8,34493) were active on GitHub. | 0% 0% (n=28) of all Bloomberg employees (n=25,76894) were active on GitHub. | 28 28 Bloomberg employees were active on GitHub. |
| 48. Uber | 0% 0% (n=29) of all Uber engineers (n=8,75995) were active on GitHub. | 0% 0% (n=29) of all Uber employees (n=34,00096) were active on GitHub. | 29 29 Uber employees were active on GitHub. |
| 49. Cisco Systems | 0% 0% (n=77) of all Cisco Systems engineers (n=25,25697) were active on GitHub. | 0% 0% (n=77) of all Cisco Systems employees (n=86,20098) were active on GitHub. | 77 77 Cisco Systems employees were active on GitHub. |
| 50. Atlassian | 0% 0% (n=21) of all Atlassian engineers (n=6,90699) were active on GitHub. | 0% 0% (n=21) of all Atlassian employees (n=13,813100) were active on GitHub. | 21 21 Atlassian employees were active on GitHub. |
| 51. Salesforce | 0% 0% (n=66) of all Salesforce engineers (n=24,359101) were active on GitHub. | 0% 0% (n=66) of all Salesforce employees (n=83,334102) were active on GitHub. | 66 66 Salesforce employees were active on GitHub. |
| 52. Apple | 0% 0% (n=123) of all Apple engineers (n=45,932103) were active on GitHub. | 0% 0% (n=123) of all Apple employees (n=166,000104) were active on GitHub. | 123 123 Apple employees were active on GitHub. |
| 53. SAP SE | 0% 0% (n=92) of all SAP SE engineers (n=37,965105) were active on GitHub. | 0% 0% (n=92) of all SAP SE employees (n=111,397106) were active on GitHub. | 92 92 SAP SE employees were active on GitHub. |
| 54. Baidu | 0% 0% (n=41) of all Baidu engineers (n=18,600107) were active on GitHub. | 0% 0% (n=41) of all Baidu employees (n=39,800108) were active on GitHub. | 41 41 Baidu employees were active on GitHub. |
| 55. NetEase | 0% 0% (n=17) of all NetEase engineers (n=12,754109) were active on GitHub. | 0% 0% (n=17) of all NetEase employees (n=26,028110) were active on GitHub. | 17 17 NetEase employees were active on GitHub. |
| 56. PayPal | 0% 0% (n=13) of all PayPal engineers (n=10,643111) were active on GitHub. | 0% 0% (n=13) of all PayPal employees (n=23,800112) were active on GitHub. | 13 13 PayPal employees were active on GitHub. |
| 57. Oracle | 0% 0% (n=58) of all Oracle engineers (n=50,000113) were active on GitHub. | 0% 0% (n=58) of all Oracle employees (n=162,000114) were active on GitHub. | 58 58 Oracle employees were active on GitHub. |
| 58. EPAM Systems | 0% 0% (n=45) of all EPAM Systems engineers (n=56,600115) were active on GitHub. | 0% 0% (n=45) of all EPAM Systems employees (n=62,850116) were active on GitHub. | 45 45 EPAM Systems employees were active on GitHub. |
| 59. Nokia | 0% 0% (n=18) of all Nokia engineers (n=31,780117) were active on GitHub. | 0% 0% (n=18) of all Nokia employees (n=78,005118) were active on GitHub. | 18 18 Nokia employees were active on GitHub. |
| 60. Samsung | 0% 0% (n=29) of all Samsung engineers (n=88,984119) were active on GitHub. | 0% 0% (n=29) of all Samsung employees (n=262,647120) were active on GitHub. | 29 29 Samsung employees were active on GitHub. |
| 61. Huawei | 0% 0% (n=32) of all Huawei engineers (n=113,000121) were active on GitHub. | 0% 0% (n=32) of all Huawei employees (n=208,000122) were active on GitHub. | 32 32 Huawei employees were active on GitHub. |
| 62. Capgemini | 0% 0% (n=14) of all Capgemini engineers (n=82,175123) were active on GitHub. | 0% 0% (n=14) of all Capgemini employees (n=341,100124) were active on GitHub. | 14 14 Capgemini employees were active on GitHub. |
| 63. IBM | (n=955) of all IBM engineers (n=NaN0) were active on GitHub. | 0% 0% (n=955) of all IBM employees (n=264,300125) were active on GitHub. | 955 955 IBM employees were active on GitHub. |
| 64. ByteDance | (n=121) of all ByteDance engineers (n=NaN0) were active on GitHub. | (n=121) of all ByteDance employees (n=NaN0) were active on GitHub. | 121 121 ByteDance employees were active on GitHub. |
| 65. Canonical | (n=68) of all Canonical engineers (n=NaN0) were active on GitHub. | (n=68) of all Canonical employees (n=NaN0) were active on GitHub. | 68 68 Canonical employees were active on GitHub. |
| 66. Software Mansion | (n=54) of all Software Mansion engineers (n=NaN0) were active on GitHub. | (n=54) of all Software Mansion employees (n=NaN0) were active on GitHub. | 54 54 Software Mansion employees were active on GitHub. |
| 67. Posit | (n=43) of all Posit engineers (n=NaN0) were active on GitHub. | (n=43) of all Posit employees (n=NaN0) were active on GitHub. | 43 43 Posit employees were active on GitHub. |
| 68. 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. |
| 69. Accenture | (n=33) of all Accenture engineers (n=NaN0) were active on GitHub. | 0% 0% (n=33) of all Accenture employees (n=779,000126) were active on GitHub. | 33 33 Accenture employees were active on GitHub. |
| 70. @supabase | (n=24) of all @supabase engineers (n=NaN0) were active on GitHub. | (n=24) of all @supabase employees (n=NaN0) were active on GitHub. | 24 24 @supabase employees were active on GitHub. |
| 71. Palo Alto Networks | (n=24) of all Palo Alto Networks engineers (n=NaN0) were active on GitHub. | 0% 0% (n=24) of all Palo Alto Networks employees (n=16,068127) were active on GitHub. | 24 24 Palo Alto Networks employees were active on GitHub. |
| 72. @PostHog | (n=19) of all @PostHog engineers (n=NaN0) were active on GitHub. | (n=19) of all @PostHog employees (n=NaN0) were active on GitHub. | 19 19 @PostHog employees were active on GitHub. |
| 73. Supabase | (n=19) of all Supabase engineers (n=NaN0) were active on GitHub. | (n=19) of all Supabase employees (n=NaN0) were active on GitHub. | 19 19 Supabase employees were active on GitHub. |
| 74. Ericsson | (n=18) of all Ericsson engineers (n=NaN0) were active on GitHub. | 0% 0% (n=18) of all Ericsson employees (n=88,826128) were active on GitHub. | 18 18 Ericsson employees were active on GitHub. |
| 75. Anthropic | (n=18) of all Anthropic engineers (n=NaN0) were active on GitHub. | (n=18) of all Anthropic employees (n=NaN0) were active on GitHub. | 18 18 Anthropic employees were active on GitHub. |
| 76. @zed-industries | (n=18) of all @zed-industries engineers (n=NaN0) were active on GitHub. | (n=18) of all @zed-industries employees (n=NaN0) were active on GitHub. | 18 18 @zed-industries employees were active on GitHub. |
| 77. Sanity | (n=18) of all Sanity engineers (n=NaN0) were active on GitHub. | (n=18) of all Sanity employees (n=NaN0) were active on GitHub. | 18 18 Sanity employees were active on GitHub. |
| 78. Expensify | (n=17) of all Expensify engineers (n=NaN0) were active on GitHub. | (n=17) of all Expensify employees (n=NaN0) were active on GitHub. | 17 17 Expensify employees were active on GitHub. |
| 79. Juspay | (n=17) of all Juspay engineers (n=NaN0) were active on GitHub. | (n=17) of all Juspay employees (n=NaN0) were active on GitHub. | 17 17 Juspay employees were active on GitHub. |
| 80. @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. |
| 81. @expo | (n=16) of all @expo engineers (n=NaN0) were active on GitHub. | (n=16) of all @expo employees (n=NaN0) were active on GitHub. | 16 16 @expo employees were active on GitHub. |
| 82. Metabase | (n=15) of all Metabase engineers (n=NaN0) were active on GitHub. | (n=15) of all Metabase employees (n=NaN0) were active on GitHub. | 15 15 Metabase employees were active on GitHub. |
| 83. @frappe | (n=15) of all @frappe engineers (n=NaN0) were active on GitHub. | (n=15) of all @frappe employees (n=NaN0) were active on GitHub. | 15 15 @frappe employees were active on GitHub. |
| 84. @PostHog | (n=15) of all @PostHog engineers (n=NaN0) were active on GitHub. | (n=15) of all @PostHog employees (n=NaN0) were active on GitHub. | 15 15 @PostHog employees were active on GitHub. |
| 85. Anyscale | (n=15) of all Anyscale engineers (n=NaN0) were active on GitHub. | (n=15) of all Anyscale employees (n=NaN0) were active on GitHub. | 15 15 Anyscale employees were active on GitHub. |
| 86. @apache | (n=15) of all @apache engineers (n=NaN0) were active on GitHub. | (n=15) of all @apache employees (n=NaN0) were active on GitHub. | 15 15 @apache employees were active on GitHub. |
| 87. Sentry | (n=14) of all Sentry engineers (n=NaN0) were active on GitHub. | (n=14) of all Sentry employees (n=NaN0) were active on GitHub. | 14 14 Sentry employees were active on GitHub. |
| 88. @bitwarden | (n=14) of all @bitwarden engineers (n=NaN0) were active on GitHub. | (n=14) of all @bitwarden employees (n=NaN0) were active on GitHub. | 14 14 @bitwarden employees were active on GitHub. |
| 89. Bitwarden | (n=14) of all Bitwarden engineers (n=NaN0) were active on GitHub. | (n=14) of all Bitwarden employees (n=NaN0) were active on GitHub. | 14 14 Bitwarden employees were active on GitHub. |
| 90. Redis | (n=14) of all Redis engineers (n=NaN0) were active on GitHub. | (n=14) of all Redis employees (n=NaN0) were active on GitHub. | 14 14 Redis employees were active on GitHub. |
| 91. ServiceNow | (n=14) of all ServiceNow engineers (n=NaN0) were active on GitHub. | 0% 0% (n=14) of all ServiceNow employees (n=29,187129) were active on GitHub. | 14 14 ServiceNow employees were active on GitHub. |
| 92. UIUC | (n=14) of all UIUC engineers (n=NaN0) were active on GitHub. | (n=14) of all UIUC employees (n=NaN0) were active on GitHub. | 14 14 UIUC employees were active on GitHub. |
| 93. @espressif | (n=14) of all @espressif engineers (n=NaN0) were active on GitHub. | (n=14) of all @espressif employees (n=NaN0) were active on GitHub. | 14 14 @espressif employees were active on GitHub. |
| 94. @GetStream | (n=14) of all @GetStream engineers (n=NaN0) were active on GitHub. | (n=14) of all @GetStream employees (n=NaN0) were active on GitHub. | 14 14 @GetStream employees were active on GitHub. |
| 95. AntGroup | (n=13) of all AntGroup engineers (n=NaN0) were active on GitHub. | (n=13) of all AntGroup employees (n=NaN0) were active on GitHub. | 13 13 AntGroup employees were active on GitHub. |
| 96. @temporalio | (n=13) of all @temporalio engineers (n=NaN0) were active on GitHub. | (n=13) of all @temporalio employees (n=NaN0) were active on GitHub. | 13 13 @temporalio employees were active on GitHub. |
| 97. Ant Group | (n=13) of all Ant Group engineers (n=NaN0) were active on GitHub. | (n=13) of all Ant Group employees (n=NaN0) were active on GitHub. | 13 13 Ant Group employees were active on GitHub. |
| 98. Figma | (n=13) of all Figma engineers (n=NaN0) were active on GitHub. | (n=13) of all Figma employees (n=NaN0) were active on GitHub. | 13 13 Figma employees were active on GitHub. |
| 99. @anthropics | (n=13) of all @anthropics engineers (n=NaN0) were active on GitHub. | (n=13) of all @anthropics employees (n=NaN0) were active on GitHub. | 13 13 @anthropics employees were active on GitHub. |
| 100. Yahoo! | (n=13) of all Yahoo! engineers (n=NaN0) were active on GitHub. | (n=13) of all Yahoo! employees (n=NaN0) were active on GitHub. | 13 13 Yahoo! 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)
- Automattic engineer count: linkedin.com (Retrieved January 2026)
- Automattic employee count: automattic.com (Retrieved January 2026)
- Elastic engineer count: linkedin.com (retrieved January 2026)
- Elastic employee count: sec.gov (page 15)
- Docker engineer count: linkedin.com (Retrieved January 2026)
- Docker employee count: linkedin.com (Retrieved January 2026)
- Kitware engineer count: linkedin.com (Retrieved January 2026)
- Kitware employee count: linkedin.com (Retrieved January 2026)
- SUSE engineer count: linkedin.com (Retrieved January 2026)
- SUSE employee count: linkedin.com (Retrieved January 2026)
- Mozilla engineer count: linkedin.com (Retrieved January 2026)
- Mozilla employee count: linkedin.com (Retrieved January 2026)
- Tenstorrent engineer count: linkedin.com (Retrieved March 2026)
- Tenstorrent employee count: linkedin.com (Retrieved March 2026)
- JetBrains engineer count: linkedin.com
- JetBrains employee count: jetbrains.com
- Cloudflare engineer count: linkedin.com (Retrieved January 2026)
- Cloudflare employee count: sec.gov (page 18)
- PingCAP engineer count: linkedin.com (Retrieved August 2025)
- PingCAP employee count: linkedin.com (Retrieved August 2025)
- DataDog engineer count: sec.gov (page 11, referred to as employees in 'research and development')
- DataDog employee count: sec.gov (page 12)
- WSO2 engineer count: linkedin.com (Retrieved January 2026)
- WSO2 employee count: linkedin.com (Retrieved January 2026)
- Odoo engineer count: linkedin.com (Retrieved January 2026)
- Odoo employee count: linkedin.com (Retrieved January 2026)
- Confluent engineer count: linkedin.com (Retrieved January 2026)
- Confluent employee count: sec.gov (page 19)
- 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)
- MongoDB engineer count: linkedin.com (Retrieved March 2026)
- MongoDB employee count: sec.gov (page 9)
- Alibaba engineer count: linkedin.com (Retrieved January 2026)
- Alibaba employee count: data.alibabagroup.com (page 14)
- NVIDIA engineer count: sec.gov (page 11, referred to as employees in 'research and development')
- NVIDIA employee count: sec.gov (page 11)
- OpenAI engineer count: linkedin.com (Retrieved February 2026)
- OpenAI employee count: linkedin.com (Retrieved February 2026)
- Snowflake, Inc. engineer count: sec.gov (page 15)
- Snowflake, Inc. employee count: sec.gov (page 16)
- AMD engineer count: linkedin.com (Retrieved January 2026)
- AMD employee count: sec.gov (page 11)
- Okta engineer count: linkedin.com (Retrieved January 2026)
- Okta employee count: sec.gov (page 13)
- Databricks engineer count: linkedin.com (Retrieved February 2026)
- Databricks employee count: linkedin.com (Retrieved February 2026)
- Arm Ltd engineer count: sec.gov (page 110)
- Arm Ltd employee count: sec.gov (page 110)
- Amazon engineer count: linkedin.com (Retrieved January 2026)
- Amazon employee count: linkedin.com (Retrieved January 2026)
- Netflix engineer count: linkedin.com (Retrieved January 2026)
- Netflix employee count: sec.gov (page 2)
- Google engineer count: linkedin.com (Retrieved January 2026)
- Google employee count: sec.gov (page 7)
- Adobe engineer count: linkedin.com (Retrieved January 2026)
- Adobe employee count: sec.gov (page 13)
- Tencent engineer count: linkedin.com (Retrieved January 2026)
- Tencent employee count: static.tencent.com (page 52)
- Square, Inc. engineer count: linkedin.com (Retrieved January 2026)
- Square, Inc. employee count: sec.gov (page 19)
- Unity Technologies engineer count: sec.gov (page 3, referred to as employees in 'technical roles')
- Unity Technologies employee count: sec.gov (page 3)
- Stripe engineer count: linkedin.com (Retrieved January 2026)
- Stripe employee count: linkedin.com (Retrieved January 2026)
- ESRI engineer count: linkedin.com (Retrieved January 2026)
- ESRI 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)
- ThoughtWorks engineer count: linkedin.com (Retrieved January 2026)
- ThoughtWorks employee count: sec.gov (page 6)
- Meta engineer count: linkedin.com (Retrieved January 2026)
- Meta employee count: sec.gov (page 9)
- Broadcom engineer count: sec.gov (page 9, referred to as 'research and development')
- Broadcom employee count: sec.gov (page 9)
- Intel engineer count: linkedin.com (Retrieved January 2026)
- Intel employee count: sec.gov (page 15)
- Autodesk engineer count: linkedin.com (Retrieved January 2026)
- Autodesk employee count: sec.gov (page 13)
- Yandex engineer count: yastatic.net (page 54, referred to as 'developers)
- Yandex employee count: yastatic.net (page 12)
- Bloomberg engineer count: linkedin.com (Retrieved January 2026)
- Bloomberg employee count: linkedin.com (Retrieved January 2026)
- Uber engineer count: linkedin.com (Retrieved January 2026)
- Uber employee count: sec.gov (page 7)
- Cisco Systems engineer count: sec.gov (page 8, referred to as employees in 'research and development')
- Cisco Systems employee count: sec.gov (page 8)
- 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)
- Salesforce engineer count: linkedin.com (Retrieved January 2026)
- Salesforce employee count: sec.gov (page 10)
- Apple engineer count: linkedin.com (Retrieved January 2025)
- Apple employee count: sec.gov (page 4)
- SAP SE engineer count: sec.gov (page 31, referred to as employees in 'development')
- SAP SE employee count: sec.gov (page 100)
- Baidu engineer count: sec.gov (page 179, referred to as employees in 'research and development')
- Baidu employee count: sec.gov (page 179)
- NetEase engineer count: sec.gov (page 146, referred to as 'R&D staff')
- NetEase employee count: sec.gov (page 146)
- PayPal engineer count: linkedin.com (Retrieved January 2026)
- PayPal employee count: sec.gov (page 12)
- 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)
- Nokia engineer count: linkedin.com (Retrieved January 2026)
- Nokia employee count: sec.gov (page 66)
- Samsung engineer count: images.samsung.com (page 64, referred to as employees in 'development')
- Samsung employee count: images.samsung.com (page 64)
- Huawei engineer count: huawei.com (page 72, referred to as employees in 'R&D')
- Huawei employee count: huawei.com (page 1)
- Capgemini engineer count: linkedin.com (Retrieved January 2026)
- Capgemini employee count: investors.capgemini.com (page 4)
- IBM employee count: ibm.com (page 15)
- Accenture employee count: sec.gov (page 3)
- Palo Alto Networks employee count: sec.gov (page 11)
- Ericsson employee count: sec.gov (page 7)
- ServiceNow employee count: sec.gov (page 21)