1/ Been thinking a lot about the interview process lately (@MorningBrew is hiring). I’ve helped not only grow the company over the last 18 months, but specifically the Rev Org from 3 to 30. Here are a few things from my experience that can hopefully help others 🧵👇 (1/18)
- Show you care and feel this is more than a “job” - paint a picture and tell a story.
- Prove your writing skills and communication ability - great communicators are essentially in just about any role...there’s an opportunity to stand out here from the start.
1) Why Morning Brew? I want to hear about your understanding and passion for the company. How long have you been a subscriber? What’s a great headline, story or ad that made you smile? What made you decide to apply for a career here?
2) Why this role? I want to understand what drives and motivates you to do the thing you’re applying to do, irrespective of the company. I want to see, hear and feel your career path and trajectory.
3) Why this role at Morning Brew / Why are you uniquely qualified for this role at Morning Brew? This is your opportunity to show you’ve done your research on the company and understand the specific role’s function inside of the specific company.
4) Why now? How you got to the app or interview. Did your friend share the JD? Were you actively searching for a new oppty? Do you check our jobs website? What makes this point in time special? There’s a diff btwn running towards a new oppty and running from an old one.
You May Also Like
A brief analysis and comparison of the CSS for Twitter's PWA vs Twitter's legacy desktop website. The difference is dramatic and I'll touch on some reasons why.
Legacy site *downloads* ~630 KB CSS per theme and writing direction.
6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices
https://t.co/qyl4Bt1i5x
PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.
735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices
https://t.co/w7oNG5KUkJ
The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.
The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.
Legacy site *downloads* ~630 KB CSS per theme and writing direction.
6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices
https://t.co/qyl4Bt1i5x

PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.
735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices
https://t.co/w7oNG5KUkJ

The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.
The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.