---
# System prepended metadata

title: 08/05/2021
tags: [0x]

---

---
tags: 0x
---

---
# 08/05/2021
What I would be responsible for:
- reviewing submissions
- sourcing candidates


# 07/22/2021

## Review Applicants

https://docs.google.com/spreadsheets/d/1yrry0-XLwSzbuvp9bqKihKy2hMhr1hTOxBEwvKpCGD4/edit#gid=930950146


Fulvia Likes:
```
Already devrel
Digital content
Software Eng
Likes education, sharing knowledge
Research
Working with other people

Cons:
Timezone
```

Brent
```
Michelle F


Cons:
If they care so badly about their title
```

Both open to timezones:
Most EU/US timezones
After covid, will this person be

Content creation aspect: 


## Iterative:

---

# 07/14/2021

:::info
- **Start Date:** March 17, 2021
- **Agenda**
1. Onboarding
2. Community
3. Sucess
4. Tasks
- **Participants:**
    - Brent Oshiro - community and ecosystem growth, devs wanting to build, Matcha
    - Clay Robbins - growth for 0x Labs and Matcha, product marketing
    - **Fulvia Morales** - Taker team PM, related to 0x API 

- **Contact:** 

- **Reference:** - [Last week meeting minute](/s/template-meeting-note)

:::
# Week 12 - 05/20/2021

## What we're looking for in a developer Advocate

```
Expectations:
Project management and organizational skill
Main owner of dev advocacy
Can own the role and work independently

Capable of:
Create a plan around dev advocacy, vision that makes sense specifically for 0x
Execute a plan

Soft-skills:
Coordinate with integration engineer
Coordinate and understand leadership vision, capabilties, have leadership buy-in
Can establish early-on the importance of dev advocacy, must advocate and over-communicated upfront

Context:
Non-technical role has to come in and teach why a non-technical role is important

currently, the current devrel need was ID by product, community, labs, 
```

### What is the team currently responsible for:
- After the awarness part of the funnel, 1 to many work, devrel comes next in the funnel
- Office Hours, hackathons,
- Engagement/retention part of the funnel 
- being the voice of the developer, internally
    - Moving Disord Qs into dev docs
- getting back to people, responding in the API channel, technical Qs
- Working with Fulvia and other engineering team that Qs are answered
- Internal devrel processes
- What are we doing today, what's tomorrow's best process
- Community devrel events such as hackathon
- Technical tutorials, collab with Brent on video content
- API academy, api docs, product marketing
- keeping tabs on projects building on 0x (you can see when an experiment turns into a real project ), the dev advocate can move them along the funnel like a pre-sales engineer

Questions:
- managing?
- for the integration manager into the engineering manager, under the API/Jacob Evans
- dev rel owner of many products vs one product vs many types of dev profiles
- does the DAO fall under Dev Advocacy? (community Brent?)

Context
- product marketing manager responsible for user acquisition, they are creating case studies, awareness, engaged

## Next Step:
tailor the the role and filter the activities down to 0x 



# Week 11 - 05/20/2021

**Initiative 1 - Technical Office Hours**
Community-lead office hours? 
    - logistics, API tech stack
    - always same community participants

**Initiative 2 - Developer Advocate Lead**
[:link: Target List](https://docs.google.com/spreadsheets/d/1yrry0-XLwSzbuvp9bqKihKy2hMhr1hTOxBEwvKpCGD4/edit?usp=sharing)


**Ideas:** (potential first initatives)
hackathon w/only teams that have built on 0x - just show up
Flex the 0x ecosystem
    workshop-basic, more advanced. Get the community involved

**Next steps:** reaching out to dev adv

**Next meeting **
May 27th - what we're looking for in a dev advocate
June 3rd - what initiatives we want them to accomplish

# Week 10 - 05/13/2021
---

**Initiative 1 - Technical Office Hours**
What worked/didn't work?

Logistics
* only 2 devs showed up! > email a reminder prior to meeting
* Fulvia’s internet was slow
* this is a very expensive hour > need people to commit to show up or have less engineers, hard to scale though

Content
* there were a couple of Mesh Qs (that ended up not being about Mesh) but we don’t have any Mesh engineers
* devs searching reference documentation took up time. This won’t scale well with more people joining > breakout rooms? ask for more info about problems/questions in advance?
* More advanced recon on issues that will be asked would be helpful > add to form?

Options:
1. Office Hours Trial 2
2. Discontinue

Questions: 
- Documents, how are they organized?
- 

Next Steps for OH:
- must meet registration quorum, or is canceled for that day. Ie if 4/5 registrants show up, incentive to follow-through
- form to presubmit questions, but prework may defeat the purpose

**Initiative 2 - Recruiting Developer Advocate Lead**
- Intro to Blueprint


Pain-points:
Discord support turns into 


**Desired:**
Scope for Beginner 0x Journey
Promotional levels for Beginners, 
Graduate through 

Next Steps:
- proposal for Beginner 0x Journey
- Sync with Blueprint


**Unknown**
The beginners, bring them back and promote
Who are falling off
# Week 9 - 05/04/2021
---

Check-in

**Initiative 1 - Technical Office Hours**
- what worked/didn't work?

**Initiative 2 - Recruiting Developer Advocate Lead**
- will get introduced to Blueprint

**Priorities:**
Integration engineer prioritized (API PM role) before dev advocacy

# Week 8 - 04/28/2021
---
**Initiative 1 - Technical Office Hours**
https://hackmd.io/lTCBZJi1TdCVzvzTzb9T4w?view
POC: Fulvia, Brent

[Sign-up Sheet](https://docs.google.com/forms/d/e/1FAIpQLSdqadutRYTBkNrAfm4BG08u_FcmhUfXGSeT0wdeROyaXfD1Rw/viewform)

1. Address Scale
![](https://i.imgur.com/ynWNnbp.png)

2. Needs
![](https://i.imgur.com/a9Amtci.png)

<br>

:star: **Metrics for Success** :star:
Does this reduce staff time in community support?
How to measure: https://forms.gle/GEyHE8GdRfySqBWT9
Measure at start and end 
Fulvia to send to Xianny and Lawrence

:::warning
Interruption factor
Not everyone is good at support
Inefficient use of resources

*What is the current open source contribution to code maintenance
:::

---

**Initiative 2 - Recruiting Developer Advocate Lead**
https://hackmd.io/cuF8aDbLRzu8wEPkdMnCcQ?view
POC: Zack, Clay

```
Schedule
May 2 Phone Interview
May 9 Take home
May 16 Onsite Interviews
May 23 Buffer
May 30 Onboarding/First Deliverable hand-over

```

:star: **Metrics for Success** :star:
Will this hire take-over developer advocacy initiatives

How to measure: Onboard candidate who has built out developer advocacy

:x: Blockers

intro me to Zack via Discord

:dart: Next Steps

Sydney - pause 1 week until recruiting firm
1. Assist in recruiting Dev Advocacy
2. Outbound to 50 developer advocates to interview
3. Review inbound application
4. Onboarding Clay, Brent

Each member (Brent, Fulvia, Clay, Sydney):
- In each respective team: Provide links, documentation, initiatives that you need to handover
- I'll designate which part of the developer funnel the dev advocate will take over
- Fulvia share integration engineer role
- Fulvia share metric survey for Tech Office Hours
- Onboard Brent and Clay

---

# Week 7 - 04/23/2021

:mag: Let's Go Over
---

**Initiative 1 - Technical Office Hours**
https://hackmd.io/lTCBZJi1TdCVzvzTzb9T4w?view
POC: Fulvia, Brent

**Purpose:** Streamline staff engineer's schedules for technical community support

**Schedule**
Friday, May 7, 2021
Friday, May 21, 2021
Friday, June 4, 2021

:memo: Needed :memo: 
- Announcement needs to be made
- Which channels?

---
**Initiative 2 - Recruiting Developer Advocate Lead**
https://hackmd.io/cuF8aDbLRzu8wEPkdMnCcQ?view
POC: Zack, Clay


**Purpose:** Developer Advocate needed to address community and bandwidth pain-points

**Process**
Phase 1: Interview Developer Advocate Lead hires
Phase 2: Onboarding by handing over Developer Advocate responsibilities
Phase 3: Launch first deliverable which is scaling community support to alleviate bandwidth restraints from 0x staff

:memo: Working On :memo: 
- take home assessments designed for developer advocate

:dart: Next Steps
---
---
# Week 6 - 

```
Interview process 

Phone Internview
Take-home projects (Skills assesment)
    - Position 0x API to users
Onsite Interviews
    - Will & Amir (Founders) to talk about values
Unique
    - Role related onsite
    - small presentation to people on the team whatever they want to present on (previous projects relevant to the job)
    - does this person have mastery, can they demo that
    - how they handle Q&A and speak to different levels of sophistication (15-30min)



Engineering Interview
High-level Qs
Potentially technical interviews

```

Dev Rel
Skills
Audience
Personality/Values:
Cultural Check:
Key: Metrics

Three Qs:
Phone - fundamental skills, Good Qs
Skills Assesment 
On-site

cc-clay

Wants help with:
- interviewing
- creating documentation for take-home

JD
https://docs.google.com/document/d/1FhRt1OqOaXjTUAlWc0GippZC2YKQZ55K3harijy_ovw/edit?usp=sharing

:::

# Week 5 - 04/12/2021
```
Today's agenda:
1. Technical Office Hours
2. Weekly Dev Advocacy meetings
3. JD
4. Recruiting Process
5. MVP Program
```

:closed_book: Tasks To Review
--

**Schedule Office Hours** (Fulvia)
- Xianny
- Lawrence

```
1. Create a message to your community that you will now be hosting Office Hours, post that messaging in the relevant channels. 
Who: 0x engineering team
What: Office Hours
When: Day, Date, Timezone
Where: Zoom/Discord
Why: What kind of help can the community get by attending OH

2. Start with 3 sessions to gauge interest, so next is to sync Google Calendars with Xianny and Lawrence (if you have an internal EA for scheduling, use that) of the next upcoming sessions. Should be the same time for the next 3 sessions

3. Optional (depends on privacy needs of your community): can send a sign-up/RSVP form via Zoom (link to learn more) unless you are hosting your Office Hours on Discord (your community lives there). Zoom is easier for breakout rooms and side-chats (which does not exist on Discord)
```
 
**Schedule internal weekly meetings** (Brent)
- Thursdays at 4PM PT(?) review bandwidth concerns


:mag: Let's Go Over
---

**JD** [[LINK]](https://docs.google.com/document/d/1FhRt1OqOaXjTUAlWc0GippZC2YKQZ55K3harijy_ovw/edit#heading=h.2rgo99u8zmhu)

- 80/20, community vs documentation
- experience
- profiles: OSS ethos, vetting what can the candidate bring to the table
- MVP program

**Recruiting process**
- inbound (timeline )
- outbound ( )
- Market-rate comps (geography, cost of living), points of reference

**MVP program** - distributing bandwidth
(Is Head of Advocacy adopting this? Did not see in JD)

Actions
- take on community calls
- enlist recruiting help (MVP)
- technical writers
- promote/coordinate/TA technical office hours (MVP)

Incentive Creation
Weekly Roadmap

:dart: Next Steps
---
Double check with Fulvia on Technical Office Hours
Clay/Brent - intro me to the recruiter, Zach

Next Initiatives 
Recruiting, coordinate with Zach
Technical Office Hours

```
Reference URLs
https://www.youtube.com/playlist?list=PLN51Tjs40v5Oh2oZNLtbN6CnVpH-xKKbI
https://github.com/0xProject/pm
https://gov.0x.org/c/schedule/20
```


# Week 4

Next Steps

**Internal**
Technical Office Hours
Dev Advocacy Stand-up

**External**
Recruiting
MVP Program

Presented on:
https://docs.google.com/presentation/d/1EQjQDL7WH3G6rR4TpV8rgVQmSGxv-70Gaw-mEV0X7lw/edit?usp=sharing

___

# Week 2 - 3

![](https://i.imgur.com/JJM0TLx.png)

```
Programming Q2-Q3

- revamp dev docs (requires band)
- internal developer experience for internal team (address band)
- experience and content (requires band)
- more content focused on success usecases  (requires band)
- 
```
Easy: organization
Difficults with hackathon: high touch dev walking around and helping


Question
1. new hire internal
2. devs in the community
3. ourselves consistently

Prioritize
1. ourselves - content (extends the technical band restraints)* limited *, internal dev exp tools and staging are in good shape 
- give back function
- internal allocates time
- eng drowned with development

2. new hires - clay
3. devs the community

Bandwidth
-
- logistics: who is responsible for what 
- process: dev advocacy stand-up, 
- share progress, roadmap and devs in the ecosystem (governance call)

** Prioritized shipping as internal dev tool - our value proposition
Trade-off: dev experience go down the drain 

## Next Steps
- bandwidth, dev advocacy
- missing resources, clay lobby for this resource, what are other dev tools are doing for the (master organizer/orchestrator)
https://www.youtube.com/watch?v=IkYBlc8iuKI&list=PLN51Tjs40v5Oh2oZNLtbN6CnVpH-xKKbI&index=2

**What have we accomplished today:**
The four of us have become the weekly dev advocacy stand-up to address developer funnel pain-points
It has become clear that beyond all the pain-points, bandwidth restraints is the next immediate fix that needs to be address, to prevent the funnel from leaking
Next week you'll have a clear list of options of what we will need to tackle
I'll showcase how other teams deal with Bandwidth constraints

```
Prioritizing how to fix Bandwidth:
1. Internal Options
- streamline community technical office hours
- weekly dev advocacy standup

2. External Options
- recruiting for building techincal trainers and MVPs (OutSystems, Google)

3. Community Options
- incentivizing community to be educators (Polkadot)
```

What's next to be delivered:
- pitch of various dev rel teams and their structures
- 



---
# Week 1

## Expectations

Identify leaks
Implement new strategy


## Onboarding 

```
Week 1-2: Onboarding and Initial Strategy Assessment 
- 0x shares relevant information to map out developer funnel proposal
- Consistent communication for any additional, missing, and follow-up information

Week 3: Stakeholder buy-in
- Drafting dev funnel proposal
- Outreach to internal customers to approve or counter strategic direction

Week 4: Direction approval
- Scheduling deliverables and assigning points-of-contact
- Collaborating with the marketing team on a shared message

Month 2: Building the developer funnel
- Managing existing and building net-new assets and programming
- Fixing and preventing churn in the user journey 

Month 3: Launch
- Directing distribution channels to funnel
- Proper offboarding and hand over 

```

:books: Study the Community
---

### What is working

```
Discord - top of funnel works really well. 

Discord is the platform to catch and engage the devs.

technical-help

API help has an idea in mind

Defi Academy - teams to work with

Well organized, users seem to know where to go

Brent most proud of: content, blog consistency

Reddit - more general audience

Converting web2 devs to web3
```
:question: 
Should we centralize all the devs or decentralize them across platforms? 

### What is not working
```
 1. [PROCESS] who/why/how did they join, when a dev reaches discord, we don't know where they came from, what are they looking for
 2. [LOGISTICS] bandwidth, limited resources, same eng building the product is helping the devs in the community
 3. [PROCESS] docs with starter guides, some are outdated, some Qs are very basic, as if no one even read the documentation
     -our technical docs - current engineers are the technical writers
 4. [LOGISTICS] Support functions broken: we have devs coming from multiple channels, how do we fix it, as if devs go to the most sense, set up a private channel on Telegram 
     - have not directed to specific channel for support, some niche questions are private, needs for private & public channels
     - chat is not support for scale, issue tracker
**our customers are our users, we need to give them a great experience and priority
5. [LOGISTICS] Finding the right dev for the project
6. [LOGISTICS] limited bandwidth for hackathons, high touch engagement activity
7. [PROCESS] two sides of the equation for dev acquisition, why are we not investing top of funnel of dev acquisition, ability to address that demand to generate it, get folks into the funnel, integrated to 0x, and disjointed at this stage
8. [PROCESS] how for community members to give back
9. [LOGISTICS] Potential messaging pivot of open-source vs corporate
 
```

--- 

:bulb: 
- customer support for dev rel
- ambassador program, challenge is to direct them effectively, now with the API there's a golden path. There are some ambassadors that are hand selected. A lot of overhead, they end up with a small group of people that are motivated, and now formalizing how these ambassadors in the community, and set them towards meaninful things

- community DAO for treasury, participate in the DAO. $2M in the DAO

:star: 
an ability for a hackathon project to turn to a project for mass usage, must stay friends with these projects because you never know

Dream is to have more motivating the devs to self motivate the ecosystem
- cultivating the culture 
- incentive creation in the ecosystem

---



:mag: Define Success
---
### What does success look like
- :star: API metric, market share of decentralized exchange vol that's attributable to 0x's API
    - what's the current and what's the goal?
    - individual devs contribution is near 0, most is institutional
- Matcha, how much are these products producing vol
- with every dev we adopt, which one has the most vol contribution
- open to expanding the defintion of metrics
- devs are existing companies may improve their company
    - metamask, many users, swap functionality
- open repo, don't have a lot of external contributors
    - ie more vol of individual contributors
    - our approach do we build our own devs beyond leveraging other projects' devs
Two theories
    - our tech is too intimidating
    - we don't expose PRs that others can work on
Potential messaging pivot of open-source vs corporate


:closed_book: Tasks
--

### Marketing:


### Ops:

:dart: Delivery
---
- each individual submits preferred priority

## Notes 
<!-- Other important details discussed during the meeting can be entered here. -->
