Posting on Twitter While Employed: Where the Lines Sit

Yes, you can post on X while you hold a job, and in Web3 most people who are good at their jobs do. The lines are simple to state: never post anything that isn't already public, follow your employer's social media and outside-work rules, don't speak for the company on news it hasn't spoken on, and treat "views are my own" as a courtesy to readers rather than a shield. Inside those lines, your lessons, your craft and your opinions about the industry are yours to share.

I've posted the whole way through employed roles. I wrote on X while I was at CoinMarketCap, where I led APAC partnerships and PR, and I still do now that I lead APAC PR and partnerships at Myosin. Nobody handed me a rulebook for it. What follows is the one I built by getting close to the line a few times and learning where it was.

Why post on X at all when you already have a job?

Because the job is temporary and the profile isn't.

Your title belongs to the company. When the role ends, the title goes with it, and so does most of the proof of what you did there. A public body of work stays with you. It's the thing a recruiter, a future client or a conference organiser reads after your name comes up.

I said a version of this during the layoff wave of early 2023.

To everyone that's working at a tech company, now is the time to start a side gig, up-skill and build your freelancing carrier! Shilika Jain on X, 20 Jan 2023

Posting is the cheapest version of that advice. It doesn't need your employer's budget or a second job. It needs you to write down what you're learning, carefully. If you want the job-search side of this, I've covered it separately in how visible work on X turns into Web3 roles.

What counts as confidential when you post about work?

More than people expect. In Web3, a lot of value sits in timing, so things that feel harmless can move markets or break trust. Treat all of these as off limits until they're public:

• Unannounced partnerships, integrations, listings or chain deployments
• Token dates, vesting schedules, airdrop criteria or snapshot timing
• Funding rounds, valuations and investor names before the announcement
• Internal metrics: revenue, user counts, retention, wallet numbers
• Client names you work with under NDA, or that haven't announced you
• Anything under embargo with a journalist, including hints that "something big drops Tuesday"
• Hiring, firing, restructuring and anything about named colleagues
• What a reporter or partner said to you in private

The embargo point catches PR and marketing people more than anyone. A teaser post before an embargo lifts can read to the reporter like a leak, and a broken embargo costs you the relationship, not just the story. I've written about the mechanics in embargo break risks in crypto PR.

A useful test: if a screenshot of your post would let someone trade, front-run, or scoop a story, it's confidential, whatever your contract says.

The traffic-light sort: what's safe, what needs a check, what's off limits

Before I post anything that touches work, I sort it into one of three colours. Green goes out. Amber waits for a check. Red doesn't get written.

The amber row is where most mistakes happen, because those posts feel like normal industry chatter. A sharp take on a rival's exploit is fine from an independent analyst. From someone at a competing protocol it reads as the company kicking a competitor while it's down, even if you meant it as a personal view.

Green is bigger than you think. "What I learned from running my first press tour across three Asian markets" needs no client name, no numbers and no permission. It's still useful, and it's still clearly yours.

How do you check your employer's social media policy?

Do it once, properly, at the start. It takes an afternoon and saves you an awkward call later.

1. Read the handbook or social media policy if one exists. Plenty of Web3 startups don't have one, which isn't the same as permission.
2. Read your contract for three clauses: confidentiality, outside work or "moonlighting", and IP ownership of content created during employment.
3. Check for disclosure rules on token holdings and trading if you're at an exchange, a fund or a market maker. These matter more than any social policy.
4. Send your manager or the comms lead a short written note: what you plan to post about, what you'll stay away from, and a request to flag anything they'd rather you avoided.
5. Save the reply. If a post is ever questioned, you can show you asked.

The contract step matters because side work is normal in this industry, and normal can make people careless.

ghostwriting & moonlighting are two common jobs in web3! Shilika Jain on X, 18 Oct 2022

Common doesn't mean cleared. If you're writing for others on the side, or posting content that promotes a paid side project, your contract may have something to say about it. Read it before your audience grows, not after.

How do you post about client work without breaking trust?

If you work at an agency or in PR, your best material is client work, and it's also the easiest place to overstep. My rule is that I only talk about outcomes that are already public, and I describe the method rather than the private details.

For example, I can say that RARI Foundation's Rari Chain mainnet launch landed in CoinDesk, The Block and Cointelegraph in the same week, because that coverage is public and I worked on it. I can say the angle was creator royalties protected at the chain level, because that's what the coverage itself said. I wouldn't post which reporters passed, what was said in pitch replies, or anything about the client's internal debate over timing.

A few habits keep this clean:

• Wait until the coverage or announcement is live before mentioning it.
• Credit the team, not just yourself. Client work is rarely one person.
• Ask the client before naming them if you're not sure they're comfortable being associated with you publicly.
• Turn specifics into principles. "One sharp angle beat five features" is shareable. The client's draft press release isn't.

Does "views are my own" in your bio protect you?

Only a little. It tells readers you're not the official channel. It doesn't change your contract, it doesn't stop a journalist quoting you as "an employee of X", and it won't help if you've posted something confidential.

So act as though your employer's name sits next to every post, because to anyone who checks your profile, it does. That doesn't mean you can't disagree with industry consensus. It means you argue the idea, not the people, and you don't argue about your own company in public.

The fear of being judged is real, and I've felt it.

stuck between can i really be myself on twitter and how will my OG crypto frens judge me about the crap that i'm posting on this bird app. Shilika Jain on X, 14 Apr 2023

What got me past it was separating two things: being myself, which is fine, and speaking for my employer, which isn't my job unless they ask. You can be candid about your own learning and still keep company matters off your timeline.

The four-question pre-post check

When a draft touches work and I'm not sure which colour it is, I run four questions. If any answer is no, it waits.

1. Is every fact in this post already public? Not "will be public soon". Public now.
2. Would I be comfortable if my manager and the client both read it tonight? Not "would they mind", but "would I be comfortable".
3. Am I talking about my craft, or speaking for the company? Craft is yours. Company positions belong to the company.
4. If this goes wrong, does deleting it fix it? On X, screenshots last longer than posts. If deleting wouldn't undo the damage, don't post.

This takes about thirty seconds and has stopped me from posting a few things I'd have regretted.

When these rules don't fit

Some roles need tighter limits than anything above. If you work in compliance, at a regulated exchange, at a fund, or anywhere that touches market-sensitive information daily, your firm's rules will be stricter and you should follow them over any general advice, including mine. The same goes for stealth-mode startups, where even saying who you work for can be sensitive.

There's also a cost to being careful: your posts get a little less specific, and specific posts travel further. I accept that trade. A slightly vaguer post that keeps your job and your clients' trust beats a viral one that costs you both.

If you're a founder rather than an employee, the rules flip. You set the policy, and your posts are company statements whether you like it or not. That's a different problem, and it's the one I work on through founder profiling.

FAQ

Should I tell my employer before I start posting on X?

You don't need permission to post about your own learning, but a short note to your manager is smart if your posts will touch your industry. It surfaces any concerns early and gives you a record that you asked. Most managers are happy to see a team member building a public profile, as long as company news stays with the company.

Can I post about looking for a new job while I'm still employed?

Avoid announcing it on X, since your employer, colleagues and clients all read the same feed. Let your work speak instead and handle the actual search through DMs and introductions. Updating your bio to say what you do, rather than where you work, is a quieter signal.

Is it okay to tag my company in my posts?

Tagging your employer on public good news, like a launch you worked on, is usually welcome. Avoid tagging them on opinions, debates or anything in the amber row, because a tag pulls the company into the conversation and puts your view in front of their audience as if it were theirs.

What should I do if I post something I shouldn't have?

Delete it quickly, then tell your manager or comms lead yourself before they hear it from someone else. Explain what was posted, how long it was up, and what you've done. Owning it early almost always goes better than hoping nobody noticed.

Want a second pair of eyes on how you show up on X without stepping on your employer's toes? Book a 30-min teardown with me.