Building in Public Without Burning Your Employer: A Guide for African Professionals

Somewhere in Lagos right now, a product manager is drafting a LinkedIn post about a feature she shipped. She wants the credit, the inbound recruiter messages, the speaking invite. She also does not want a Monday-morning conversation with Legal about the internal churn numbers she almost pasted into the caption. That tension, between visibility and self-sabotage, is the whole game. Building in public is one of the highest-return career moves an employed professional can make in 2026. It is also one of the easiest to get catastrophically wrong.

The good news: the line between "career capital" and "career-limiting move" is not mysterious. It is mostly about what you share, whose data it touches, and whether you have read your own contract. This is a practical guide, not legal advice, and where your employment terms are involved you should confirm specifics with a qualified professional in your jurisdiction.

Why building in public is worth the effort

Traditional networking is capped by time and geography. A great conversation at a Yaba meetup reaches the handful of people in the room. Publishing does not have that ceiling. The real shift is discoverability: opportunities arise not because someone applied for a role or pitched a service, but because their content made them visible to the right people. For African professionals competing for global remote roles and senior local moves, that visibility compounds in three ways.

• Inbound instead of cold applications. Recruiters, founders and journalists search for people who demonstrate expertise publicly. A consistent feed turns you from an applicant into someone who gets approached. It pairs so well with a properly optimised LinkedIn profile.

• The warm-introduction effect. By the time a hiring manager reaches out, they already know how you think and communicate. This is also how LinkedIn quietly becomes a job pipeline without you ever pressing "Easy Apply."

• Career insurance. A restructuring, a funding winter, a sudden layoff. When your network already sees your work, your next move starts from a warm audience rather than a cold CV. Building in public is insurance you pay for in small weekly instalments.

The upside is real. So is the downside, which is why most people either overshare or, more commonly, freeze and post nothing for years.

The real risks, named honestly

Being fired for a post is not a hypothetical. Documented cases include a new employee dismissed after a selfie revealed confidential company documents in the background, an HR manager fired for posting job applicants' resumes with mocking comments, and a nurse dismissed for posting about a patient's diagnosis even without naming them. None of these people set out to leak anything. They just posted without thinking about who else was in the frame.

For an employed builder, the risks cluster into five buckets:

• Confidentiality breaches. Customer data, unreleased products, internal metrics, deal terms, security details. Most employment contracts bind you to secrecy, and these duties can survive even after you leave.

• Intellectual property. Work you produce on the job usually belongs to your employer. IP-assignment clauses mean the code, designs and decks you create at work are typically the company's to publish, not yours.

• Social media policy violations. Many companies have explicit rules about disclosing affiliation, speaking "on behalf of" the firm, or posting during work hours.

• Looking like a flight risk. A feed that reads like an open job hunt can quietly cost you the stretch project or the promotion.

• Clients and colleagues seeing it. Your post does not stay in your bubble. The client you subtweeted, the peer you vented about, are two taps from your content.

What you can and cannot share

Here is the working rule that keeps builders safe: share the lesson, not the leak. The generalised insight is yours. The specific, identifying, internal detail is not. Almost every good "build in public" post is a lesson wearing the costume of a story, with the confidential parts filed off.

Do share

• Skills, frameworks and mental models you have developed ("how I structure a discovery call").

• Publicly released work, once it is genuinely public, with credit to the team.

• Your own learning journey, mistakes and reflections.

• Industry commentary, trends and things you are reading.

• Anonymised, generalised lessons where no real person, client or number is identifiable.

Do not share

• Customer or user data. Names, faces, account details, screenshots with real records. Ever.

• Unreleased work. Roadmaps, features, launches, pricing, or the deal that has not closed.

• Internal metrics. Revenue, churn, CAC, headcount plans, board slides, dashboards.

• Trash-talk about your employer, boss, clients or colleagues. It reads as a red flag to every future employer. If you are wrestling with a difficult colleague, handle it through the channels covered in handling conflict with a peer at work, not in a caption.

The reframe: "We cut onboarding drop-off by 40% last quarter" is a leak (internal metric, specific to your employer). "Three onboarding mistakes I keep seeing, and how I'd fix each" is a lesson. Same expertise, none of the exposure.

Read your contract and the company policy first

Before you post anything about your work, spend twenty minutes doing what most people never do: actually read the documents you signed. Look specifically for:

• The confidentiality / NDA clause. What counts as "confidential information," and does the duty continue after employment?

• The IP-assignment clause. Does it claim everything you create during employment, or only work "related to the business"? This decides whether your side project is even yours.

• Any social media or communications policy. Look for rules on disclosing your employer, moonlighting, and posting during work hours.

• Non-disparagement and non-compete terms, which shape what you can say and build on the side.

If you cannot find a policy, that absence is itself information: ask HR for the current version rather than assuming permission.

Getting buy-in from your manager

The single most underused move is the boring one: tell your manager what you are doing before they hear about it from someone else. Most managers are glad to have a visible, credible team member, because your reputation reflects on them too.

Script (the heads-up): "I've started writing on LinkedIn about [my craft], to sharpen my thinking and grow in the field. I'll keep it strictly to general lessons, nothing about our customers, numbers, or unreleased work. Is there anything on your radar you'd want me to steer clear of?"

Script (asking to feature company work): "The [X] we shipped is public now. I'd love to write about my part in it and credit the team. Can I run the draft past you before it goes up?"

That last line, offering to show the draft, does most of the work. If you do not yet have that relationship to lean on, this is exactly the kind of thing a good mentor helps with; here is how to find a mentor as an African professional.

Personal brand versus employer-branded content

Keep a clean line between two modes. Personal content is your voice, your lessons, your career, and it travels with you when you leave. Employer-branded content speaks for the company, ideally coordinated with marketing, and stays with them. One practical habit: make clear when you speak for yourself, not the organisation. A simple "views are my own" in your bio helps, but it is not a magic shield; behaviour matters more than a disclaimer. Build the personal brand as the durable asset, and do not let your feed become an unpaid extension of the company's marketing, or you leave with nothing that is yours.

What to do if your employer objects

• Ask for specifics. "Thanks for flagging. Can you tell me exactly which part is the concern so I can fix it?" Often it is one detail, not the whole activity.

• Comply quickly on the specific post, especially anything touching confidentiality. Speed here buys enormous goodwill.

• Separate the post from the practice. Ask whether the objection is to that content or to your posting at all, and get the boundary in writing.

• Know your floor. In many jurisdictions there are protections for discussing pay and working conditions collectively, but these are narrow and local. If a dispute escalates, get advice specific to your country.

Handled maturely, an objection can actually strengthen trust. You have shown you take the company's interests seriously, which makes the next "yes" easier.

The summary

Building in public is not reckless if you do it deliberately. Read your contract and policy. Give your manager a heads-up. Share lessons, frameworks and released work; never customer data, unreleased projects, internal numbers, or complaints about the people who sign your cheques. Keep your personal brand separate from your employer's, because one is your asset and one is theirs. Do that, and the audience you build becomes leverage, inbound and insurance, all without a Monday summons to Legal. A strong feed also makes the other career levers easier, including getting referred for roles by people who already know your work.

FAQ

Can my Nigerian employer really fire me for a LinkedIn post?

Yes, particularly where a post breaches confidentiality, an IP clause, or a social media policy you agreed to. Documented cases include people dismissed for leaking documents in the background of a photo. This is general information, not legal advice; check your specific contract and local law.

Do I need my manager's permission to post about my industry?

Not usually for general industry commentary and your own lessons. You do need coordination before posting anything about your specific company's work, customers, metrics, or unreleased products. A quick heads-up costs nothing and prevents most problems.

What if there is no social media policy at my company?

Treat the absence as a prompt to ask HR, not as permission. Default to the "share the lesson, not the leak" rule, and confirm anything company-specific with your manager before it goes live.

Should I put "views are my own" in my bio?

It helps signal that you speak for yourself, but it is not a legal shield. What actually protects you is not posting confidential information and not disparaging your employer, regardless of what your bio says.