Slack Engineering

We build @SlackHQ.

[Slack Engineering @SlackEng]

A place for opportunities at Slack, blog posts about the engineering practice here, and other like-minded things. If you’re looking for product updates, you’ll need @slackhq, and for realtime information on service outages, @slackstatus. Platform updates are at @SlackAPI. Neato!

[Slack Engineering @SlackEng]

Learn how our team built a proactive defense mechanism to automatically identify threat behaviors and respond in real-time.

Instead of waiting days or hours for human intervention, the Anomaly Event Response responds in minutes.

https://t.co/Az3CMhj5Gm

[Javier Turégano @setoide]

How I felt in love with Slack and eventually got a job there. A story of overcoming failure and chasing your dreams. Featuring @jewelia @rands @iamcal @dustyp @krismerrill @tvars and my own family. https://t.co/bouvNxGmxq

[Frank @frankc]

What happens when your distributed service has challenges with stampeding herds of internal requests?
How do you prevent cascading failures between services?

We share how circuit breakers helped prevent internal cascading failures at @slackeng @SlackHQ!

https://t.co/YCrEpobgOQ

[Slack Engineering @SlackEng]

In case you missed it: Learn how @SlackHQ uses product thinking to improve our internal tools https://t.co/CzqqyICGI7

[𝙳𝚘𝚝𝚊𝚗 𝙷𝚘𝚛𝚘𝚟𝚒𝚝𝚜 @horovits]

a new research paper by Slack engineering outlines a #metrics storage engine that's better than @PrometheusIO. Check out OpenObservability Talks with @mansu to hear about it:
https://t.co/KTplv1MhIy
or on the podcast apps:
https://t.co/WnlBMrhmez
@SlackEng @OpenObserv #devops

[Frank @frankc]

🎉 @Carlos_vr_ and I share how @slackeng evolved socio-technical workflows to increase developer velocity and to redefine confident testing and deploy workflows.

https://t.co/QqggFQ0XHF

1/

[𝙳𝚘𝚝𝚊𝚗 𝙷𝚘𝚛𝚘𝚟𝚒𝚝𝚜 @horovits]

What does it take to build #observability in web-scale company such as @SlackHQ, @Pinterest & @Twitter?
Tune in to OpenObservability Talks @OpenObserv to hear it first hand from @mansu
@SlackEng @TwitterEng @PinterestEng

Live-streaming 16 Feb, 11 AM PST
https://t.co/DonvBRBXCi

[Slack Engineering @SlackEng]

“Building the Next Evolution of Cloud Networks at Slack: A Retrospective” from @SlackEng https://t.co/Dx2Gn3xTYF

[Frank @frankc]

🎉 https://t.co/XEkJ7tac0p

A deep dive on how we crafted an order of magnitude change in our spend (10x reduction compared to baseline growth) over the last two years with iterative understanding and changes in Slack’s Continuous Integration (CI) infrastructure. 1/

[LeadDev @TheLeadDev]

'As an organization grows, an engineering leader’s role in a company needs to transition' - @iamcal of @SlackEng

[Allan Leinwand @leinwand]

"The Four Agile Values and Slack" by Ashoke Chakrabarti @brianriggsbee Elizabeth Beddiaf. A great article by @slackeng! https://t.co/7AjmPYspGH

[LeadDev @TheLeadDev]

‘Your team care a lot more about technical debt when you are able to frame it in the terms of things that they care about’ - @QcMaude from @SlackEng

[Slack Engineering @SlackEng]

A well-designed API can boost developer innovation, while a poorly designed one can be a liability.

@episod and @saurabhsahni provide an inside look at our API design principles with some ideas that you can take back to your own process. https://t.co/GoT8FXnejA

[yenkel @yenkel]

Curious to learn how @SlackEng implements Role Management & Authorization and missed yesterday's @TwitterSpaces chat with @jakebyman and Aish Dahal?

Don't worry! Got you covered 🎉https://t.co/lup72i2UPt

[yenkel @yenkel]

1/ In the 2nd Authorization @TwitterSpaces chat
we'll learn how @SlackHQ designed, implemented and rolled out a big change at scale: their new authorization features

On Wed at 4:30 PM PDT I'll chat with @jakebyman & Aish Dahal, two @SlackHQEng engineers who worked on this

[Slack Engineering @SlackEng]

A decent number of Slack's features were once ideas and prototypes at our internal hackathon.

We've been running hackathons since 2016, learned a few things along the way, and wrote up 9 tips for throwing a successful (and fun!) one: https://t.co/SQy2Ek8qA3

[Slack Engineering @SlackEng]

Performance problems can be a real struggle to track down, especially if they're hard to reproduce.

We're using distributed tracing to understand work that spans multiple services and the client. Our colleague Justin wrote up how we're actually doing it: https://t.co/Zg79ZO2dXB

[Slack Engineering @SlackEng]

That high school student was @_clavin, now one of our @electronjs engineers!

[Stack Overflow @StackOverflow]

A high school student was submitting great PR’s to Slack’s open source projects. That turned into an internship and now, a full time job. https://t.co/AlCkLCPszP

[CNCF @CloudNativeFdn]

“Migrating Millions of Concurrent Websockets to ⁦@EnvoyProxy⁩” via ⁦@SlackEng⁩ https://t.co/XpeBz9jgZj