Our work / Thunder Compute

From scattered profiles to research a team can use.

606Distinct LinkedIn profiles in a saved shortlistSaved delivery evidence. Shortlist entries, not hiring outcomes.
Thunder ComputeFrom scattered profiles to research a team can use.
Carl Peterson & Brian Model

A company research workflow, LinkedIn–GitHub matching and a review application. Built to help a specialist team find and assess systems engineers with the evidence in one place.

The challenge

Specialist engineering research meant opening profiles, interpreting job titles, searching for public coding work and copying findings into spreadsheets. Repeating that process made it difficult to maintain a consistent shortlist or see what had changed.

The work

We built two complementary tools: a Google Sheets research workflow and a searchable web application. Company-based collection, role checks and possible GitHub matches feed organized research. The dashboard adds profile details, inclusion and exclusion decisions, company coverage, public activity history and export tools.

The result

A saved delivery shortlist contains 606 rows with 606 distinct LinkedIn profile links. The team received reusable research data and the tools to review it, refresh new profiles and inspect changes. That count describes the saved research output, not hires or independently verified identity matches.

Inside the delivery

Two interfaces. A more repeatable research process.

Researchers can start in Google Sheets, then use the web application to compare profiles and make review decisions. Import and export tools connect the outputs; this is not a two-way live sync.

01

Company to candidate research

Collect available employee profiles, check likely engineering roles and apply a narrower fit score with reasons for the research brief.

02

Professional experience meets public work

Inspect LinkedIn background beside possible GitHub matches, with identity checks, confidence information, projects and programming languages.

03

A review process the team controls

Search and filter profiles, compare company coverage, include or exclude candidates and retain manual archive decisions during relevant refreshes.

04

History that gives the next review context

Inspect dated snapshots and public coding activity. Configurable summaries bring visible changes together for a researcher to assess.

05

Reuse research already completed

Refreshes process newly found people without repeating every classification. Recent lookups, imports and exports keep useful research reusable.

06

Built to be operated

Job status, retries, health checks and documented deployment support the workflow. Researchers remain responsible for identity checks and shortlist decisions.

Documented output

A concrete research deliverable.

606 saved rows. 606 distinct LinkedIn links. Each record brings together available role, location, fit information, profile links and a summary.

The supplied review checked saved files and repository snapshots. Public coding activity does not establish willingness to change jobs, and the shortlist is not a record of hires.
Another perspective on the work

BlackFly Media

Let’s make it happen

What’s your next move?

Tell us what’s slowing you down—or what you’re ready to build.

Start a conversation