How I unified 13 ATS providers into one trusted talent board for VC networks

The obvious approach: build a job board and bolt on VC management later. Instead, I treated each VC's data scope as the fundamental design unit. A single job record in the database flows through three entirely different user experiences — with zero data duplication.

The key insight: a VC should be able to hide a job from their branded career page without affecting the public board or other VCs. This isn't a visibility toggle on the job itself — it's context-dependent availability. The same "Senior Engineer at Stripe" listing can be visible on the public board, hidden from Techstars' career page, and featured on Orange DAO's — all from one database record.

The standard approach to multi-role products: show different features per role. Show more buttons for admins, fewer for talent. But Bridge's users don't just need different features — they need a fundamentally different relationship with the same data.

A VC manager looking at "23 jobs this week" sees a portfolio health metric. An admin seeing the same number sees a platform growth signal. Talent sees opportunity. Same number, three meanings. I designed the entire interface around this principle: roles don't just gate access — they change what data means.

Here's the counterintuitive product decision: Bridge's best outcome is when VCs forget they're using Bridge. The career page at careers.techstars.com shouldn't look like a Bridge product — it should look like Techstars built it themselves.

I designed the career pages not as white-label templates (slap a logo on and ship), but as fully owned product surfaces. Custom domain routing at the edge proxy level. Per-VC navigation, hero content, footer links, and social icons — all configurable from the VC Manager settings panel. JSON-LD structured data scoped to each VC. Even an offline screen that carries the VC's brand, not Bridge's.

This changed Bridge's distribution model. VCs don't share bridge.app links — they share their own career page URL. Bridge becomes invisible infrastructure, and that's exactly what makes VCs adopt it.

A job board that shows stale listings is worse than no job board at all. But most platforms hide their sync status behind admin dashboards or monitoring tools. I made a different choice: make data freshness a first-class, visible metric that VC managers and admins see every time they open their dashboard.

The "Last synced" stat card uses color-coded urgency — green when fresh, amber when aging, red when stale. This isn't decoration. It's a trust mechanism that turns infrastructure health into a product feature. VCs can immediately tell if their job data is current without filing a support ticket.