StartupBlink: case study
I lead the seven engineers behind ~18M requests a month.
~18Mrequests a month
~70%cache-hit rate
+35%engagement in 5 months
01
The problem, and who it’s for
StartupBlink is a global startup-ecosystem intelligence platform. It ranks 300,000+ startups across 2,000+ cities in 118 countries, and 40+ government clients rely on it.
02
What the job is
Everything a lead engineer does. I set the architecture and the standards, review the code, plan delivery with seven engineers and keep production healthy. I also own the tooling that makes the team faster, including how we use AI.
03
What I own
Here is the path a request takes.
- The architecture of a Turborepo monorepo: TypeScript, Node.js, tRPC, Prisma, MySQL, Redis and React/Next.js.
- The migration of legacy JavaScript into a TypeScript monorepo of 10+ packages and apps, with shared services reused across 5+ apps.
- Operating and tuning the Cloudflare-fronted, Redis-cached setup.
- CI/CD that ships 2+ production deploys a week.
- Structured AI-assisted engineering for the team: coding agents, MCP integrations, custom skills and multi-agent workflows, all under human review.
- Visitors
- 37K+ unique visitors a day, and about 18M requests a month.
- Cloudflare
- The edge in front of everything. I operate and tune it.
- Redis
- The cache behind Cloudflare. Together they reach a ~70% cache-hit rate.
- Apps
- React/Next.js apps and Node.js services using tRPC, in a Turborepo of 10+ packages and apps.
- MySQL
- The database, through Prisma.
Click a step, or use the arrow keys.
04
The hard parts, and the decisions
- One typed monorepo.Legacy JavaScript moved into a TypeScript Turborepo of 10+ packages and apps. Its shared services are reused across 5+ apps.
- Cache before compute.Cloudflare in front, Redis behind: a ~70% cache-hit rate on ~18M requests a month.
- Ship often.2+ production deploys a week, with deploy time cut by 50%.
- AI-assisted, human-reviewed.Agents help with the work. People review everything that ships.
05
What happened
The results I can put numbers on. The engagement jump came after an end-to-end platform refactor that I led.
+35%user engagement in 5 months
−50%deployment time
2+/weekproduction deploys
37K+unique visitors a day