Career & Leadership › Career Growth

Writing and Speaking Publicly

Blogs, talks and sharing what you learn.

Writing or speaking publicly is one way to share what you have learned with people outside your immediate team. A post, talk, or tutorial can clarify your own thinking, help others solve a similar problem, and make your work easier to find.

Choose a topic you can explain accurately from experience. For example, describe how your team found and fixed a migration issue, including constraints and lessons, without exposing customer data or confidential architecture. Separate what you observed from advice that may not apply elsewhere. A small, practical explanation is often more useful than trying to make every piece definitive.

Public communication takes preparation and carries risk. Check employer policies, permissions, and confidentiality obligations; get approval for company-specific details where needed. Do not publish security-sensitive findings before the responsible disclosure process is complete. You can also write anonymously or contribute to community documentation if public attribution is not appropriate.

Backend engineers might explain a migration constraint or an operational lesson. Frontend engineers can share an accessibility fix or a state-management trade-off. Data engineers might describe a validation approach that caught a silent failure. Keep examples small and reproducible, and note what did not transfer to other contexts. Start with an internal review or a short community post, and treat audience questions as material for the next revision.

Speaking and writing are skills that improve through feedback, not a requirement for career advancement. Decide what you want from the effort and choose a format that fits. See presenting, writing culture, and career conversations.