What is Developer Relations (DevRel)?
TO THE COMMUNITY, I REPRESENT THE COMPANY.
TO THE COMPANY, I REPRESENT THE COMMUNITY.
I MUST HAVE BOTH OF THEIR INTERESTS IN MIND AT ALL TIMES.
DevRel Responsibilities
- Nurture high-impact fintech partnerships
- Advocate for the needs of the developer community
- Create proof-of-concept prototypes using our toolkit
- Write technical guides, tutorials, and reference docs
- Engage the developer community by answering questions, sharing announcements, and finding champions/ambassadors
- Present at conferences, meetups, webinars, livestreams, and industry/company events
When should you engage the DevRel team?
External Engagements (e.g. Customers/FIs, Vendors, Consulting Firms)
It makes sense to engage the DevRel team for external engagements when any of these apply:
- Customer has reviewed the public resources and has additional technical questions about our Authentication / APIs / Plugins
- Strategic partnerships with fintech companies
Key points:
- Should share with our team prior to engagement:
- relevant legal briefings (e.g. data access)
- technical documentation (e.g. special rate limit agreements)
- other contextual information that is already known
- Must have a well-defined meeting agenda
- Must have attendee list that includes one or more of the following:
- Software Developer / Software Engineer
- Software Architect / Systems Architect
- Engineering Manager
- Director of Engineering
- Vice President (VP) of Engineering
- Chief Technical Officer (CTO)
- Should have software developers in attendance
Internal Discussions
It makes sense to engage the DevRel team for internal discussions when any of these apply:
- APIs are being created, updated, deprecated, or removed
- Questions arise that are similar to ‘does this make sense for the developer community?’
Key points:
- We’re friendly folks, please reach out and we can schedule some time!
- We prefer having a well-defined meeting agenda to help prep for the discussion
Public Resources to Share
These resources can be shared freely with customers/FIs/vendors/consultants. They are publicly available on the open web.
Sharing these resources can lead to better-focused meetings or in some cases eliminate the need for a meeting.
- Banno Digital Toolkit website: https://banno.com/digital-toolkit
- Developer Docs site: https://jackhenry.dev
- Authentication Framework: https://jackhenry.dev/open-api-docs/authentication-framework/getting-started/
- Consumer API: https://jackhenry.dev/open-api-docs/consumer-api/getting-started/
- Plugin Framework: https://jackhenry.dev/open-api-docs/plugins/getting-started/
- Admin API: https://jackhenry.dev/open-api-docs/admin-api/getting-started/
- Accessing the Digital Toolkit: https://jackhenry.dev/open-api-docs/accessing-the-digital-toolkit/
- Consumer API OpenID Connect Example: https://github.com/Banno/consumer-api-openid-connect-example
- Simple Plugin Example: https://github.com/Banno/simple-plugin-example
- Design Guidelines: https://jackhenry.design