Home
/
Blog
/
Tech Assessment
/
How to drive API adoption through hackathons

How to drive API adoption through hackathons

Author
Vivek Siva
Calendar Icon
September 29, 2017
Timer Icon
3 min read
Share
Studies show that hackathons seem to be the most effective method to acquire and engage developer talent for open APIs.

Introduction

The star working behind the scenes, connecting devices, databases, and applications, application programming interfaces (APIs) are super-efficient “messengers” vital to organizations across sectors; for reuse in useful, interesting apps (tools and widgets), APIs allow these organizations to open their databases, backend systems, and information assets.

A simple definition of an API could be this: “An API is the messenger that delivers your request to the provider that you’re requesting it from and then delivers the response back to you.” For example, say you order an anorak from an e-retailer such as Amazon. The website will send your credit card details to PayPal, a payment processor, your shipping information to FedEx, a delivery partner, and then, validate your address using another API. Did you notice that all you needed to know was what to click and how to send a “request” and wait for the “response,” which could be payment status, shipping charges, etc.? (If you think about it, the function of an API closely mirrors that of a waiter at a restaurant.)

Programmers communicate with an application, such as Accuweather or Candy Crush, use this common interface, which acts like a go-between. “API is a precise specification written by providers of a service that programmers must follow when using that service. It describes what functionality is available, how it must be used and what formats it will accept as input or return as output. In recent years, the term API colloquially is used to describe both the specification and service itself, e.g., the Facebook Graph API,” says API Chapter Manager at Sprout Social, Kevin Stanton.

Uses of APIs

According to John Musser, co-founder of Programmable Web, an API can be used to create value in several ways, including the following:

  • APIs as product
  • Marketing/Distribution channel
  • User/Content acquisition
  • Drive innovation/traffic
  • Accelerate internal projects
  • Partner/Upsell opportunities
  • Lead generation/ Business development/Increase footprint
  • Extend product/Device and Mobile support
  • Increase stickiness
  • New line of business

Three P’s of an API program

Developing an API program comprises three stages1 — Plan, Productize, and Promote.

From the snapshot below, you can see that attracting and engaging developers are core activities for a successful API strategy. With a well-designed API program with skilled developers and open APIs, companies can extend their reach significantly by enabling market adoption, accelerating innovation by crowdsourcing, and maintaining a constant revenue cycle.

For an organization, its value chain will have its assets, the APIs that open up these assets, developers who use these assets through APIs to create value, apps the developers build and end users.

The 3 Ps of API - how to drive API adoption using hackathons

Source: Software AG

Promoting your API

Once a product is good to go, it is ready to enter the marketing cycle. This is true for APIs as well.

  • Just like you would design any marketing strategy, segment your audience, target accessible, differentiable, and substantial developer segments to enter, and position the API to effectively address specific challenges of the target segments.
  • Indulge in influencer marketing; create advocates and get buy-in from great developers. Instead of talking at the developer community, listen to their feedback and advice.
  • Give the influencers leeway; let them work for you.

You need a great demo that talks about your company and the product, how it generates business value, and a live demo showing some code or what you can build on top of the API.

With a scalable, practical, and reliable API, developers can innovate, happily too if rewards and recognition are assured. Remember that developers target different environments, platforms, operating systems, languages, services, etc. Companies work with developer evangelists, support developer events, and launch an outstanding developer portal to better position the interface.

Call it marketing or call it raising awareness. Either way, your developers need to know this API exists. Public Relations managers can ensure that the information that is disseminated about your API is accurate while highlighting its unique features. You can reach developers through social channels, at events, and through other developer communities.

Remember to define your metrics. (Go here for a good post on API metrics.)

API funnel 0- how to drive API adoption using hackathons

*The first two steps—acquisition and activation, come under the marketing umbrella.

**The other three—retention, revenue, and referral depend on many factors such as the quality of your API.

Provide forums and interactive, up-to-date documentation to engage and educate the developers

In his talk on API adoption, marketing expert Adam DuVander presented results from a survey on API adoption, where developers rated these factors as most important on a scale of 1–4. Complete and accurate documentation tops the list with a rating of 3.5. DuVander says, “You can also help your marketing department to speak ‘developer,’ and part of that is making sure your documentation is great and accessible.” To plug into the API, “Not only show them what’s possible, but show them how to do it using your API.” (With sample apps or tutorials). Forums allow developers to have stimulating and informative discussions on code examples, best practices, etc.

Ebook - Hackathon Guide

Create an all-encompassing API portal

This portal will be the go-to place for developers to “register, explore, and learn” about your API, including seamless payment link integrations. A registration process that’s easy to use should give them an API key for example. An API console or ready code will help developers test the functionality without having to write any code; make sure it is impressive. Offer the right devkits or SDKs, with installation and packaging standards. Ensure you offer adequate support services; a little hand holding is always appreciated. Present developers with great uses cases with sample code and your SDKs. Your links to external resources must include announcements/updates and any information that will be useful (e.g. standards). Tools such as APIfy will help to build and manage such a central repository.

Driving API adoption through hackathons

A well-marketed and well-executed hackathon can get you 1500 developers and 3000+ for big names such as IBM. And you can get anywhere between 20–40 decent applications. All this can be done over a course of 4 weeks. “From a marketing standpoint, the developer acquisition is cost is very low.” Hackathons are an excellent example of viral marketing.

Specifically, a hackathon:

  • Gives you maximum air time to pitch your API to the developers
  • Gives you the opportunity to put your product (API) in the hands of passionate developers and get them to use it
  • Gets you valuable feedback from the developers to improve your product

*Hackathons are different from developer conferences and meetups. “A simple analogy would be that a hackathon is an internship, while a developer conference is a classroom.”

Points to remember for API providers hosting hackathons for marketing

  • Online hackathons are better suited
    Note that online hackathons could be a better bet as you get rid of all constraints related to venue selection and logistics. They also allow you to reach out to developers around the world. Keep the submission phase of the hackathon open for a longer duration, ideally for about two months.
  • Support at the hackathon
    Provide support and know-how via webinars, walkthrough, videos, tutorials, and examples of similar applications built using the API.
  • Post-hackathon engagement
    Support developers who could support only half-built applications as well; invite the developers for a symposium, follow up with them via emails and social channels for their feedback, and engage with them regularly. These people will form your talent pipeline.

**For all the finer details about how to organize a hackathon, download this ebook.

Conclusion

According to Philipp Schöne, Product Manager at Axway, “hackathons are a great way to learn what external people think about your offering… start with smaller groups and go bigger if you get more confident with your offering.”

You don’t always need to host a hackathon. You could participate or be a partner for smaller events. “Too often people think building a community means running a hack event, we found that running our own hack events didn’t fit our API, however attending and participating (as a team vs API vendor) in hack events was invaluable for building out a community. The best thing you can do is roll up your sleeves and get involved,” says Keran McKenzie, a platform evangelist at MYOB.

If companies find it hard reaching out to the developer community, then they can partner with vendors such as HackerEarth to leverage its 1.5 million+ developer community and use its hackathon management software.

Subscribe to The HackerEarth Blog

Get expert tips, hacks, and how-tos from the world of tech recruiting to stay on top of your hiring!

Author
Vivek Siva
Calendar Icon
September 29, 2017
Timer Icon
3 min read
Share

Hire top tech talent with our recruitment platform

Access Free Demo
Related reads

Discover more articles

Gain insights to optimize your developer recruitment process.

The Mobile Dev Hiring Landscape Just Changed

Revolutionizing Mobile Talent Hiring: The HackerEarth Advantage

The demand for mobile applications is exploding, but finding and verifying developers with proven, real-world skills is more difficult than ever. Traditional assessment methods often fall short, failing to replicate the complexities of modern mobile development.

Introducing a New Era in Mobile Assessment

At HackerEarth, we're closing this critical gap with two groundbreaking features, seamlessly integrated into our Full Stack IDE:

Article content

Now, assess mobile developers in their true native environment. Our enhanced Full Stack questions now offer full support for both Java and Kotlin, the core languages powering the Android ecosystem. This allows you to evaluate candidates on authentic, real-world app development skills, moving beyond theoretical knowledge to practical application.

Article content

Say goodbye to setup drama and tool-switching. Candidates can now build, test, and debug Android and React Native applications directly within the browser-based IDE. This seamless, in-browser experience provides a true-to-life evaluation, saving valuable time for both candidates and your hiring team.

Assess the Skills That Truly Matter

With native Android support, your assessments can now delve into a candidate's ability to write clean, efficient, and functional code in the languages professional developers use daily. Kotlin's rapid adoption makes proficiency in it a key indicator of a forward-thinking candidate ready for modern mobile development.

Breakup of Mobile development skills ~95% of mobile app dev happens through Java and Kotlin
This chart illustrates the importance of assessing proficiency in both modern (Kotlin) and established (Java) codebases.

Streamlining Your Assessment Workflow

The integrated mobile emulator fundamentally transforms the assessment process. By eliminating the friction of fragmented toolchains and complex local setups, we enable a faster, more effective evaluation and a superior candidate experience.

Old Fragmented Way vs. The New, Integrated Way
Visualize the stark difference: Our streamlined workflow removes technical hurdles, allowing candidates to focus purely on demonstrating their coding and problem-solving abilities.

Quantifiable Impact on Hiring Success

A seamless and authentic assessment environment isn't just a convenience, it's a powerful catalyst for efficiency and better hiring outcomes. By removing technical barriers, candidates can focus entirely on demonstrating their skills, leading to faster submissions and higher-quality signals for your recruiters and hiring managers.

A Better Experience for Everyone

Our new features are meticulously designed to benefit the entire hiring ecosystem:

For Recruiters & Hiring Managers:

  • Accurately assess real-world development skills.
  • Gain deeper insights into candidate proficiency.
  • Hire with greater confidence and speed.
  • Reduce candidate drop-off from technical friction.

For Candidates:

  • Enjoy a seamless, efficient assessment experience.
  • No need to switch between different tools or manage complex setups.
  • Focus purely on showcasing skills, not environment configurations.
  • Work in a powerful, professional-grade IDE.

Unlock a New Era of Mobile Talent Assessment

Stop guessing and start hiring the best mobile developers with confidence. Explore how HackerEarth can transform your tech recruiting.

Vibe Coding: Shaping the Future of Software

A New Era of Code

Vibe coding is a new method of using natural language prompts and AI tools to generate code. I have seen firsthand that this change makes software more accessible to everyone. In the past, being able to produce functional code was a strong advantage for developers. Today, when code is produced quickly through AI, the true value lies in designing, refining, and optimizing systems. Our role now goes beyond writing code; we must also ensure that our systems remain efficient and reliable.

From Machine Language to Natural Language

I recall the early days when every line of code was written manually. We progressed from machine language to high-level programming, and now we are beginning to interact with our tools using natural language. This development does not only increase speed but also changes how we approach problem solving. Product managers can now create working demos in hours instead of weeks, and founders have a clearer way of pitching their ideas with functional prototypes. It is important for us to rethink our role as developers and focus on architecture and system design rather than simply on typing c

The Promise and the Pitfalls

I have experienced both sides of vibe coding. In cases where the goal was to build a quick prototype or a simple internal tool, AI-generated code provided impressive results. Teams have been able to test new ideas and validate concepts much faster. However, when it comes to more complex systems that require careful planning and attention to detail, the output from AI can be problematic. I have seen situations where AI produces large volumes of code that become difficult to manage without significant human intervention.

AI-powered coding tools like GitHub Copilot and AWS’s Q Developer have demonstrated significant productivity gains. For instance, at the National Australia Bank, it’s reported that half of the production code is generated by Q Developer, allowing developers to focus on higher-level problem-solving . Similarly, platforms like Lovable enable non-coders to build viable tech businesses using natural language prompts, contributing to a shift where AI-generated code reduces the need for large engineering teams. However, there are challenges. AI-generated code can sometimes be verbose or lack the architectural discipline required for complex systems. While AI can rapidly produce prototypes or simple utilities, building large-scale systems still necessitates experienced engineers to refine and optimize the code.​

The Economic Impact

The democratization of code generation is altering the economic landscape of software development. As AI tools become more prevalent, the value of average coding skills may diminish, potentially affecting salaries for entry-level positions. Conversely, developers who excel in system design, architecture, and optimization are likely to see increased demand and compensation.​
Seizing the Opportunity

Vibe coding is most beneficial in areas such as rapid prototyping and building simple applications or internal tools. It frees up valuable time that we can then invest in higher-level tasks such as system architecture, security, and user experience. When used in the right context, AI becomes a helpful partner that accelerates the development process without replacing the need for skilled engineers.

This is revolutionizing our craft, much like the shift from machine language to assembly to high-level languages did in the past. AI can churn out code at lightning speed, but remember, “Any fool can write code that a computer can understand. Good programmers write code that humans can understand.” Use AI for rapid prototyping, but it’s your expertise that transforms raw output into robust, scalable software. By honing our skills in design and architecture, we ensure our work remains impactful and enduring. Let’s continue to learn, adapt, and build software that stands the test of time.​

Ready to streamline your recruitment process? Get a free demo to explore cutting-edge solutions and resources for your hiring needs.

Guide to Conducting Successful System Design Interviews in 2025

What is Systems Design?

Systems Design is an all encompassing term which encapsulates both frontend and backend components harmonized to define the overall architecture of a product.

Designing robust and scalable systems requires a deep understanding of application, architecture and their underlying components like networks, data, interfaces and modules.

Systems Design, in its essence, is a blueprint of how software and applications should work to meet specific goals. The multi-dimensional nature of this discipline makes it open-ended – as there is no single one-size-fits-all solution to a system design problem.

What is a System Design Interview?

Conducting a System Design interview requires recruiters to take an unconventional approach and look beyond right or wrong answers. Recruiters should aim for evaluating a candidate’s ‘systemic thinking’ skills across three key aspects:

How they navigate technical complexity and navigate uncertainty
How they meet expectations of scale, security and speed
How they focus on the bigger picture without losing sight of details

This assessment of the end-to-end thought process and a holistic approach to problem-solving is what the interview should focus on.

What are some common topics for a System Design Interview

System design interview questions are free-form and exploratory in nature where there is no right or best answer to a specific problem statement. Here are some common questions:

How would you approach the design of a social media app or video app?

What are some ways to design a search engine or a ticketing system?

How would you design an API for a payment gateway?

What are some trade-offs and constraints you will consider while designing systems?

What is your rationale for taking a particular approach to problem solving?

Usually, interviewers base the questions depending on the organization, its goals, key competitors and a candidate’s experience level.

For senior roles, the questions tend to focus on assessing the computational thinking, decision making and reasoning ability of a candidate. For entry level job interviews, the questions are designed to test the hard skills required for building a system architecture.

The Difference between a System Design Interview and a Coding Interview

If a coding interview is like a map that takes you from point A to Z – a systems design interview is like a compass which gives you a sense of the right direction.

Here are three key difference between the two:

Coding challenges follow a linear interviewing experience i.e. candidates are given a problem and interaction with recruiters is limited. System design interviews are more lateral and conversational, requiring active participation from interviewers.

Coding interviews or challenges focus on evaluating the technical acumen of a candidate whereas systems design interviews are oriented to assess problem solving and interpersonal skills.

Coding interviews are based on a right/wrong approach with ideal answers to problem statements while a systems design interview focuses on assessing the thought process and the ability to reason from first principles.

How to Conduct an Effective System Design Interview

One common mistake recruiters make is that they approach a system design interview with the expectations and preparation of a typical coding interview.
Here is a four step framework technical recruiters can follow to ensure a seamless and productive interview experience:

Step 1: Understand the subject at hand

  • Develop an understanding of basics of system design and architecture
  • Familiarize yourself with commonly asked systems design interview questions
  • Read about system design case studies for popular applications
  • Structure the questions and problems by increasing magnitude of difficulty

Step 2: Prepare for the interview

  • Plan the extent of the topics and scope of discussion in advance
  • Clearly define the evaluation criteria and communicate expectations
  • Quantify constraints, inputs, boundaries and assumptions
  • Establish the broader context and a detailed scope of the exercise

Step 3: Stay actively involved

  • Ask follow-up questions to challenge a solution
  • Probe candidates to gauge real-time logical reasoning skills
  • Make it a conversation and take notes of important pointers and outcomes
  • Guide candidates with hints and suggestions to steer them in the right direction

Step 4: Be a collaborator

  • Encourage candidates to explore and consider alternative solutions
  • Work with the candidate to drill the problem into smaller tasks
  • Provide context and supporting details to help candidates stay on track
  • Ask follow-up questions to learn about the candidate’s experience

Technical recruiters and hiring managers should aim for providing an environment of positive reinforcement, actionable feedback and encouragement to candidates.

Evaluation Rubric for Candidates

Facilitate Successful System Design Interview Experiences with FaceCode

FaceCode, HackerEarth’s intuitive and secure platform, empowers recruiters to conduct system design interviews in a live coding environment with HD video chat.

FaceCode comes with an interactive diagram board which makes it easier for interviewers to assess the design thinking skills and conduct communication assessments using a built-in library of diagram based questions.

With FaceCode, you can combine your feedback points with AI-powered insights to generate accurate, data-driven assessment reports in a breeze. Plus, you can access interview recordings and transcripts anytime to recall and trace back the interview experience.

Learn how FaceCode can help you conduct system design interviews and boost your hiring efficiency.

Top Products

Explore HackerEarth’s top products for Hiring & Innovation

Discover powerful tools designed to streamline hiring, assess talent efficiently, and run seamless hackathons. Explore HackerEarth’s top products that help businesses innovate and grow.
Frame
Hackathons
Engage global developers through innovation
Arrow
Frame 2
Assessments
AI-driven advanced coding assessments
Arrow
Frame 3
FaceCode
Real-time code editor for effective coding interviews
Arrow
Frame 4
L & D
Tailored learning paths for continuous assessments
Arrow
Get A Free Demo