dsyang

Notion | https://notion.com | Android Engineer | SF | hybrid (in office 2x a week) | Full time

  Level: All levels (at least 2yrs of experience shipping production Android apps)
  Salary: $130,000 - $250,000 + equity
  Hiring Process:  Recruiter call -> Practical tech screen -> 1-2 practical coding/1 system design/1 career history -> post onsite -> reference checks -> offer

Notion’s looking for more android engineers to join our Mobile Product pod and help us build more high-quality, mobile-first experiences. Our Android app began as a shell that ran the web app in a webview that we’ve increasingly ported to Kotlin and Compose. This greatly improved app performance[1] and has unlocked the potential for more delightful mobile UX. Some example projects you might work on include: making Notion AI actually useful on mobile, making it dramatically faster to view notion pages, and building more mobile-native integrations to help our users be productive on-the-go.

Role details available at https://job-boards.greenhouse.io/notion/jobs/6151801003

Feel free to email me if interested. I can submit internal referrals to fastrack the appliation: dan [at] makenotion [dot] com

Notion | https://notion.so | Android Engineer | SF | hybrid (in office 2x a week) | Full time

  Level: Mid/Mid+ (4-6yrs experience)
  Salary: $130,000 - $250,000 + equity
  Hiring Process:  Recruiter call -> Initial screen -> 1-2 coding/1 system design/1 career history -> post onsite with staff -> reference checks -> offer

(Shared in October, the position is still open!)

Notion’s looking for an android engineer to join our Mobile Product pod and help us build more high-quality, mobile-first experiences. Our Android app began as a shell that ran the web app in a webview that we’ve increasingly ported to Kotlin and Compose. This greatly improved app performance[1] and has unlocked the potential for more delightful mobile UX. Help us make this a reality! Role details available at https://job-boards.greenhouse.io/notion/jobs/6151801003

Feel free to email me if interested. I can submit internal referrals to fastrack the appliation: dan [at] makenotion [dot] com

[1] https://www.notion.com/blog/notion-on-android-is-now-more-th...

Notion | https://notion.so | Android Engineer | SF | hybrid (in office 2x a week) | Full time

  Level: Mid/Mid+ (4-6yrs experience)
  Salary: $130,000 - $250,000 + equity
  Hiring Process:  Recruiter call -> Initial screen -> 1-2 coding/1 system design/1 career history -> post onsite with staff -> reference checks -> offer

Notion’s looking for an android engineer to join our Mobile Product pod and help us build more high-quality, mobile-first experiences. Notion’s Android app began as a shell that ran the web app in a webview that we’ve increasingly ported to Kotlin and Compose. This greatly improved app performance[1] and has unlocked the potential for more delightful mobile UX. Help us make this a reality!

Role details available at https://job-boards.greenhouse.io/notion/jobs/6151801003

Feel free to email me with any questions: dan [at] makenotion [dot] com

[1] https://www.notion.so/blog/notion-on-android-is-now-more-tha...

Having experienced all three types of judging formats as a hacker, I honestly enjoyed the Demo-athon types the best.

The most exciting part of a hackathon is seeing what other hackers have made and that's almost impossible when you're stuck at your table demoing. Especially if you're a solo hacker or a key member of the team.

The expo-style format may be the most scalable, but there's also a ton of room for improvement. I distinctly remember a hackathon (MHacks maybe?) where none of the sponsor judges came to see my app. Another time I overheard judges prioritized tables that had the most twitter mentions, turning the expo into a social network popularity contest of sorts.

Its exciting to see hackathons trying to solve the demo problem, and I'm really glad someone put together a guide, but I think the ideal judging format has yet to be found.

Thanks for your answer sharemywin! What if you were looking at a large project that doesn't have a well-defined "beginning?" How would you pick what code to run through the debugger first?

Thanks for your answer! Your approach sounds like it works well if you have to write a new component from scratch. What if you had to jump into an existing codebase? How would you go about understanding the code?

What do you mean when you say compare it to what you see? How do you take the files and lines of code you read and model it into a working architecture? Where do you start? Do you think we could write a program that can make this process easier? (also, thanks for your answer!)

Thanks for the answer! It sounds like you're taking a bottom-up approach when reading code. Do you think we can use software to build this dependency graph and make it easier to read code?

Thanks! It was great meeting you guys too and congrats!

EDIT: Since I can't change the submission title. It's an SMS autoresponder app. Let your phone text for you when you can't!

Here's a video describing the app: http://www.youtube.com/watch?v=ZI9p5txM0Sg

Same thing happened to me. No confirmation e-mail yet...