Contents — press Esc to close

    Walmart Global Tech · strategy plan

    GitHub strategy for
    engineering reputation
    & employer brand

    Turning WGT's public engineering work into a curated, credible proof layer — for developers, candidates and the wider tech community.

    The legal story

    The contents of this document are the sole and exclusive property of Zensciences. They may not be disclosed to any third party or at any party, copied, reproduced in any form or matter or used for any purpose, other than that for which they were provided, without the written permission of Zensciences.

    All rights reserved.
    © Zensciences 2026

    What GitHub is & why it matters

    What GitHub is

    GitHub is the world’s largest software collaboration platform, where engineering teams store, document and collaborate on software projects. It serves as a public portfolio and a critical credibility signal.

    GitHub is where developers evaluate how organizations build software — not just what they build.

    01
    Public portfolio
    Makes engineering work visible to developers, candidates and industry peers through repositories, documentation and project history.
    02
    Collaboration platform
    Enables internal and external developers to co-create, participate and contribute productively.
    03
    Reputation signal
    Creates measurable proof of engineering quality, technical depth and open collaboration that strengthens employer credibility.

    What GitHub is & why it matters

    The nine signals developers actually read

    ← → through the signals · 1–9 to jump

    walmartlabs / lacinia Public v1.2.2 · SemVer

    GraphQL implementation in pure Clojure. The README carries purpose, install, schema definition, query execution and a full tutorial.

    Clojure 1,863 stars 167 forks 10 open issues Pull requests SECURITY.md · CLA

    Anatomy of a real WGT repository — live walmartlabs/lacinia figures

    What GitHub is & why it matters

    Why GitHub matters for WGT

    As Walmart evolves into an AI-native, platform-driven technology organization, GitHub can serve as the public proof of that transformation. It showcases WGT’s engineering across AI, cloud, APIs and retail-scale systems, making its technical excellence visible to developers, candidates and the broader tech community.

    The shift

    A stronger GitHub presence turns a code repository into an engineering reputation asset.

    Walmart Global Tech on GitHub

    353 followers · 115 repositories · pinned projects in Clojure, Java and JavaScript.

    Benchmarking

    How leading companies build technical reputation

    Positioning — the elite profiles open with a stated point of view, not a repository list.

    Microsoft — open source narrative

    Frames open source around a clear, flexible identity — and tells developers exactly how to get involved.

    Netflix — engineering at scale

    Ties open source directly to scale, cloud reliability and speed of delivery.

    Netflix — technical depth

    Transparently explains hard engineering problems and guides community participation into them.

    Click any screenshot to enlarge

    Benchmarking

    What an elite engineering profile looks like

    Pinned projects, plain-language READMEs and visible activity are what convert a visit into credibility.

    Pinned repositories

    Recognizable, high-impact repositories surfaced first, each with a clear description and hard signals.

    README quality

    Shopify states project purpose, active status and contribution needs in plain language — including when a project is no longer maintained.

    Active signals

    Discussions, contributors and stars are what establish hard engineering credibility — dormant repos read as abandoned.

    Benchmarking · beyond the repository

    The repository is the proof — the channel and the route to a role are what convert it

    Live

    Screenshots captured 11 August 2026. Post selection illustrates format, not performance. Chapter 3 loads live from Instagram and needs a network connection.

    ← → story · 1–5 jump

    Benchmarking · case study

    Target — how open source became a talent strategy

    Target has published no before/after perception study. The recruitment and retention benefits are Target’s own stated claims — the GitHub figures are independently verifiable.

    ← → story · 1–6 jump

    WGT GitHub audit

    Where WGT stands

    01
    Visibility
    Public engineering work is already visible. Multiple projects represent real developer investment and provide a baseline content foundation.
    02
    Technical scale
    Projects span high-interest engineering fields — modern API integrations, microservices orchestration, cloud deployments and complex retail and supply-chain engines.
    03
    Credibility
    WGT has clear internal proof points for robust systems engineering. The opportunity is to present them so they are discoverable, understandable and trusted externally.

    The profile as it stands today

    WGT GitHub audit

    What is limiting us

    01
    Presentation
    Pinned repositories are not clearly aligned to WGT’s larger technology story.
    02
    Documentation
    READMEs, descriptions, tags and project-status signals are inconsistent across repositories.
    03
    Engagement
    External audiences lack clarity on which projects are active, supported or open for discussion.
    04
    Storytelling
    GitHub activity is not connected to social spotlights, careers pages or campus initiatives.
    Opportunity

    WGT already has the engineering credibility. The opportunity is to package, curate and amplify that work so GitHub becomes a visible proof point of Walmart Global Tech’s engineering reputation.

    GitHub potential

    Targeted outcomes

    Reputation
    Each outcome feeds the next — and creates proof points for storytelling.
    Reputation building
    Engineering-first reputationTechnical credibilityDeveloper trustEmployer brand authenticityTop talent attraction

    Campaign strategy

    The reputation journey

    Campaign objective

    Use GitHub to make WGT’s engineering work more visible, understandable and credible — while building internal participation and creating stronger employer-brand stories.

    Engineersbuild the culture.
    →
    GitHubshows the work.
    →
    Employer brandingtells the story.
    Narrative today

    A retail company with a tech office.

    →
    Narrative earned

    A technology-led organization building at global scale.

    Phase-wise approach

    Engineering reputation is built progressively — not launched as a campaign

    Reputationaccumulated across the phases, not created in the last one
    Build
    Prove
    Pull

    WGT must first activate its engineering culture, then make credible proof visible, and finally convert that proof into technology prestige and talent interest.

    How to read the next three phases

    Each phase inherits what the previous one created. The bar at the foot of every screen stays lit for the phases already completed.

    Phase 01 — Culture & Capability

    Reputation begins inside the engineering culture

    Before WGT communicates externally, it must enable engineers to participate, contribute and build credible GitHub assets.

    Explore Phase 1 →

    Phase 01 · architecture

    Phase 1 builds both the culture to participate and the infrastructure to sustain it

    Workstream A

    Activate the engineering culture

    Create awareness, participation, ownership and recognition internally.

    • Leadership narrative and GitHub ambition launch
    • Onboarding, learning sessions and contribution guides
    • GitHub Champions and project nominations
    • Maintainer recognition, showcases and awards

    Workstream B

    Build the GitHub foundation

    Establish repositories, standards, governance and contribution systems.

    • Audit and prioritise the repository portfolio
    • README, contribution and security standards
    • Repository owners, maintainers and review paths
    • InnerSource-to-open-source pipeline
    Shared Phase 1 outcome

    An activated engineering community and a GitHub portfolio ready to be seen. Neither workstream delivers it alone.

    Phase 01 · activate the engineering culture

    Engineers need a reason, a route and recognition for participating

    01 · Inspire

    The reason

    • Leadership narrative
    • Engineering town halls
    • GitHub ambition launch

    02 · Enable

    The route

    • Onboarding
    • Learning sessions
    • Contribution guides
    • Team toolkits

    03 · Mobilise

    The movement

    • GitHub Champions
    • Project nominations
    • Internal contribution sprints

    04 · Recognise

    The reward

    • Maintainer recognition
    • Showcases and awards
    • Leadership amplification

    Hero programme

    WGT GitHub Champions

    Mobilises teams

    Identifies projects and stories

    Supports contributors

    Connects engineers with communications

    Sustains momentum across locations and functions

    Phase 01 · build the GitHub foundation

    Culture becomes credible only when participation produces strong engineering assets

    01 · Curate

    Audit & prioritise

    • Audit repositories
    • Prioritise flagship assets
    • Archive unsupported projects

    02 · Standardise

    READMEs & guides

    • README standards
    • Contribution guidelines
    • Security policies
    • Documentation

    03 · Govern

    Owners & review

    • Repository owners
    • Maintainer roles
    • Legal and security review
    • Response standards

    04 · Prepare

    Ready to be seen

    • InnerSource pipeline
    • Open-source readiness
    • Measurement framework
    • Release plans

    Repository readiness — 25%. The portfolio deliberately gets smaller, not larger.

    97 → 60

    Phase 01 · outcome

    Phase 1 creates an activated engineering community and a GitHub portfolio ready to be seen

    Active GitHub Champions network
    Identified maintainers and repository owners
    Prioritised flagship repositories
    Common contribution and documentation standards
    InnerSource-to-open-source pipeline
    Initial engineering stories and advocates
    Reputation asset bank — carried into Phase 2
    ChampionsMaintainersFlagship reposStandardsPipelineStories

    Phase 02 — Proof & Participation

    Engineering activity must now become visible proof

    WGT uses the culture, champions and repositories created internally to begin earning credibility within the external developer ecosystem.

    Carried in from Phase 1
    ChampionsMaintainersFlagship reposStandardsPipeline

    Explore Phase 2 →

    Phase 02 · architecture

    Phase 2 develops GitHub further while beginning proof-led external communication

    Workstream A · the action

    Activate GitHub externally

    Create releases, contribution pathways and developer participation.

    • Flagship repositories and public roadmaps
    • Good-first issues and contribution weeks
    • Maintainer office hours and community sessions
    →

    Workstream B · the telling

    Communicate the proof

    Make engineers, repositories and technical activity visible.

    • Release and launch content
    • Maintainer and contributor stories
    • Technical explainers, RFCs and engineering blogs
    • Channel architecture, cadence and ownership
    The governing principle

    Every communication output traces back to a genuine GitHub action. Proof first, communication second.

    Phase 02 · activate GitHub externally

    WGT moves from maintaining repositories to creating developer participation

    01

    Discover

    Flagship repositories, project pages, clear roadmaps.

    02

    Understand

    Documentation, demos, technical explainers.

    03

    Contribute

    Good-first issues, contribution weeks, challenges.

    04

    Connect

    Maintainer office hours, community sessions, university cohorts.

    05

    Belong

    Repeat contributors, external reviewers, contributor recognition.

    Each rung is a deeper degree of external participation — cumulative, not a list of tactics

    Phase 02 · communicate the proof

    External communication starts by showing the work — not making broad technology claims

    Code

    Repository launches

    People

    Meet the Maintainer

    Thinking

    Technical explainers

    Participation

    Office hours & challenges

    v1.2.2 release notes and migration guide

    Source · release

    “Ten good-first issues” contribution call

    Source · repository

    New tool announcement with a working demo

    Source · repository

    Meet the maintainer behind lacinia

    Source · maintainer

    GitHub Champion spotlight series

    Source · contributor

    First-contribution story from a new joiner

    Source · contributor

    Why we rebuilt the schema layer

    Source · maintainer

    Architecture decision record, made public

    Source · repository

    RFC opened for community comment

    Source · repository

    Monthly maintainer office hours

    Source · maintainer

    Campus contribution challenge

    Source · repository

    Community session on retail-scale systems

    Source · release

    Phase 02 · communicate the proof

    Start from the channel, not from the story

    Each channel answers a different question and demands a different cut. Content planned backwards from the channel survives contact with a developer audience. Content adapted forwards from a press release does not.

    ChannelThe question it answersNative formatCut from
    01 · GitHubIs this real?Release notes, README, public roadmap, good-first issuesthe commit
    02 · Engineering blogIs it hard?Explainers, architecture decision records, RFCs, post-mortemsthe maintainer’s reasoning
    03 · LinkedInWho built it — and could I work with them?Carousel breakdowns, maintainer profiles, leadership posts, role linksthe person
    04 · Short-form videoIs this a place worth watching?30–60 second reels, screen demos, build-in-public clipsthe demo
    05 · Long-form videoCan I watch someone actually build this?Talks, demos, recorded office hours, deep divesthe session
    06 · Community & eventsWould they have me?Office hours, contribution weeks, campus challenges, meetupsthe invitation
    The discipline

    No asset is written once and pushed everywhere. One engineering action produces one source of truth on GitHub and five native cuts — the pattern Microsoft Developer runs when it answers a GitHub release with a reel rather than a link to one.

    Phase 02 · outcome

    WGT begins earning technology credibility through visible engineering proof and external participation

    Active flagship repositories
    Consistent releases and public roadmaps
    External contributors and developer interaction
    Recognisable engineering voices
    Proof-led content library
    Initial community and ecosystem credibility
    Reputation asset bank — carried into Phase 3
    ChampionsMaintainersFlagship reposStandardsPipelineStoriesReleasesContributorsEngineering voicesContent libraryChannel mixCommunity credibility

    Phase 03 — Prestige & Pull

    Visible proof now becomes technology prestige — and talent pull

    WGT scales its earned engineering credibility into employer-brand consideration, developer interest and stronger access to relevant talent.

    Explore Phase 3 →

    Phase 03 · architecture

    Phase 3 scales engineering reputation and converts it into measurable talent interest

    Workstream A

    Scale technology prestige

    Build broader recognition across talent, media and the technology ecosystem.

    • Owned engineering campaigns and the annual Built This Year film
    • Conferences, meetups and university partnerships
    • Developer media, technology stories and expert recognition
    • Maintainer, contributor and alumni advocacy

    Workstream B

    Convert prestige into interest

    Connect engineering proof with teams, careers and candidate pathways.

    • Repository-to-role mapping and careers integration
    • Code Behind the Career stories
    • Talent communities by technology domain
    • Contributor-to-candidate pathways and interest tracking

    Phase 03 · scale technology prestige

    GitHub proof gives WGT the credibility to enter larger technology conversations

    GitHub proof

    Owned

    Our platforms

    Built This Year, engineering campaigns, leadership content.

    Community

    Where developers are

    Conferences, meetups, university partnerships, ecosystem programmes.

    Earned

    What others say

    Developer media, technology stories, awards, expert recognition.

    Advocacy

    Who speaks for us

    Maintainers, contributors, alumni and engineering leaders amplifying WGT.

    Each arena is only enterable because the proof from Phases 1 and 2 already exists

    Phase 03 · convert prestige into pull

    Candidates can move directly from discovering WGT’s engineering to exploring a career

    Discovers code

    →

    Explores engineers

    →

    Understands the work

    →

    Finds relevant roles

    →

    Expresses interest

    What has to be true

    None of this happens on its own. Three things have to be true. Every project we put in front of people has to say who builds it and whether that team is hiring. Anyone already helping out — using our code, reporting problems, suggesting fixes — should be invited to apply, not cold-approached six months later. And we have to count how many people reach us this way, because that number is the only proof the whole thing worked.

    Phase 03 · the annual moment

    Built This Year

    It’s a GitHub Wrapped — or a YouTube Rewind for engineering. Once a year, WGT publishes what its engineers actually built.

    How much got built
    How many projects were opened, how many updates shipped, how many problems fixed.
    Who built it
    How many engineers took part, how many teams, how many did it for the first time.
    Who joined in from outside
    How many people outside Walmart used WGT’s code, improved it or reported problems — and where in the world they were.
    What travelled furthest
    The biggest launch of the year, the most-used project, the one that improved most.
    The people of the year
    Champions, first-time contributors, and the engineer whose work reached the most people.
    And the reason it matters

    It gives the whole programme a cadence — something to build towards every year, the same way Wrapped gives Spotify a December.

    Operational governance

    Who owns what, phase by phase

    PhaseWGT ownsZensciences owns
    Phase 1 — Culture & CapabilityEngineer participation, repository quality, Champions, security and legal reviewProgramme design, internal narrative, recognition formats
    Phase 2 — Proof & ParticipationReleases, maintainers, responding to issues and contributionsChannel architecture, content production, editorial standards
    Phase 3 — Prestige & PullRoles, careers pages, recruiter enablementCampaigns, earned media, Built This Year
    Always onSecurity, legal, IP and what can be publishedMeasurement and reporting

    Campaign roadmap

    The programme, month by month

    PhaseMonthsDone when
    Phase 1 — Culture & Capability1–3Champions named, flagship repositories chosen, standards published and signed off.
    Phase 2 — Proof & Participation4–8Repositories shipping regular updates, outside contributors arriving, content running across the channel mix.
    Phase 3 — Prestige & Pull9–12Careers pages connected to real projects, first outside coverage earned, applicants arriving through GitHub being counted.
    Built This Year12The year’s work published.
    Retail RewiredWe Got ThisBuilt by Walmart

    Walmart Global Tech × Zensciences

    To new beginnings.