Technical.ly is always looking for new voices to chronicle how tech companies and similar organizations are changing Philadelphia, Baltimore, D.C. and Delaware.
We also love to share the stories of the people behind that change. Some notable guest posts by community leaders we’ve published in recent months:
- “How can employers improve the job hunt? ‘Please just have some goddamn empathy’” (Philly) — Formerly unemployed QA engineer Rachel Drane has six suggestions for how to make hiring more humane
- “Prediction: 2019 will be the year for women of color in tech” (D.C.) — BEACON cofounder Aerica Shimizu Banks cites the recent rise in funding for WOC entrepreneurs as a main factor
- “What this advertising agency learned by opening a coffee shop in Locust Point” (Baltimore) — Planit cofounder Matt Doud on why his company opened Order & Chaos Coffee as a part of its new office
- “Why universities should push undergrads to intern sooner” (Delaware) — University of Delaware student James Massaquoi on how school can help more underclassmen get work experience
Here are 3 reasons to write for Technical.ly:
1. Share your expertise.
You know your organization, your job, your field better than most. What have you learned? What should others know? How can the sector improve, and what are some actionable steps to get there?
2. Spread the word.
We can only cover so much. Have a cool event coming up? Want to offer Technical.ly readers a discount to your program? There may be a chance your story will make it to print if you write it yourself. That said, your piece should still be interesting and insightful — tell us first why your event stands out. (Bonus points if it aligns with our editorial calendar!)
3. Change the narrative.
We’re particularly passionate about amplifying the voices of women, people of color and other underrepresented folks, so if that’s you, please reach out, even if you haven’t contributed professionally before.
Pitch us your ideas or just drop us a line letting us know you’re interested in writing for us and we’ll be in touch.