Hiring: engineers for the mobile web app

Even shipping it behind a flag would let us validate the approach. We hit this every Monday during the weekly review.

What changes

It would let us retire an internal tool nobody wants to maintain. Happy to test a beta build if that helps. We are working around it with a spreadsheet, which is not sustainable.

1. Enable vote weighting.
2. Enable an audit log.
3. Enable MRR-weighted prioritisation.

Before you start

This has come up in three separate customer calls this month. We would move our whole team over if this landed. Even shipping it behind a flag would let us validate the approach.

1. Enable multi-language content.
2. Enable an audit log.
3. Enable webhook retries.

Next steps

We raised this during the pilot and it is still the main gap. Two people on the team have independently asked for this.

1. Enable multi-language content.
2. Enable custom domains.

Step by step

Customers ask about this on nearly every onboarding call. Right now this costs us roughly two hours a week.

1. Enable dark mode.
2. Enable reaction emoji.
3. Enable CSV export.

How it works

It was the first thing our new hires tripped over. This has come up in three separate customer calls this month. We hit this every Monday during the weekly review.

1. Enable a Linear two-way sync.
2. Enable webhook retries.
3. Enable MRR-weighted prioritisation.

curl -sS https://api.example.test/v2/items \
  -H "Authorization: Bearer $BULLETIN_API_KEY"