Clubhouse | San Francisco or Remote (US) | https://www.clubhouse.com/jobs

We’re building Clubhouse, a new type of social network based on voice—where people around the world come together to talk, listen, tell stories, learn and hang out together in real-time. As a team, we take pride in being small and mighty, with a relentless focus on our product and the community.

We have raised our Series A, B and C, all led by a16z. We launched in 2020 and began 2021 with about 10 people. Today we’re a team of just over 100 people. We love building and shipping fast, and creating delightful experiences for all to enjoy.

Check out our team blog (https://blog.clubhouse.com/tag/technically-speaking/) if you’d like to hear from some of the engineering team on their current projects.

Here are a few of our open roles:

• Software Engineer, Android

• Software Engineer, Security

• Software Engineer, Infrastructure

• Product Designer

• Product Manager

If you’re interested, we’d love to talk :)

Fair point! The Clubhouse room about this goes into more technical depth: https://www.clubhouse.com/room/xe72WW1G

Clubhouse is using CPython

Interesting. Is there a reason for this?

It's the standard and best supported approach and the level of speedup you get from PyPy is significantly workload dependent.

I mean... it's the default?

Shameless plug here, but if you were using Hackpad for meeting notes, links, code snippets and other short work notes, you should give https://memo.ai a try!

We're building Memo, a note-taking app for technical teams. We integrate deeply with Slack which makes it super easy to save notes while in Slack, and you can write notes using both Markdown and Slack formatting (including @users, #channels and :emoji:).

We were recently on Hacker News and Product Hunt and got a ton of great feedback: https://news.ycombinator.com/item?id=14092279

Having been through an acquisition before, our plan is to build a sustainable business asap by charging for the product.

We haven't considered that so far since our focus is on technical teams at work, but it's an interesting idea

Sorry to hear, we are planning to add G Suite and GitHub sign-in soon.

If you'd like to get a better idea of the product you can check out the graphics in our Slack App Directory description: https://slack.com/apps/A0G9XHRE0-memo-notes-at-work

We also have more screenshots on our blog: https://blog.memo.ai/

Good question! We're focused on different use-cases (note-taking vs. project management), as well as a narrower niche (technical teams vs. any group of people, teams, families, etc.).

We use both Trello and Memo in our and the usage is quite complementary.

Do you use Trello for note-taking at work?

Consider developing an extension (browser), not sure if this is secure at all, but think how easy it would be to grab current tabs, highlight-get text from pages, etc... I've got this for myself but it sounds relevant to your app.

Again not sure about security though, but convenient. No need to switch to another tab while deep in the rabit hole of opening links.

Totally agree! A browser extension is on our roadmap, if you're interested to get early access to it I can add you to our "beta program".

Sorry, English is not my first language. What would be a better way to phrase it?

It's good English, but it's not transparent as to what future costs I might encounter if I start using the product while it's in beta, and want to continue using it in the future.

I'm happy to pay to use good software, but it's better to know the pricing plan in advance. I think that https://octopus.com/purchase provides a good example:

> Community edition is free for small teams, even for commercial use. It allows you to deploy up to five projects to up to ten target machines, and is limited to five users.

You're right, we could be more transparent about future pricing. It hadn't come up until now, we'll make sure to address it.

I think he wants to understand what your future pricing scheme will be before he commits to your system.

We're thinking $3-$5 per active user, but it's early days, so I can't say for sure ¯\_(ツ)_/¯

We'll also make sure early users don’t have to pay for a good chunk of time.

That's a good point! We used to have a video, but it was hard to maintain, but we should revisit that.

We have some different graphics in our Slack App Directory description: https://slack.com/apps/A0G9XHRE0-memo-notes-at-work - do you find these more helpful?

Those are helpful, but I think in addition to isolated screenshots I'd want to see full screen snaps of what the app looks like. This is to help me visualize it in context of my existing work environment/flow on the desktop.

It seems like there is a lot of interplay between participants too and I'd like to see how that works.

Just some cents on my initial reaction to seeing the product. Kudos though!

Thanks for the feedback, we'll look into recording the entire flow from Slack to web app. In the meantime, I don't have a better alternative than signing up :)

Why not?

It seems like an arbitrary sso to offer as the only option.

Got it. One of the differentiators of Memo is the deep Slack integration, for example with the recently launched Message Menus: https://blog.memo.ai/10x-your-slack-apps-ux-with-message-men...

We plan to offer G Suite and GitHub sign-in soon.

Slack accounts are separate for each team you join. A lot of people join a handful of public and private teams. This means we have to create an account each time?

For now, yes. We've noticed that quite a few Slack users have multiple teams, but most of them have just one team in which they spend 80% of their time (usually it's their work team).

We're also planning to add other team logins (G Suite & GitHub) and we also expect Slack to improve the experience for users with multiple teams.

Why not normal username+password authentication?

We're focusing the product on "teams" (technical teams more specifically), so signing in with your "team identity" (Slack, G Suite, GitHub, etc.) helps power all the collaborative features (@-mentioning, sharing, etc.)