Back to @ujjwalscript's profile

Ujjwal Chadha engagement report

@ujjwalscript - 89K followers on X

Measured over 10 original posts from a 30-day window, last computed on September 24, 2026.

Engagement

Middle of its size range
Per follower
0.099%
of 89K followers
Per impression
1.03%
8.5K views on a typical post
Reach
9.55%
of its followers see a post
Typical post
88
interactions (median)
Saved
0.452%
38 bookmarks on a typical post
Posting rate
0.4/day
active 30% of days
Peak time
11:00 UTC
Wednesday

A typical post picks up 88 interactions against 89K followers, an engagement rate of 0.099%. Measured over 10 original posts, its engagement rate beats 51% of 26,733 tracked accounts of a similar size, which puts it in the middle of its size range rather than at either end. Posts are seen about 8.5K times each, and 1.03% of those impressions turn into an interaction. That is about 9.59% of the follower count, which is the gap between an audience on paper and an audience in a timeline. Posting runs at about 0.4 posts a day over the last 30 days, though only 30% of days saw any activity at all. Most posts go out around 11:00 UTC, and Wednesday is the busiest day of the week. The account's strongest tracked post pulled 5.1K interactions, about 58x its own typical post.

Measured over 10 original posts from a 30-day window, last computed on September 24, 2026.

Compared with accounts its own size

Ujjwal Chadha's engagement rate beats 51% of the tracked X accounts closest to it in follower count (26,733 accounts, accounts of similar size (decile 8 of 10)). A percentile is spread evenly by construction, so 50 really is the middle of that group and 90 really is its top tenth.

On engagement per impression rather than per follower it beats 41% of the same group. When those two numbers disagree, the gap is about how far its posts travel rather than how people react to them.

Where this sits in the catalog

At 0.099%, Ujjwal Chadha sits above the 25th percentile of the 268,215 accounts in this comparison. That places it in the below the median band, which runs 0.029% to 0.165%.

p100.004%
p250.029%
p50 (median)0.165%
p750.77%
p902.84%
p9974.6%
Engagement rate as a share of followers, across the 268,215 accounts we have scanned enough to measure. The axis is logarithmic, because the top and bottom of this population are about 17,764 times apart and a linear axis would flatten everything below the median into a single point.
Show the percentile table
Engagement rate percentiles
PercentileEngagement rate
10th percentile0.004%
25th percentile0.029%
50th percentile0.165%
75th percentile0.77%
90th percentile2.84%
99th percentile74.6%

This ruler is the whole measured catalog, not a size-matched group: it shows where the raw rate falls across every account we can measure, all of which are large. For a like-for-like comparison, read the size-band percentile above instead. See how the bands are built

Posting timing

This account posts most often around 11:00 UTC, and Wednesday is its busiest day of the week. The bars below are the catalog-wide pattern, with this account's own busiest slot marked. They do not show how this account performs at each hour: we keep one aggregate per account, not one per hour, so that measurement does not exist in our data.

Engagement by hour posted, UTCTwenty-four bars, one per UTC hour. Each bar shows how posts published in that hour compare with their own authors' median engagement. Bars above the centre line ran higher than the median, bars below ran lower. A marker flags Busiest hour: 11:00 UTC.
0003060912151821
Above the authors' own mediansBelowScale: plus or minus 111%Busiest hour: 11:00 UTC
Show engagement by hour posted, utc as a table
Engagement by hour posted, UTC
Hour (UTC)Vs author medianPosts
00:00 UTC-1%89K
01:00 UTC-2%90K
02:00 UTC-3%88K
03:00 UTC-4%94K
04:00 UTC-5%76K
05:00 UTC-4%75K
06:00 UTC-5%86K
07:00 UTC-5%93K
08:00 UTC-4%108K
09:00 UTC-4%124K
10:00 UTC-3%129K
11:00 UTC-3%141K
12:00 UTC-3%154K
13:00 UTC-3%167K
14:00 UTC-4%173K
15:00 UTC-2%176K
16:00 UTC-3%171K
17:00 UTC-3%159K
18:00 UTC-2%149K
19:00 UTC-2%141K
20:00 UTC-1%131K
21:00 UTC0%116K
22:00 UTC-2%100K
23:00 UTC-1%90K
Engagement by day of weekSeven bars, one per weekday, Sunday first. Each bar shows how posts published on that day compare with their own authors' median engagement. Bars above the centre line ran higher than the median, bars below ran lower. A marker flags Busiest day: Wednesday.
SunMonTueWedThuFriSat
Above the authors' own mediansBelowScale: plus or minus 111%Busiest day: Wednesday
Show engagement by day of week as a table
Engagement by day of week
DayVs author medianPosts
Sunday+5%393K
Monday+1%483K
Tuesday-2%520K
Wednesday-3%472K
Thursday-2%430K
Friday-3%447K
Saturday+2%393K
See what moves engagement across the whole catalogWhat counts as a good engagement rate at this size

Formats this account uses

Its own posting mix on the left, and what each of those formats does across every account we track on the right. Only formats where the effect clears our publish test appear here, so an empty row is a format we could not measure rather than one that does nothing.

This account's posting mix compared with catalog-wide effects
FormatThis accountCatalog effect95% intervalAccounts behind it
Image or video0% of posts+111%+108% to +115%34K
Outbound link0% of posts-41%-42% to -40%32K
Typical length-+15%+14% to +16%32K
  • 0% of this account's sampled posts carry an image or video. Across the catalog, posts with an image or video run 111% above the same accounts' other posts.
  • 0% of its posts carry a link off X. Across the catalog, posts with an outbound link run 41% below the same accounts' other posts.
  • Its average post runs 1161 characters, which falls in the over 280 characters band. Across the catalog, posts over 280 characters run 15% above the same accounts' other posts.

These are catalog-wide differences applied to this account's own posting mix, not a measurement of how each format performs for this account specifically. We keep one median per account, not one per format per account, so the second thing is not something this data can tell you.

Best tweets

  • Mar 13, 202658x their median

    Unpopular Opinion: We aren't building the future 10x faster with AI. We are just generating legacy code 10x faster. Everyone is currently bragging about developer velocity. "I built this entire backend in a weekend!" "AI wrote 80% of my codebase!" But here is the reality check we are ignoring: Code is a liability, not an asset. If an AI tool spits out 1,000 lines of functional boilerplate in five seconds, that is still 1,000 lines that a human being has to read, review, secure, and maintain when the dependencies inevitably break next year. We are treating code generation like a pure productivity win, but we are optimizing for the wrong metric. The bottleneck in software engineering was never how fast we could type. The bottleneck has always been comprehension, architecture, and maintenance. If we don't shift our focus from "generation speed" to "architectural sanity," the tech debt of the next five years is going to be an absolute, unmaintainable nightmare.

    4.1K522386107640K viewsView on X
  • Apr 26, 202624x their median

    Stories of vibe coded disasters piling up on Reddit Unless YOU intervene and build out a structure for AI, it is going to push slop. https://t.co/yXlYwYGrdS

    1.6K15425189232K viewsView on X
  • Jun 3, 202621x their median

    BREAKING: Ray Dalio just said the AI market is a bubble and it will burst. "All great technology changes produce bubbles," Dalio told Bloomberg. "The pricking is the converting of wealth into money" right now, every major tech company is pouring hundreds of billions into AI infrastructure and booking it as investment. The moment investors demand actual returns, companies will have to show that the money spent is generating real profits from real customers. If the revenue is not there, valuations collapse and right now, the revenue is not there. AI companies are spending $800 billion in capital expenditure this year alone. OpenAI spends $60 billion annually on cloud infrastructure against $25 billion in actual revenue. Less than 1% of executives globally report meaningful ROI from their AI investments. 95% of enterprise AI pilots have failed to deliver measurable returns according to MIT. The entire $2 trillion cloud backlog held by Microsoft, Oracle, Google, and Amazon is anchored by two unprofitable companies: OpenAI and Anthropic. By 2030, the industry needs $2 trillion in annual revenue to justify what is being built today. Bain estimates it will fall $800 billion short. Dalio is not saying the technology is fake. He is saying the economics do not work yet and every bubble in history has ended the same way when that moment of reckoning arrived.

    1.3K3551274299K viewsView on X
  • Mar 24, 202618x their median

    The "10x AI Developer" is a MASSIVE lie. You are just a 1x Developer generating 10x the technical debt. The entire tech industry is high on the illusion of "vibe coding" right now. The popular consensus is that because Claude and Devin can spin up a backend in 45 seconds, software is now infinitely cheaper to build. Here is the provocative reality nobody is budgeting for: AI is about to make software engineering significantly MORE expensive. Everyone is cheering for code generation, but completely ignoring the Verification Tax. When an AI agent writes 5,000 lines of code, it is optimizing to pass the immediate test. It is not optimizing for human readability. It relies on brute-force loops, repetitive logic, and bizarre architectural shortcuts that just happen to compile. Fast forward 12 months. Your business needs to pivot, or a core dependency breaks. You are now staring at a 50,000-line black box that no human being actually wrote, understands, or can safely modify. You cannot simply "prompt" your way out of architectural collapse. When the machine-generated spaghetti finally breaks, you won't be saved by a $20/month LLM subscription. You will have to hire a top-tier Principal Engineer at absolute premium rates just to untangle the mess your "autonomous swarm" created. We are treating code generation as a pure productivity win, but code is a liability, not an asset. Stop measuring how fast your team can generate syntax. Start measuring how quickly they can debug it.

    1.2K14819743116K viewsView on X
  • Apr 3, 202616x their median

    The “Vibe Coding” honeymoon is officially OVER. For a while, it felt magical. Prompt in, product out. No deep context, no architecture, no trade-offs. Just vibes. But reality is catching up: • Systems still need to scale
• Edge cases still exist
• Debugging still hurts
• And someone still has to own the code AI didn’t replace engineering, it amplified the gap between people who understand systems and people who don’t. “Vibe coding” is great for getting started.
But shipping real, reliable software? That still requires thinking. The engineers who win won’t be the ones who vibe the fastest - they’ll be the ones who understand what the vibe produced.

    1.1K8820826155K viewsView on X
  • Apr 13, 202612x their median

    Tech hiring isn't dead. You are just COMPLETELY unhireable right now. My timeline is developers crying that the market is frozen, the bubble burst, and AI took all the jobs. BUT from the hiring side of the table, engineering teams are desperate for talent. We just can't find anyone who actually knows how to build for the real world. Here is why your application is going straight to the trash in 2026: 1. The "Keyword Soup" Delusion: You list React, Python, Firebase, and 15 different LLM APIs on your profile. It just makes you look like a tutorial-follower with zero depth. Teams don't hire human tech-stack encyclopedias anymore, the AI does that. We hire problem solvers. 2. The "Agent" Obsession: Everyone wants to brag about building autonomous AI swarms and flashy generative UIs. Nobody wants to build a reliable Google Cloud Task Queue to actually process the asynchronous data at scale. The companies doing the heavy hiring right now need engineers to manage the unsexy, high-scale infrastructure, not prompt tinkerers. 3. Zero Business Context: You set up a slick CI/CD pipeline with GitHub Actions. Great. Did it reduce deployment time? Did it save the startup money? Did it unblock the sales team? If your career story doesn't connect your code directly to business revenue or efficiency, you aren't an engineer. You are just a typist. Stop blaming the macroeconomic conditions. Stop blaming AI. Fix your narrative. Show how you engineer actual value, and the interviews will follow.

    92264703143K viewsView on X
  • Mar 22, 20267.8x their median

    Your AI Agent is mathematically guaranteed to FAIL. This is the dirty secret the industry is hiding in 2026. Everyone on your timeline is currently bragging about their "Multi-Agent Swarms." Founders are acting like chaining five AI agents together is going to replace their entire engineering team overnight. Here is the reality check: It’s a mathematical illusion. Let’s look at the actual numbers. Say you have a state-of-the-art AI agent with an incredible 85% accuracy rate per action. In a vacuum, that sounds amazing. But an "autonomous" workflow isn't one action. It’s a chain. Read the ticket ➡️ Query the DB ➡️ Write the code ➡️ Run the test ➡️ Commit. Let's do the math on a 10-step process: $0.85^10= 0.19$ Your "revolutionary" autonomous system has a 19% success rate. And the real-world data proves it. Recent studies out of CMU this year show that the top frontier models are failing at over 70% of real-world, multi-step office tasks. We are officially in the era of "Agent Washing." Startups are rebranding complex, buggy software as "autonomous agents" to look cool, but they are ignoring the scariest part: AI fails silently. When traditional code breaks, it crashes and throws a stack trace. When an AI agent breaks, it doesn't crash. It just confidently hallucinates a fake database entry, sidesteps a broken API by faking the response, and keeps running—corrupting your data for weeks before you notice. If your "automated" system requires a senior engineer to spend three hours digging through prompt logs to figure out why the bot made a "creative decision," you didn't save any time. You just invented a highly expensive, unpredictable form of technical debt. Stop trying to build fully autonomous swarms to replace human judgment. Start building deterministic guardrails where AI is the engine, but the engineer holds the steering wheel

    449631542338K viewsView on X
  • Mar 27, 20267.7x their median

    "English is the new programming language" is largely BS. Everyone on X timeline is saying: "Just vibe code it! You don't need to learn syntax anymore, just prompt the AI in plain English!" HOT TAKE from the trenches of reviewing pull requests all day: English is the worst programming language ever invented. It is ambiguous. It is emotional. It lacks strict constraints. Code isn't hard because of the brackets or the syntax. Code is hard because of the precision. When you write in Python or React, you are forced to define the exact boundaries of reality. You have to explicitly handle the edge cases, the null states, and the architecture. When you write in "English", you are just hoping a probabilistic engine guesses your intent correctly. I am watching people use AI to "vibe code" entire backends in a weekend. The result? It functionally works for a demo, but it's an absolute disaster under the hood. No scalability, zero security considerations, and multiple responsibilities crammed into single, unmaintainable components. We aren't building the future 10x faster. We are just generating legacy spaghetti code 10x faster. The engineers getting promoted on my team right now aren't the best "prompt whisperers." They are the ones who know exactly why the AI's "English-to-Code" translation just introduced a silent memory leak into the system design. Stop learning how to "chat" with a bot. Start learning how to architect systems. Ambiguity is the enemy of scale.

    51967841135K viewsView on X
  • Mar 26, 20267.6x their median

    Be an AI Engineer in 2026. Learn this: 1. The Vector Stack: - Embeddings (Text-to-Vector) - Vector Databases (Storage) - Semantic vs. Hybrid Search 2. RAG & Context: - Advanced Retrieval (Reranking) - GraphRAG (Knowledge Graphs + Vectors) - Long-context window management 3. Pipelines & Orchestration: - Chaining (Deterministic flows) - Routing (Selecting the right model for the task) - Frameworks: LangChain / LlamaIndex 4. The Agentic Layer: - Tool Use (Search, APIs, Code Interpreters) - Planning Loops (Reasoning before acting) - Multi-Agent Orchestration (Swarms) 5. Evaluation & Testing: - Golden Datasets (Establishing Ground Truth) - LLM-as-a-Judge (Using strong models to grade weak ones) - Metrics: Faithfulness, Answer Relevance, Recall - Continuous Eval in CI/CD pipelines 6. Ops & Monitoring: - Tracing (Debugging the chain) - Cost & Latency optimization

    5678412236K viewsView on X
  • Jan 27, 20267.3x their median

    https://t.co/7fBKfLvCN6

    5427818373K viewsView on X

Ranked by total interactions across everything we have tracked for this account, which is a longer history than the 30-day window the rates above use. The multiple compares each post to this account's own median.

Buy or sell Twitter (X) accounts - escrow-protected

PlayerSells is an escrow marketplace for Twitter (X) accounts. Every deal is protected, with no middleman risk.

Reading these numbers

A typical post picks up 88 interactions against 89K followers, an engagement rate of 0.099%. Measured over 10 original posts, its engagement rate beats 51% of 26,733 tracked accounts of a similar size, which puts it in the middle of its size range rather than at either end. Posts are seen about 8.5K times each, and 1.03% of those impressions turn into an interaction. That is about 9.59% of the follower count, which is the gap between an audience on paper and an audience in a timeline. Posting runs at about 0.4 posts a day over the last 30 days, though only 30% of days saw any activity at all. Most posts go out around 11:00 UTC, and Wednesday is the busiest day of the week. The account's strongest tracked post pulled 5.1K interactions, about 58x its own typical post.

What is Ujjwal Chadha's engagement rate on X?
Ujjwal Chadha (@ujjwalscript) has an engagement rate of 0.099%, based on the median interactions across 10 original posts from the last 30 days against 88,716 followers. Replies, reposts and quote-posts of other people are excluded from that sample.
Is that a good engagement rate?
At 0.099%, Ujjwal Chadha sits above the 25th percentile of the 268,215 accounts in this comparison. Those comparison accounts are all large ones, because our scanning cadence is weighted towards big accounts, so this is a ranking among peers of similar scale rather than a ranking across X.
Does @ujjwalscript have real engagement?
Its engagement rate beats 51% of the tracked X accounts closest to it in follower count (26,733 accounts), which puts it in the middle of its size range group. Ranking inside a size band matters because engagement rate falls as accounts grow, so a raw rate would mostly re-measure the follower count. It is a starting point for a look at follower quality, not a verdict on it.
When does @ujjwalscript post?
Most posts go out around 11:00 UTC, and Wednesday is its busiest day, at roughly 0.4 posts per day across the measured window.

Keep going