WebVetted
+ New  

LinkedIn OSINT Intelligence Report: Ayham Tannous

Generated: Jun 29, 2026

Ayham Tannous Profile Picture

Ayham Tannous

Person

Bottom Line Up Front

This appears to be a real LinkedIn profile for Ayham Tannous, a verified Software Engineer at Meta in Seattle. The profile has a strong identity match, a long work history in software engineering, and no obvious impersonation signals in the provided evidence. The main limitation is that there are no posts, so behavioral and audience-authenticity analysis is thin.

Key Judgments

The LinkedIn profile is strongly attributable to Ayham Tannous, with exact name match, matching Seattle location, and corroborated employment at Meta.

Almost certain High Confidence

The account shows low authenticity risk based on the available evidence, because the profile is verified and the work and education history are coherent.

Likely High Confidence

There is limited behavioral signal because no LinkedIn posts were observed in the evidence set.

Almost certain High Confidence

Risk Assessment

12%
Low Risk

Analytic confidence in this assessment is high.


Identity resolution

Live Intel Map

Resolved Primary Identity

Ayham Tannous

Assessment

High-confidence resolution to Ayham Tannous, a verified LinkedIn user profile tied to a Software Engineer role at Meta in Seattle. The profile details are internally coherent: name, title, current employer, location, education, and career timeline all line up without major conflict. Cross-platform search also produced one strong LinkedIn match and several weaker same-name candidates, which reinforces the primary attribution rather than undermining it.

Resolved Identifiers

full name

Ayham Tannous

job title

Software Engineer

employer

Meta

location

Seattle, Washington, United States

school

The George Washington University

organization

LinkedIn verified profile

Online presence

Ayham Tannous

LinkedIn • Public

Location: Seattle, Washington, United States
Category: Software Engineer

Linkage Basis:

  • Exact full-name match
  • Verified LinkedIn profile
  • Matching Seattle location
  • Matching software engineering career history
  • Cross-platform search match
Ayham Tannous

Facebook • Public

Location: Seattle, Washington

Linkage Basis:

  • Exact name match
  • Seattle location match
Ayham Tannous

Instagram • Public

Linkage Basis:

  • Exact name match only
Ayham Tannous

X • Public

Linkage Basis:

  • Exact name match only
  • Sparse profile bio
Ayham Tannous

Pinterest • Public

Linkage Basis:

  • Username match only

Account OSINT

Top Associated Accounts

The network is dominated by professional and education anchors rather than interpersonal links. Meta, Amazon, Expedia, Damascus University, and The George Washington University are the only strong associations in the evidence set. A Facebook account with the same name and Seattle location may belong to the same person, but the linkage is not strong enough to treat as resolved.

M

Meta

employee_employer

LinkedIn profile

"Current employer and strongest organizational anchor."

E

Expedia Group

employee_employer

LinkedIn profile

"Prior employer consistent with the subject’s engineering timeline."

A

Amazon.com

employee_employer

LinkedIn profile

"Prior employer and a strong corroborating career marker."

T

The George Washington University

school

LinkedIn profile

"Graduate education association supporting identity resolution."

D

Damascus University

school

LinkedIn profile

"Undergraduate education association supporting identity resolution."

A

Ayham Tannous (Facebook candidate, Seattle)

same_contact_point

Cross-platform social search

"Possible secondary profile, but not confirmed."

Who is Ayham Tannous associated with?

Reveal the Linkedin accounts Ayham Tannous is connected to and interacts with most.

Reveal Associates »

Account Timeline

The profile reflects a long-running, professionally oriented account with sparse public content. Career history is the main temporal signal, and it is coherent across more than a decade of employment and education.

Job Change

Joined Meta in August 2020 after prior roles at Expedia and Amazon.

Shows a steady software engineering career path across major employers.

Education Change

BS completed 2001-2006; MS completed 2009-2011.

Academic timeline is coherent and supports the identity resolution.

Activity Gap

No LinkedIn posts observed in the available record.

Public activity is minimal, so chronology from content cannot be reconstructed.

Interactive Graph

Map the hidden network.

Switch to the interactive workbench to trace relationships, aliases, and connections instantly across 361 intelligence data points.

Intelligence gathered

Strong Identifiers And Pivots

  • Exact full name is Ayham Tannous, and the LinkedIn public ID matches the supplied profile URL.
  • The profile lists Seattle, Washington, United States as the user location and Meta as the current employer.
Intelligence Gaps 2
  • No email address, phone number, or other direct contact point was provided.
  • No external corporate directory or public resume was supplied to independently confirm employment.

Weak Identifiers And Background Markers

  • The account has 468 followers and 466 connections, which is consistent with a long-established professional profile rather than a throwaway impersonation account.
  • The profile is marked verified and is not listed as creator or influencer.
Intelligence Gaps 2
  • No profile description/about text was available.
  • No public posts were observed, so voice, interests, and topical consistency cannot be assessed.

Account Attribution And Identity Linkage

  • Cross-platform person search produced a strong LinkedIn match with very high confidence for Ayham Tannous at Meta in Seattle.
  • The strongest alternative candidate is a Facebook profile for Ayham Tannous that also lists Seattle, but it lacks the employer/title corroboration seen on LinkedIn.
Intelligence Gaps 2
  • No mutual-contact graph or shared-endorsement evidence was provided.
  • No direct link from the LinkedIn profile to the secondary social accounts was observed.

Online Presence And Platform Activity

  • LinkedIn is the only clearly attributable profile in the evidence set.
  • The posts record shows zero LinkedIn posts, so there is no visible content history to review.
Intelligence Gaps 2
  • No activity metrics for Facebook, Instagram, X, or Pinterest were provided.
  • No engagement data, comments, or repost history was available.

Behavioral Markers And Preferences

  • The subject presents as a career-focused software engineer with a long tenure in major tech companies.
  • Career progression is linear: MTN, agencyQ, Computer Consultants Corporation, National Crash Analysis Center, Amazon, Expedia, then Meta.
Intelligence Gaps 2
  • No textual posts, comments, or recommendations were provided.
  • No skill endorsements or recommendation text was included in the evidence set.

Temporal Markers And Activity Windows

  • Current Meta employment began in August 2020 and was listed as 5 years 11 months at collection time.
  • The career timeline shows Amazon from March 2011 to December 2013 and Expedia from January 2014 to July 2020.
Intelligence Gaps 2
  • No precise account creation date was provided.
  • No active-hours or posting-window data was available.

Best next moves

Risks & recommendations

Identified Risks

3 risks

⤷ 3 additional risks found in this analysis

Impersonation risk

Unlikely

Low, but not zero. The strongest signals support a genuine professional profile, yet any public profile can be copied or lightly spoofed elsewhere.

Horizon: Near-term

Contact or identity confusion

Likely

Moderate risk that weaker same-name accounts could be mistaken for the primary subject during outreach or vetting.

Horizon: Near-term

Limited behavioral transparency

Almost certain

No posts means there is little public content to evaluate for opinions, consistency, or audience authenticity.

Horizon: Near-term

Recommendations

2 actions

⤷ 2 recommended courses of action

Confirm the LinkedIn profile as the primary identity anchor

3 steps

Use the LinkedIn profile as the baseline identity record for Ayham Tannous unless a stronger conflicting source appears.

Treat the LinkedIn URL as the canonical profile in internal records. Use the full name, Seattle location, and Meta employment as the first-pass match set. A conflicting employer or location appears.

Verify the Facebook candidate before attribution

3 steps

The Seattle-based Facebook profile is the best secondary candidate, but it should stay unconfirmed until additional evidence ties it to the LinkedIn subject.

Compare profile photos, mutual contacts, and any public workplace signals. Look for reused usernames, cross-posted images, or shared education details. A matching photo, employer, or school appears.

Data sources

Source Registry

5 sources
Source ID / Type Description Grading (Src/Info)
eval_1
social profile
LinkedIn profile record for Ayham Tannous
Coverage: Profile metadata, work history, education, verification status, location, and follower count
SRC A
INFO 1
eval_2
post
LinkedIn posts record for the same profile
Coverage: Observed post count and post presence
SRC A
INFO 1
eval_3
username search
Cross-platform social search results for Ayham Tannous
Coverage: Candidate accounts on LinkedIn, Facebook, Instagram, X, and Pinterest
SRC B
INFO 2
eval_4
reverse image
AI/deepfake image detection on the LinkedIn profile image
Coverage: Face detection and synthetic-image probability signals
SRC B
INFO 2
eval_5
people search
Person-focused social search match scoring
Coverage: Identity match confidence and competing candidates
SRC B
INFO 2

Follow Up Questions

Ask anything on 361 data points collected for Ayham Tannous.

Suggested questions

Click a card to ask

Who is most likely behind this LinkedIn profile?
Are there any signs this profile is fake or impersonated?
Which external accounts are most likely linked to Ayham Tannous?
What evidence best supports the Meta employment claim?
Analyst Briefing

Get answers grounded in the sourced data. Citations like will link to the evidence locker.

Evidence Locker
// Waiting for data ingestion...

Evidence Locked

This raw JSON payload contains sensitive intelligence data .

Unlock
361 data points collected