Giri Venkatesan

Giri Venkatesan

Solace Corporation

Solace Corporation

A Technology enthusiast, keen on learning new tech and engineer innovative products and solutions. My favorite topics are EDA & Integration. Expert problem solver, and Solution Thinker. Currently engaged as Developer Advocate, Office of the CTO at Solace.

Onboarding - Not All Developers are the same

オンボーディング - すべての開発者が同じではない

Talk description トーク概要

A Developer community is very similar to a real-world community, a techno-social unit made of members from varying experience and backgrounds but celebrating technology, common goals and challenges. DevRel focuses on serving the community needs in every possible way during their journey and hopes to turn them into champions and ambassadors. However, care must be taken not to assume all members are same or equal and employ a one-size-fits-all approach. We will be dealing with people of varying technical experience, backgrounds, expectation, interest level, prior exposure, skillset and above all the intent and goals.

The most crucial aspect of Developers’ journey is the onboarding and it determines their commitment for a successful and continuous engagement. It should be noted that their experience and engagement may affect the success of the Partners or Customers whoever they are representing. When designing the onboarding journey, DevRel should be aware of the persona of developers and devise paths to engage them correctly from the beginning. Oftentimes, one would assume that creating world-class materials and references, in all possible media forms is enough to turn every Developer into an ambassador - sadly not true. The sifting and searching one has to go through to get their feet on the ground would drain the interest levels, rather than engaging.

There are numerous classification schemes for learners and learning patterns.

a) The question of ‘Who’

Who are they and why are they there? Are they a ‘Student’ - genuinely wanting to learn, a ‘Tourist’ - a drifter, just want to check it out and decide and lastly a ‘Prisoner’ - who doesn’t want to be there. The return on investment is much higher on the Student and even Tourist persona, as their attention span and interest levels are better and will excel eventually without fail.

b) The question of ‘How’

The University of Arizona classifies typical learning patterns as

i) Sequence - Begin a task by asking basic questions like ‘What are the directions’ and ‘What am I expected to do?’. Learners following this pattern would wait till their questions are cleared and are convinced of the agenda for themselves.

ii) Precision - Loads of questions, needing information and acting with precision to do things correctly. These are walking encyclopaedia 😊

iii) Reasoning - Hands on, wanting to get a handle on the tools and gadgets and do it themselves. These are tinkerers who love to solve problems and prefer to work alone and DIY guys.

iv) Confluence - Abstract thinkers, usually think out of the box and use metaphors to explain things as they see and experience, rather than the exactness with words

I would like to add the following as the fifth pattern for advanced and experience developers who already have relevant background but might require bit of concept mapping and unlearning :)

v) Cross-reference - Experts who have prior experience on similar products, who prefer to map out things to either a standard or vocabulary they are familiar with.

c) The question of ‘What’

From the wealth of resources and materials, what excites them. Their learning style would steer them towards artifacts of a particular medium - visual, auditory, written and kinaesthetic. Having content in relevant mediums would ensure that they kick start their journey with ease and joy.

To cover the disparate needs and expectations - the following guideline would help make the first step.

  1. Collect key information at the time of signup to know the Developer’s persona, how they learn and their preferences
  2. Catalog all the existing reference materials marked for level, path and relevant tags
  3. Collate materials, stitching up a learning path for distinct roles with versions of right mix of different mediums (audio, visual, reading and labs)
  4. Collaborate with them to create new assets, present opportunities to showcase their expertise, recognized and reward them

Of course, it goes without saying ‘continuous evaluation and tweaking is expected’ and should become part of the process.

A Developer Community that has maximum participation, collaborative knowledge creation and sharing and genuine reach-out with the singular goal of helping is bound to succeed and surely poised to become a sustained community.




a) 「誰」という問いかけ


b) 「どのように」という問いかけ


i) 順番 - 「指示は何ですか」「私は何をすればいいですか」などの基本的な質問をしてタスクを始める。このパターンの学習者は、自分の疑問が解消され、自分にとっての課題を確信するまで待つ。

ii) 精密さ - たくさんの質問をし、情報を必要とし、物事を正しく行うために正確に行動する。これらは歩く百科事典のようなものです😊。

iii) Reasoning - 手を動かすことが好きで、ツールやガジェットを使いこなして自分でやってみたいと思っています。問題を解決することが好きで、一人で作業することを好む、DIY好きな人たちです。

iv) Confluence - 抽象的な考え方をする人で、通常は既成概念にとらわれず、言葉で正確に説明するのではなく、自分が見たり経験したりしたように、比喩を使って説明する。


v) 相互参照 - 類似した製品の経験がある専門家で、自分がよく知っている基準や語彙で物事をマッピングすることを好む。

c) 「何を」の問題



  1. サインアップ時に、開発者のペルソナ、学習方法、好みなどの重要な情報を収集する。
  2. 既存の参考資料をすべてカタログ化し、レベル、パス、関連タグを明記する。
  3. 教材を照合し、さまざまな媒体(オーディオ、ビジュアル、リーディング、ラボ)を適切に組み合わせたバージョンで、それぞれの役割に応じた学習パスを作成する。
    1. 彼らと協力して新しい資産を作り、彼らの専門知識を披露する機会を提供し、彼らを評価し、報いる。