Posting Patterns & Frequency

6.0 posts/week

Posts / Week

1.4 days

Days Between Posts

Total Posts Analyzed

HIGH

Posting Frequency

Timezone: Europe/London

Best Performing Days

ThursdayFridayTuesday

Best Performing Times To Post

Late morning to early afternoon (around 12:20–12:40 local time)

Topics & Content Focus

Primary Topics

Practical software engineering craft and refactoring at scaleEngineering culture, psychological safety, and blameless incident responseIC leadership without formal titles and senior engineer behaviour patternsNon-linear software engineering career progression and mindsetAI-assisted development and the future of the '10x engineer'

Secondary Themes

On-call ownership and production incident managementTeam collaboration, mentorship, and knowledge sharingTechnical judgment, decision-making, and tradeoffs under pressureTechnical debt, legacy code, and long-term system healthContinuous learning, curiosity, and self-directed growth in tech

Industry Focus

Big Tech cloud infrastructure and platform engineering (AWS context)Backend and systems-oriented software engineering in large organizationsProfessional software engineers and aspiring senior/Big Tech ICs

Content Categories

Tactical how-to playbooks (e.g., refactoring principles and habits)Culture and values storytelling from inside Big TechCareer narrative and mindset reframes for engineersShort, humorous or meme-style posts about engineering status tropesCredibility-building posts anchored in personal Amazon/AWS experience

Performance Insights

777%

Avg Engagement Rate

STABLE

Performance Trend

Best Performing Topics

Humorous future-of-engineering/10x engineer commentaryDeeply tactical refactoring and code-quality principles from real-world experienceBlameless culture and how strong engineering teams handle incidents

Virality Signals

High share counts on posts that articulate aspirational team cultures (blameless, trust-based)Above-average likes and comments when combining Big Tech credibility with tactical listsHumorous, extremely short posts that tap into well-known engineering archetypes (e.g., '10x engineer')Stronger traction when CTAs explicitly invite saving, reposting, or contributing additional lessonsUse of relatable, high-pressure scenarios (on-call, production outages) that many engineers recognize

Structure & Quality

180

Avg Length (Words)

HIGH

Depth Level

ADVANCED

Expertise Level

8/10

Uniqueness Score

Common Hooks

Status-challenging statements that reframe what it means to be 'senior' or '10x'Big Tech authority hooks (e.g., 'Amazon taught me...', 'I'm a Software Engineer at AWS')Personal journey intros that normalize non-traditional paths into software engineeringNumbered list promises with strong constraints (e.g., '18 lessons in 60 seconds')Direct, second-person statements that speak to the reader's insecurity or ambition

Common Endings

A distilled moral about culture, leadership, or growthEncouragement to readers who feel behind or underqualifiedSubtle self-positioning as an ongoing resource for 'practical software engineering tips'Open-ended prompts or questions to invite additions from the audienceExplicit social actions: save, repost if it resonates, or follow

Value Delivery Methods

Concrete, field-tested principles engineers can apply immediately (e.g., how to refactor safely)Shift in how readers think about seniority, leadership, and culture in engineering teamsNormalization of imperfect, non-linear career paths to reduce impostor syndromeProcess-level insights into how high-performing teams operate under pressureExplicit codification of tacit knowledge (judgment, habits, team behaviours) usually learned slowly over years

Formatting Style

Short, single-sentence lines separated by line breaks for rhythm and emphasisArrow bullets (→) for behaviours, principles, and checklistsNumbered lists for structured advice-heavy postsStandalone one-liner conclusions for punchy takeawaysLight use of emojis for tone (e.g., 😂) while keeping content mostly professionalUse of --- separators to visually distinguish body from CTAsConsistent use of niche hashtag (#softwareengineering) to anchor audience

Audience & Tone

YES

Question Usage

0.5%

Response Rate

Detected Tone

Relatable Big Tech insiderCalm, process-oriented mentorCulture-first engineering leader in IC clothingPractical, no-drama problem solverAspirational yet grounded guide for early and mid-career engineerssemi-formalfirst-person

Interaction Style

Invites readers to contribute their own lessons or experiences to extend the postUses empathy and shared struggle to create a 'we're in this together' dynamicPositions self as an approachable mentor rather than distant expertLeverages socially loaded prompts ('Repost if this resonates') to signal belongingAppeals to both ambition (becoming senior/10x) and safety (blameless culture, supportive teams)

Community Building Signals

Repeatedly emphasizing practical tips to become better engineers, reinforcing a learning-focused communityHighlighting supportive cultures and mentorship as norms to aspire to and recreateSharing personal vulnerability around mistakes and non-traditional paths to foster psychological safetyEncouraging ongoing dialogue through 'What would you add?' style prompts that validate audience expertise

Writing Style Patterns

Content Strategy

Hook: Status-challenging statements that reframe what it means to Tone: semi-formalCTA: Follow CTAs tied to a clear value promise ('practi

Abdirahman Jama

Performance Overview