Skip to content

Commit 291254d

Browse files
remstosbgian
andauthored
Start adding Design Engineer Challenge (#6)
Co-authored-by: Bobby Giangeruso <hi@bobby.so>
1 parent 668421f commit 291254d

File tree

1 file changed

+59
-0
lines changed

1 file changed

+59
-0
lines changed

design-engineer/readme.md

Lines changed: 59 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,59 @@
1+
# Design Engineer Challenge
2+
3+
Welcome to the Heart Hands Design Engineer Challenge. We want to see your creativity, product instincts, strategic thinking, and technical skills in action.
4+
5+
This challenge is part of the hiring process for Design Engineers at [Heart Hands](https://hearthands.tech).
6+
7+
## Why this challenge?
8+
9+
We're a small, talented team seeking design engineers with strong technical abilities, product sense, and creativity. This challenge offers a glimpse into the impactful features we build and the challenges we tackle.
10+
11+
M1 is all about communication, and a key part of this is sharing call notes seamlessly across platforms. This challenge will test your ability to think beyond a single platform, delivering exceptional design and user experience while balancing functionality, strategic prioritization, and implementation.
12+
13+
We expect you to spend 4-6 hours on this challenge, simulating real-world, time-boxed work.
14+
15+
## Instructions
16+
17+
You are tasked with redesigning the call notes experience for the web, starting by designing the web view of a call note with sharing in mind.
18+
19+
### Requirements
20+
21+
- Write a proposal outlining your solution.
22+
- Include your designs in the document with a link to Figma.
23+
- Outline how you would measure success for your proposal.
24+
- Describe the next steps, challenges to build, and how you would start bringing the prototype to life.
25+
26+
> **Note:** Don’t feel tied to existing designs. While being aware of what exists is great for feature parity, we encourage creativity and introducing something new.
27+
28+
29+
## Context
30+
31+
After a phone call, voice note, or Google Meet, users receive a detailed summary inside the app. They often want to do more with it, especially sharing the notes link with other participants who don't have M1 installed.
32+
33+
Currently, call notes on the web offer the bare minimum. The native iOS view is far more advanced in terms of features, but once shared outside of M1, new users are left with a subpar experience, missing out on M1’s magic!
34+
35+
We see this as a great opportunity to bring new users to the app, give them a taste of M1 on the web, and drive virality, as sharing notes is key to relaying information.
36+
37+
## Bonus
38+
39+
Prototype with code: If you have ideas that are better expressed through code than a static prototype, let’s see them!
40+
41+
## Resources
42+
43+
We have prepared a Figma file containing some of our existing designs for you to copy or build upon!
44+
45+
[Open Figma](https://www.figma.com/design/LYHc8FzoYfAVo2tPdh9lc1/%5BStef%5D-Design-Engineer-Challenge?node-id=0-1&t=bPSKWg0mJOr1aq31-1)
46+
47+
<img width="1155" alt="Screenshot 2024-10-11 at 1 28 54 PM" src="https://github.com/user-attachments/assets/6b1a75d3-e578-4e5c-bf5c-f520108808f8">
48+
49+
50+
## Challenge Review
51+
52+
Here are some key points that will be considered during the review:
53+
54+
- **Storytelling:** Your ability to articulate ideas and present them in a way that excites people and helps them understand your proposal.
55+
- **Impact:** How would you measure success for this iteration? What data points would you look for after the release?
56+
- **Prioritization:** What trade-offs did you make, and how did they drive your focus? What would you do if you had more time?
57+
- **Evolution:** If the iteration performs well, how do you see the feature evolving? What theories or opinions does it help shape for you about the product?
58+
59+
Have fun building magic! 🌠

0 commit comments

Comments
 (0)