Use case
Office Worker for engineers and technical teams
- From:
- Hesham Barr, founder
- Published:
- Updated:
The problem: technical people often avoid professional feeds altogether. Between hype posts, "10 AI tools you need" lists and recruiters who haven't read your profile, there is little left worth reading.
How engineers use Office Worker
- Write the post-mortem. "Our queue backed up for six hours. Here's why, and what we changed." Real incidents, real fixes.
- Compare approaches. "How are you handling database migrations with zero downtime on a small team?" gets answers from people running real systems.
- Skip the hype. Posts that are all buzzwords and no substance tend to get caught by the check. See how to spot AI-generated posts.
- Avoid recruiter noise. There is no cold-message inbox to fill.
A typical week
A backend engineer posts a short memo on why her team moved off a managed queue service, with the numbers. Engineers at three other companies reply with their own experience, one with a warning she hadn't considered. It reads like a good internal engineering channel, except across companies.
What makes it different
Everyone is verified with a work email, so you know replies come from working engineers. And because the feed is not ranked by reactions, a dry, detailed memo isn't buried by a viral one-liner.
Ready to try it?
Join with your work email and write up the last thing that broke and how you fixed it. Read what a work-only network looks like for the house rules.
Frequently asked questions
- Can I post code or technical detail?
- Yes. Technical detail is welcome, as long as you are not sharing anything your employer would consider confidential.
- Will recruiters spam me?
- Office Worker is built around public memos and replies, not a cold-message inbox, so there is no channel for mass recruiter messages.