Bilawal Sidhu

Bilawal's writing style

Bilawal Sidhu writes in tight, declarative bursts: short opening sentences that announce an experiment or claim, then 1–3 follow-up lines that add technical context or a punchline. He frequently punctuates posts with one-line captions and single-sentence paragraphs — for example, "I built WorldView in three days." — then uses the next line to telescope into provenance or constraints: "But I also spent six years at Google ..." He favors concrete, technical nouns (Gemini 3.1, Claude 4.6, 3D, CGI, XR) and sprinkled hashtags (#3d #cgi #ai) rather than long connective exposition. Visual whitespace is deliberate: most posts are anchored by a hero image, GIF, or short video, followed by a 2–6 sentence caption that reads like release notes. Bilawal also slips in one-line declarative summaries mid-post — e.g., "AI can now create AND explore 3D worlds." — that read like experiment logbook entries. He occasionally embeds code-like fragments or hex references ("#e5e5e5") as shorthand for aesthetic or technical choices, and often closes with an invitation to comment or a short question aimed at peers rather than a broad call-to-action.

Who Bilawal writes for

Bilawal Sidhu is speaking to a mix of technical product builders and spatial-technology specialists: XR and 3D maps product managers (current and former Googlers feature in his signals), AI/ML engineers experimenting with generative models (evidenced by direct comparisons of Gemini 3.1 and Claude 4.6), and CGI/3D artists testing model outputs (#3d #cgi). He also targets founder-operators and startup investors tracking fast experiments — his bio lines (AI founder, CEO @ Intangible, ex-Google PM) and the pace of "built WorldView in three days" appeal to early-stage builders who value rapid prototyping. Career stage skews mid-senior: product leads, research engineers, and technical founders who can read short experiment write-ups and reproduce them. Secondary audience includes engaged tech-interested generalists who follow TED-curated talks; Bilawal frequently frames posts so these readers can grasp the headline claim before the technical details. Engagement metrics (dozens of comments) show he writes for peers who will reply with technical nitpicks, replication notes, or deployment questions.

Bilawal's signature hooks

1) The rapid-build brag-and-context opener. Example pattern: start with a one-line accomplishment, then immediately add experience as context. Paraphrase: "I built WorldView in three days. But I also spent six years at Google ..." This signals credibility plus speed. 2) The model-comparison experiment opener. Example pattern: name two models or versions and state the experiment intent in one sentence. Paraphrase: "Now that Gemini 3.1 and Claude 4.6 are both out, I wanted to see ..." This frames a head-to-head test and promises reproducible results. 3) The visual-narrative opener. Example pattern: lead with a striking descriptive caption about a demo or replay, then embed a 3D/CGI clip. Paraphrase: "God's eye view 24-hour replay of Operation Epic Fury." This invites curiosity and anchors the post in a cinematic visual. Bilawal repeats these three archetypes across posts: quick-build credibility, comparative model tests, and cinematic demo reveals, each designed to cue a different kind of reader (builders, evaluators, viewers).

Posting cadence and format mix

Bilawal posts a steady stream of short experiments and demos rather than long, infrequent essays. Indicators in the snippets show recurring, bite-sized updates: model comparisons when new releases drop (Gemini 3.1, Claude 4.6), rapid prototypes (WorldView built in three days), and visual replays or CGI showcases (#3d #cgi). He favors media-first posts: rendered images, short explainer videos, or interactive-looking 3D clips lead the post, with compact captions beneath. He uses hashtags consistently to categorize content but rarely publishes long-form technical deep dives; those few longer posts are the exception. Bilawal does more quick iteration posts and demo threads and less of multi-page LinkedIn articles or long personal narratives. Engagement numbers (tens of comments on several posts) suggest he posts often enough to sustain conversation around each experiment, likely multiple times per week when models or tools shift, and at least sporadically to highlight visual experiments outside of model-release cycles.

What to steal from Bilawal

Open with a one-line build claim and one line of provenance. Example: "I built X in Y days. But I also spent Z years at <relevant company>..." followed by 1–2 sentences explaining constraints. Start a model-comparison post by naming the versions and the test goal in one sentence. Example: "Now that ModelA vX and ModelB vY are out, I wanted to see how they handle <task>." Follow with two concrete test prompts and one result sentence. Anchor a demo post with a cinematic caption, then show the media. Example: "God's eye view 24-hour replay of <event>." Paste in the clip/image, then add one technical takeaway line. Use a short, bold declarative sentence mid-post as a thesis line. Example: "AI can now create AND explore 3D worlds." Then list two replicable steps or parameters (model name, seed, resolution) so readers can reproduce. Close with a single, specific question aimed at peers. Example: "If you run this at 512px with prompt X, what differences do you see?"