MasudMasud
← MasudAll work
2025 — Present·Senior Software Engineer

LeadSync Extension

Find · close leads · Chrome

Install from the Chrome Web Store to capture searches and profiles straight into LeadSync—authenticated against the same account as the dashboard so prospects land in sequences with correct tenancy and rate-aware scheduling.

Chrome Web Store
LeadSync Extension

Role

Senior Software Engineer

Year

2025 — Present

Stack

TypeScript · Chrome Extension · Manifest V3

Status

Shipped

01 / Problem

Problem

Reps lived in LinkedIn tabs but campaigns lived in another product—manual CSV exports and copy-paste dropped fields and wasted hours.

02 / Solution

Solution

A Manifest V3 Chrome extension with a hardened content-script boundary, OAuth-aligned session handoff to the LeadSync API, and UX that respects LinkedIn pacing while pushing structured leads into campaign queues.

03 / Outcome

Outcome

Shipped on the Chrome Web Store as the primary LinkedIn-side entry point—imports feed the same sequencing and tenancy model as the web dashboard.

✦ Scope

Owned the extension codebase—permissions model, messaging bridge to the platform APIs, release packaging, and Web Store lifecycle alongside the core product.

✦ Key features

What makes it work.

  • 01

    One-click import from LinkedIn search and Sales Navigator views

  • 02

    Structured prospect payloads mapped to LeadSync tenant schemas

  • 03

    Session continuity with dashboard login — no duplicate accounts

  • 04

    Human-paced actions aligned with LeadSync sequencing safeguards

  • 05

    Inline feedback when imports succeed or need attention

  • 06

    Manifest V3–compliant service worker and content isolation

✦ Tech stack

  • TypeScript
  • Chrome Extension
  • Manifest V3