DEV Community: Zevi Reinitz

Top 5 Elasticsearch Consulting Companies in 2026

Zevi Reinitz — Mon, 16 Feb 2026 14:49:09 +0000

Authors note: I've been working with companies in the Elasticsearch and OpenSearch space for over a year now. Together with a select group of industry coleagues I've put together this list as a resource to the community. Hope it's valuable!

As Elasticsearch continues to evolve, organizations that depend on it for analytics, search, and observability face growing complexity. The engine that once ran a few indices on a single node now powers high-traffic websites, AI-driven search platforms, and data pipelines serving millions of queries per day.

At this scale, running Elasticsearch efficiently and reliably requires more than familiarity with the stack — it demands deep expertise, tuning experience, and an understanding of how infrastructure, application design, and data models intersect.

Whether you’re planning a migration, scaling production clusters, or looking to optimize performance and cost, partnering with the right consulting team can make a measurable difference.

Below, we highlight the top consulting firms specializing in Elasticsearch, based on technical depth, project track record, and client satisfaction.

How We Selected These Firms

This list focuses on firms with proven expertise in Elasticsearch rather than general IT outsourcing vendors. Each company was evaluated across four key criteria:

Technical expertise and specialization– demonstrated proficiency in Elasticsearch architecture, scaling, and performance tuning.
Real-world experience – successful delivery of enterprise search, observability, or analytics projects.
Customer references – verifiable impact on performance, stability, or ROI.
Breadth of services – the ability to integrate Elasticsearch with supporting systems (data pipelines, monitoring, AI search).

The goal is to give decision-makers a practical overview of the consulting landscape in 2026, separating niche specialists from large-scale integrators.

Comparison Snapshot

Company	Core Focus	Ideal For	Key Strength
BigData Boutique	Deep Elasticsearch & OpenSearch consulting	Enterprises needing expert-led tuning and cost optimization	In-depth engineering backed by proprietary AI tools (Pulse)
Toptal	Freelance experts across many tech domains	Short-term Elasticsearch projects	Rapid access to vetted engineers
Brainhub	Software engineering and product delivery	Product teams building search-driven apps	Integration of Elasticsearch into full-stack projects
Altoros	Cloud-native and data platform modernization	Enterprises migrating from legacy systems	Cloud automation and Kubernetes expertise
Netguru	End-to-end digital solutions	Businesses seeking UX + search together	User-focused approach to search experience
Selleo	Custom web development	Mid-size companies building specialized systems	Balanced development and search integration skills

Top Specialized Elasticsearch Consulting Firms

BigData Boutique

BigData Boutique is one of the most recognized names in the Elasticsearch and OpenSearch ecosystem. Founded by Itamar Syn-Hershko, a long-time search technologist and OpenSearch Ambassador, the company has delivered hundreds of projects spanning large-scale search applications, observability stacks, and log analytics platforms. BigData Boutique is an official AWS technology partner and their work with BigData projects has been featured by AWS.

Their approach combines deep technical understanding with tooling built specifically for Elasticsearch operations. The company’s flagship platform, Pulse, functions as an AI-powered virtual SRE platform for OpenSearch and Elasticsearch — proactively identifying performance issues with RCA, suggesting optimizations, and reducing operating costs.

This combination of human expertise and automation makes BigData Boutique a top choice for organizations seeking continuous optimization rather than one-off consulting.

Typical engagements include:

Cluster performance audits and cost optimization
Search relevance tuning and query analysis
Upgrades, version migrations, and high-availability design
24/7 expert support through the Pulse platform

With a reputation for transparency and measurable results, BigData Boutique continues to be a go-to partner for enterprises that depend on Elasticsearch at scale.

Toptal
Toptal operates a global network of freelance professionals across software engineering, data science, and DevOps. For Elasticsearch users, Toptal’s value lies in its flexibility — the ability to bring in senior-level engineers on demand for short-term tuning, migration, or integration tasks.

While it’s not a dedicated search consultancy, Toptal’s screening process ensures access to engineers experienced with Elasticsearch APIs, schema design, and infrastructure scaling. This model suits teams that have internal expertise but need temporary bandwidth for specific challenges.

Brainhub

Brainhub focuses on building and scaling digital products. Its developers and data engineers have experience embedding Elasticsearch into web and SaaS platforms for real-time search, analytics dashboards, and recommendation systems.

The firm stands out for combining software craftsmanship with an understanding of data modeling and API performance — making it a good choice for teams that want to integrate search deeply into their product experience rather than treat it as an external service.

Altoros

Altoros has long been recognized for its work in cloud automation, Kubernetes, and data platform modernization. Their engineers bring strong expertise in containerized Elasticsearch deployments, infrastructure-as-code, and observability pipelines.

The company often helps clients migrate on-premise or legacy systems to Elasticsearch on AWS or Kubernetes, with a focus on maintainability and cost control.

Altoros’s ability to standardize complex deployments and integrate Elasticsearch into modern CI/CD environments makes it a strong option for enterprises modernizing large data infrastructures.

Netguru

Netguru is best known for design-driven software development, but their data and engineering teams also have solid experience delivering Elasticsearch-powered search and analytics capabilities.

They excel at bridging the gap between search performance and user experience — helping organizations ensure that query results are both fast and contextually relevant. Netguru is often chosen by companies building customer-facing products where usability and precision are equally important.

Selleo

Selleo delivers full-cycle custom software development with a strong focus on web applications and API integrations. While smaller than some others on this list, Selleo’s engineers have implemented Elasticsearch solutions for clients seeking domain-specific search and filtering capabilities within complex business systems.

Their strength lies in adaptability — integrating Elasticsearch into Ruby, Python, and Java-based ecosystems and ensuring that search aligns with each organization’s data model. This makes Selleo a practical choice for mid-market businesses looking for reliable, specialized development support.

Top Global IT and Business Consulting Firms for Elasticsearch

While the specialized firms above offer focused technical expertise, global IT consultancies bring scale and integration capabilities suited for large digital transformation initiatives. These firms often handle Elasticsearch as part of broader cloud, data, or observability programs.

Accenture

Accenture integrates Elasticsearch into enterprise data and analytics strategies, often combining it with cloud-native services on AWS, Azure, or GCP. The company focuses on operational visibility, AIOps, and observability frameworks, helping Fortune 500 clients centralize logs, metrics, and traces across hybrid environments.

IBM

IBM’s consulting division leverages Elasticsearch as part of its data fabric and AI initiatives. With deep enterprise presence and security focus, IBM provides long-term managed services for Elasticsearch clusters supporting analytics, risk monitoring, and IT operations management.

Deloitte

Deloitte applies Elasticsearch within its analytics and risk practices, focusing on search-driven insights, compliance visibility, and performance monitoring. They often combine Elasticsearch with data visualization tools to help enterprises detect anomalies and improve decision-making.

Infosys

Infosys integrates Elasticsearch into large-scale modernization and observability projects. Their teams build unified search and logging platforms that support DevOps and SRE workflows for global clients, particularly in telecom, retail, and finance.

Capgemini

Capgemini uses Elasticsearch across cloud transformation engagements, emphasizing log analytics, cybersecurity monitoring, and infrastructure intelligence. Their engineers help enterprises build resilient, cost-optimized platforms that scale on AWS and Kubernetes.

Cognizant

Cognizant delivers Elasticsearch as part of digital operations and AIOps initiatives. The company focuses on integrating search and analytics with business workflows to improve reliability and reduce incident resolution time.

Common Use Cases for Elasticsearch Consulting

Across industries, Elasticsearch consulting engagements typically focus on these high-impact areas:

Performance Optimization: Identifying query bottlenecks, optimizing mappings, and improving indexing strategies.
Cost Reduction: Right-sizing clusters, improving storage efficiency, and leveraging hot-warm-cold architectures.
Migration and Upgrades: Seamless version upgrades, including Elastic → OpenSearch transitions.
Relevance Tuning: Refining search accuracy for e-commerce, document retrieval, and enterprise search.
Monitoring and Observability: Integrating with AWS OpenSearch Service, Kibana, or external monitoring tools for proactive alerting.
Security and Compliance: Implementing access control, encryption, and audit logging in regulated environments.

Example: Automation and Optimization Through Pulse

One of the most notable trends among leading consultancies is the integration of AI-driven operations. BigData Boutique’s Pulseplatform exemplifies this direction — a system designed to act as a virtual OpenSearch SRE, continuously analyzing performance metrics, providing automated root cause analysis, regular cluster health assessments, and cost/performance optimization recommendations.

By combining this intelligent automation with expert guidance, organizations reduce manual effort, detect anomalies earlier, and maintain consistent performance across clusters — particularly in high-availability AWS environments.

FAQs

Q: Do I need a consulting firm if I’m using managed services like Amazon OpenSearch Service?

Yes. Managed services simplify infrastructure but don’t automatically optimize query performance, mappings, or relevance. Consulting partners help fine-tune configurations, manage costs, and ensure scalability.

Q: What’s the difference between Elasticsearch and OpenSearch consulting?

They share the same roots and similar APIs. Experienced consultancies typically handle both. The key is understanding version compatibility and operational nuances in each environment.

Q: How do I choose between a boutique firm and a global integrator?

If your focus is hands-on optimization, go boutique. If Elasticsearch is one component in a multi-system transformation, a global integrator may offer better alignment with enterprise governance and program management.

Final Thoughts

The Elasticsearch consulting ecosystem has matured significantly.

In 2026, organizations have options ranging from highly specialized boutique firms to large-scale system integrators — each bringing unique strengths. The right partner depends on whether you need deep technical tuning, long-term support, or enterprise integration at scale.

For teams running critical workloads, platforms like Pulse are redefining what support looks like — moving from reactive issue resolution to proactive, intelligent optimization.

Whatever your path, aligning with experts who understand the evolving Elasticsearch landscape remains one of the best investments you can make in stability, speed, and cost efficiency.

Wix’s xEngineer Is Changing The Definition of "Shift-Left"

Zevi Reinitz — Wed, 11 Feb 2026 12:23:00 +0000

This amazing piece of content was created with ❤️ by the team at Pulse - the AI SRE platform for OpenSearch and Elasticsearch, automating cluster maintenance and support for the world's best teams.
_

Wix’s Big AI Engineering Announcement

Wix recently announced a structural shift in how it expects its engineering organization to operate in an AI-first environment. Predictably, much of the reaction focused on what this might mean for headcount and job security.

That focus misses the point.

The announcement wasn’t about reducing teams or replacing engineers. It was about redefining how engineering work is done as AI becomes a permanent part of the development process.

At its core, Wix is formalizing a model in which engineers are expected to work with AI systems by default. AI isn’t positioned as a productivity layer bolted onto existing workflows, but as infrastructure — something engineers are expected to reason with as part of their day-to-day work.

This shift reflects a broader change already underway across the industry. Engineering roles aren’t disappearing. They’re expanding, with broader ownership, higher expectations, and deeper reliance on specialized tooling.

Wix gave this shift a name: the xEngineer — an AI-native engineer with responsibility that spans the development lifecycle.

Why This Is Bigger Than Just Wix

While the announcement is specific to Wix, it’s notable because it shows how a large, mature engineering organization is thinking about AI beyond experimentation.

Instead of framing AI as a set of tools or initiatives, Wix framed it as an organizational change — one that affects how engineering work is defined, evaluated, and prioritized.

Large engineering organizations tend to formalize changes only after they’ve already proven out in practice. When roles and expectations shift at this level, it usually reflects pressures that are already present across the industry.

Wix was explicit that this shift is not about replacing engineers or reducing teams, but about changing how engineering effort is applied. Less time is expected to go toward low-leverage implementation details, with more focus on system design, architecture, reliability, and security.

Seen through that lens, the announcement reads less like a company update and more like a preview of where engineering roles are heading.

Where This Shift Shows Up First

When it comes to AI adoption, not all engineering domains are affected equally — especially in an xEngineer model where engineers are expected to take on broader ownership across the lifecycle.

If this shift is real and structural, it won’t appear everywhere at once. It will surface first in areas where complexity is high, signals are noisy, and better judgment has immediate production impact.

To see what that looks like in practice, it’s useful to look at another announcement from the same Wix team earlier this year.

Several months before the broader organizational change, Wix described how it had already begun introducing AI into parts of its CI/CD and reliability workflows.

The key insight was that not every aspect of CI/CD needs to be deterministic. While builds and deployments must remain predictable, tasks like interpreting logs, triaging failures, and recommending fixes operate in gray areas where AI’s pattern recognition is particularly effective.

Just as importantly, Wix was careful about boundaries. AI was not used to trigger deployments or make infrastructure decisions. It was used to guide the humans who do — reducing cognitive load and speeding up understanding without removing accountability.

Seen in that light, the broader xEngineer announcement becomes clearer. If engineers are expected to own outcomes beyond writing code, AI has to prove its value first in operational domains like DevOps — where understanding system behavior is the bottleneck, not execution.

What Wix’s Announcement Actually Signals

Taken together, Wix’s announcements point to three clear signals about how engineering work is evolving in an AI-first world.

First, xEngineer is now a real role model.

Wix may have named it, but many teams already feel the shift. Engineers are expected to think more broadly, own outcomes more fully, and work across traditional boundaries with AI as a built-in part of how they operate.

Second, specialization is shifting from people to tooling.

As engineers become broader, the tooling around them becomes deeper. Instead of relying on narrowly specialized roles for every domain, organizations are investing in system-aware tools that absorb complexity. The xEngineer isn’t a shallow generalist — they’re supported by increasingly expert tooling.

Third, operations is where this change is felt most strongly.

DevOps and SRE work already involves interpreting noisy signals, correlating events, and making judgment calls under pressure. These are exactly the conditions where AI can meaningfully assist without taking control.

How xEngineering Reframes Shift-Left

This evolution carries with it an important side effect: it reframes what “shift-left” actually means.

Historically, shift-left meant pushing responsibilities earlier in the lifecycle, often from DevOps or SRE teams onto developers, with the goal of reducing downstream friction. In practice, this frequently redistributed operational burden without redistributing context or tooling.

The xEngineer model changes that dynamic.

When engineers are expected to reason across development, operations, and reliability as a single responsibility, shift-left is no longer about moving tasks between functions. The boundaries between those functions are already breaking down. Shift-left becomes an inherent property of the role itself.

In some organizations, xEngineers will take on near end-to-end ownership of how their systems behave in production. They won’t be deep experts in every underlying technology, but they will be accountable for outcomes — which only works if AI tooling helps them reason about systems they don’t fully specialize in.

In other organizations, dedicated SRE, DBA, or platform teams will continue to exist. But their role changes. These teams won’t manage a single narrow technology in isolation. They’ll span multiple systems, rely on AI tooling by default, and depend on xEngineers to remain actively involved after code ships. Operational responsibility becomes shared rather than handed off.

In this model, the challenge isn’t expanding responsibility. It’s making that expansion sustainable with the right tools.

So shift-left tooling is no longer about exposing more dashboards to more people. It’s about enabling xEngineers — and the specialized teams working alongside them — to share understanding and operate from the same context.

Without that shared understanding, shift-left collapses into toil.

What AI Actually Changes for DevOps and SRE Teams

In practice, the first impact of AI in operational engineering is on time and attention.

Less time is spent manually parsing logs, correlating signals across tools, or acting as the first stop for every pipeline failure. That work doesn’t disappear — it becomes compressed.

AI absorbs much of the mechanical effort involved in detection, scoping, and initial root cause analysis. Engineers reach meaningful decisions earlier, with more context and less cognitive overhead.

This also changes how issues move through organizations. Instead of DevOps specialists being pulled in primarily to interpret noisy data, AI-assisted analysis surfaces clearer explanations earlier. The result is fewer escalations and fewer handoffs.

Wix’s CI/CD experience illustrates this well. Build failures that once required developers to contact DevOps engineers are now often resolved independently, with AI-powered analysis providing enough context to understand what went wrong and why. DevOps teams aren’t removed from the process — they’re removed from the bottleneck.

This is what makes broader ownership viable.

Why This Resonates With Us at Pulse

In that sense, Wix’s announcement doesn’t feel disruptive to us. It feels clarifying.

The industry is converging on a model where engineers take broader responsibility — sometimes directly, sometimes in close partnership with specialized SRE and DBA teams — but always with shared ownership of outcomes. That model only works when understanding moves earlier than problems do.

Pulse was built for exactly this reality. It’s an AI-powered SRE and DBA platform for teams running complex, business-critical Elasticsearch and OpenSearch deployments. From day one, the goal wasn’t to abstract these systems away or automate decisions for experts — it was to make expanded responsibility possible without pushing operational burden onto individuals.

Pulse gives xEngineers and operational experts a shared, system-aware view of what’s happening. AI-powered root cause analysis compresses investigation time. Continuous cluster health checks establish clear system state. Purpose-built dashboards make complex environments legible across teams.

Our AI handles the heavy issue discovery and correlation, so expert humans can focus on judgment, tradeoffs, and response.

That’s what modern shift-left actually requires.

And that’s the intersection Pulse was designed to serve.

This is part of a series of thoughtful posts from the team at Pulse.

Pulse is an AI SRE platform for Elasticsearch, OpenSearch and Clickhouse that automates maintenance and support for your clusters with cluster insights, root cause analysis, cost optimization and more. Pulse is led by world-renowned Elasticsearch and OpenSearch experts.

Learn more about Pulse at https://pulse.support

Build an AI Agent And Win 💸

Zevi Reinitz — Fri, 18 Jul 2025 20:23:30 +0000

“Everyone’s talking about AI agents. But what can you actually build?”

We (the team at Portia AI) keep hearing this — so we’re turning the question back to the community... and we're offering $$$ to the people who can come up with the best answer!

Announcing The "Agents Showdown"

For the next 4 weeks, we're taking submissions for our first ever online hackathon. Join us for a chance to earn £500

💸 Glory awaits!

Overview

Portia AI is an open source SDK that wants to stand out because it helps AI agents pre-express their planned response to a prompt, share their progress during execution, and solicit human input under defined conditions.

👉🏼 We want to build some cool examples that leverage our differentiators and add them to our examples repo on Github.

The Bounty

The best submission will win a £500 bounty and will be featured on our social channels.

Judging Criteria

Submission should be very current i.e. leverages the latest emerging technologies in AI (MCP, A2A etc).
- Example: Two Portia agents coordinating their plan runs with each other / kicking off other Portia agents.
Demonstrates Portia’s strong suit e.g. dynamic planning with reinforcement (user-led learning) and / or human-agent interaction (hooks and clarifications).
- Example: Use hooks to handle profanity, PII leaks, prompt injections and more.
Touches on regulated spaces where mistakes due to agents going off the rails are very costly e.g. healthcare, finance, legal, insurance
Quality of submission (demo video, readme, code quality)
Submission should use solely (or predominantly) the Portia framework

Eligibility and How To Enter

Comment on this issue when you start working on the hackathon to let us know you're on it
Submit your project as a comment on this Github issue
- Provide a link to a private repo shared with emmaportia and Momo
Include a high-resolution demo video explaining how your project works
Write up a Readme including:
- Key package dependencies
- Setup steps
- Running instructions
- Overview of key components in the code
Follow our contribution guidelines in particular around linting
Star our GitHub repo 😇

Developer Resources

Get immersed in our SDK and give us a star ⭐️ (GitHub).
Head over to our docs (docs.portialabs.ai).
Join the conversation on Discord (https://discord.gg/DvAJz9ffaR).
Sign Up to Portia cloud and access 1000+ cloud and MCP tools with built-in auth out of the box

3 Issues That Remote MCP Developers Should Avoid

Zevi Reinitz — Tue, 08 Jul 2025 16:48:22 +0000

Remote MCP servers are only just starting to take off. As more platforms roll out support for the Model Context Protocol (MCP), we're seeing rapid growth in developer experimentation — and equally, we're seeing many of the common pitfalls emerge for teams building MCP servers for the first time.

At Portia, we’ve tested a broad range of remote MCP servers — from major providers like Asana, Atlassian, Intercom and Stripe, to emerging integrations like Fulcra, Globalping and Invideo. In the process, we’ve seen a few recurring issues that make MCP servers harder to use, slower to adopt, and more brittle in production.

[For some quick context - Portia is the framework that enables developers to build safe, reliable AI agents. We'd be thrilled to have you check out our SDK and give it a GitHub star!⭐ 🙏]

Here are 3 mistakes we’d recommend every MCP developer avoid.

1. OAuth redirects only work on localhost

Several MCP servers we tested work fine locally, but break when used in real-world staging or production environments. A common cause: OAuth redirect URIs are hardcoded to allow only localhost. While this might be convenient during initial development, it blocks testing in any remote environment.

For example, we couldn’t add Atlassian because they rejected valid redirect URIs during authorization flows. This makes it nearly impossible for integrators to properly test your server in their deployment pipelines.

✅ Best practice: Always allow multiple redirect URIs for OAuth clients, including both local and remote environments. Ideally, make this configurable per client.

2. Missing `.well-known` OAuth metadata or misconfigured tool discovery

The MCP spec depends on being able to automatically discover OAuth configuration using the .well-known/oauth-authorization-server endpoint. Several servers — including PostHog, Semgrep and Invideo — either failed to serve this file or required tokens to access the tools/list endpoint, which prevents tool discovery.

Without a valid .well-known file:

Client libraries can't automatically configure OAuth.
MCP agents can't discover your tool easily.
Developer experience suffers.

✅ Best practice: Make sure your .well-known/oauth-authorization-server is publicly accessible, standards-compliant, and returns the necessary OAuth metadata.

3. Unreliable server availability

MCP servers are expected to handle dynamic discovery, token exchange, and tool invocation — and this requires a fairly high level of reliability. In our testing, we encountered servers that were down for maintenance (Asana), intermittently unavailable (Plaid, Neon), or failed authorization flows with unhelpful errors (Fulcra).

In an agentic world, unreliability doesn’t just block a single API call — it can break entire task chains and workflows.

✅ Best practice: Invest early in uptime monitoring, clear error messages, and comprehensive OAuth error handling. MCP servers should fail gracefully and predictably.

The Good News: Testing is Easy With Portia

If you’re building a new remote MCP server, testing your implementation doesn’t need to be painful. Portia makes it simple to integrate, validate, and experiment with new MCP servers directly inside your agentic app — often in just 3 clicks.

As the MCP ecosystem matures, we're excited to help developers ship more reliable, agent-friendly integrations that just work — across staging, production, and every environment in between.

A Bit More About Portia

Portia AI is an open-source framework for building predictable, stateful, authenticated agentic workflows.

We allow developers to have as much or as little oversight as they’d like over their multi-agent deployments and we are obsessively focused on production readiness.

We invite you to play around with our SDK, break things, and tell us how you're getting on in Discord

[Boost]

Zevi Reinitz — Thu, 12 Jun 2025 12:57:25 +0000

Celebrating The Top Search-Tech Voices for 2025 🏆

Zevi Reinitz — Wed, 29 Jan 2025 17:40:10 +0000

The folks at Pulse are thrilled to launch the first ever awards for the "Top Search-Tech Voices"- a carefully curated list of the world's top search-tech professionals and thought leaders in ElasticSearch, OpenSearch and other search-relevant areas of tech.

Click here to nominate your favorite Search-Tech Pros for 2025

Finding Search Tech Industry Leaders

Search technology is quietly at the heart of so many of the products and platforms we rely on every day. From e-commerce sites delivering instant product results to observability tools helping DevOps teams uncover critical insights, search tech powers the digital experiences that users expect to be seamless, fast, and intuitive.

Behind the scenes, technologies like Elasticsearch and OpenSearch are the engines driving these capabilities—but the expertise to design, implement, and optimize search systems is anything but straightforward.

The professionals who excel in this field come from a variety of backgrounds and hold a range of job titles: data engineers, architects, developers, DevOps specialists, and even product managers. Despite their diverse roles, they all share one thing in common—a deep understanding of and interest in search.

But finding these experts on the internet and learning from them isn’t easy. Search tech isn’t as sexy as other areas of the tech industry. It doesn’t enjoy the same spotlight as fields like AI or cloud computing, and there isn’t a central hub where the leading voices of the search tech world are celebrated or easily discovered.

That’s why we created this list. To give credit where credit is due, and to make the top search-tech voice readily available to the rest of the community.

So whether you’re a developer trying to optimize your Elasticsearch cluster, a DevOps engineer integrating search into an observability stack, or a product leader seeking inspiration for building user-centric search features, this collection highlights the leaders sharing knowledge and pushing boundaries in the world of search.

These voices represent the pulse of search tech in 2025, and we’re here to celebrate and learn from them, together.

Why We Put This List Together

Here at Pulse, we live and breathe search technology.

As experts in Elasticsearch and OpenSearch operations ourselves, we’ve worked with dozens of companies and hundreds of industry professionals over the years who are solving complex problems and driving innovation in their organizations. One thing we’ve learned along the way? These individuals aren’t just powering search; they’re powering their companies’ success.

We also know how important the search tech community is. This is a space built on collaboration and shared knowledge—innovations happen faster when insights are shared, challenges are discussed, and new ideas are celebrated. However, despite the critical role these experts play, there hasn’t been a go-to resource to shine a light on their contributions or make it easy for others to learn from their expertise.

That’s why we’re finally putting this list together. It’s more than just a recognition of top voices; it’s a resource for the community we care so much about. Whether you’re new to search or a seasoned pro, we hope this list helps you discover new perspectives, find inspiration, and connect with the incredible professionals shaping the future of search technology.

How Do We Decide Who Makes the List?

In the spirit of transparency, here are the considerations we use to choose the top search-tech voices to follow:

Tech Stack: Are search technologies an integral part of their organization’s tech stack? We’re looking for people who have hands-on experience using and managing these technology deployments at scale.
Creativity and Innovation: We’re looking for people who have exhibited a creative approach to working with these technologies to positively impact their products, their organizations or the wider industry.
Leadership: Is this person a leader in this field? Do they exhibit unique opinions or have they exhibited exceptional achievements in this space?
Wisdom Sharing: Does this person share valuable content on social media or through regular speaking engagements? We’re looking to highlight people who take the time to share their wisdom with the community
Community-sourced: We’re giving strong preference to people who are nominated by the community. We want to celebrate the voices you value most!

We'll review this list regularly, and we welcome your feedback and suggestions.

How to Nominate Someone to Get Featured

The list of Top Search Tech Voices is under ongoing review by our editorial team. If you know of someone who deserves a mention - nominate them! It’s free and only takes about 45 seconds of your time.

Just fill out this form.

You can submit as many names as you’d like and you can even nominate yourself.

We’ll be publishing our initial list of recipients soon, and we’ll be adding/publicizing new additions as they are added throughout the year.

Check this out..

Zevi Reinitz — Wed, 22 Jan 2025 12:58:52 +0000

💡 The Untold History of GitHub Awesome-Lists 🤯

Zevi Reinitz ・ Jan 22

#github #programming #opensource #webdev

💡 The Untold History of GitHub Awesome-Lists 🤯

Zevi Reinitz — Wed, 22 Jan 2025 07:27:00 +0000

If you use GitHub, you’re probably familiar with “awesome-lists”.

Awesome-lists are a series of open source GitHub projects. They offer curated content around a specific topic that readers will find… awesome. Each list uses the “awesome-” naming convention and most of them give credit to other awesome lists that inspired them to create their own.

They’ve become so popular that GitHub now displays “Awesome Lists” as one of the options in the mobile app Explore tab:

You’ll find awesome-lists ranging from mainstream tech topics like awesome-react to random stuff like awesome-falsehoods (”a curated list of falsehoods programmers believe in.”), awesome-board -games (“a curated list of awesome and exceptional board games”) and awesome-veganism (“a curated list of awesome resources, pointers, and tips to make veganism easy and accessible to everyone”).

My Progress From Consumer → Maintainer

For me, awesome-lists were love at first site when I was introduced to the concept a few years ago. I’m now a maintainer of my very own list, having recently started awesome-opensearch together with my friends at Pulse.

👉 👉 [Would you mind giving my awesome list a GitHub star ⭐ ? I’d really appreciate it! 🙏 🙏

Researching the Origins of awesome-lists

All of this got me thinking - where did this awesome-list concept come from in the first place?

Who started it?

Did they do anything to promote the idea early on?

And why “awesome” of all possible superlatives?

I looked around and could not find anyone who had written about this, so I decided to fill the gap myself and write the first comprehensively researched history of awesome-lists in history.

It’s helpful that GitHub is built to leave digital fingerprints and clues, and so after sifting through lot of commit histories, READMEs and PR comments I’ve pieced together an authoritative timeline and history of awesome-lists.

Where it All Began

The first awesome-list in history was awesome-php, launched January 25, 2012 by Jamie York (@ziadoz on GitHub).

In his initial commit he wrote:

Here's some awesome PHP libraries that are awesome. Yes, so awesome I've used the word three times! You should be using them already:
Two years later, on January 17, 2014 another awesome-list came to life when Jan Van Ryswyck launched awesome-talks. And while this project carried a similar naming convention to awesome-php, Jack didn’t make any connection in his initial commits.

The first signal of influence and attribution would come a month later, on February 10, 2014 with the launch of awesome-sysadmin. In the initial commit, Francisco Augusto wrote:

A curated list of amazingly awesome sysadmin open source resources inspired by Awesome PHP.
Later that day, Francisco edited the README by adding more context:

A curated list of amazingly awesome sysadmin open source resources inspired by [Awesome PHP](https://gist.github.com/Xanza/7663627)
Notice that the reference is a GitHub Gist URL. Gist is a GitHub feature that lets you store and distribute code snippets without setting up a full-fledged repository. It’s sort of like GitHub’s version of a post or a tweet.

It turns out that the specific Gist reference that Francisco added is a dead link. Looks like he meant to reference: https://gist.github.com/ziadoz/1677679 which is where Jamie York had posted awesome-php back in January of 2012.

Early Traction

It seems then, that the initial awesome-lists were not actually repositories - they were Gists. And the initial traction and visibility of the awesome-list concept was thanks to the social and sharing nature of the Gists feature.

After almost 2 years on Gists, awesome-php had reached 260 forks and 1400 stars. And on Nov 29, 2013, Francisco announced that "Awesome PHP has been relocated permanently to its own Github repository](https://github.com/ziadoz/awesome-php). No further updates will made to this gist".

Awesome-lists had outgrown Gists and it was time to finally find their permanent home as stand-alone projects in GitHub proper.

The Wild Summer of 2014

The real inflection point for awesome-list growth was the summer of 2014 as several new awesome-list GitHub projects were launched during June and July.

On June 28, 2014, awesome-python was started. In the initial commit, Vinta Chen wrote:

A curated list of awesome Python frameworks, libraries and resources. Inspired by awesome-php.
On July 3rd, Marc Anguera launched awesome-ruby. There was no reference to other lists in the initial commit, but the timing and naming convention suggest that this was inspired by other awesome-lists that preceded it.

Awesome-lists were also starting to gain wider promotion on other social platforms. Take this tweet for example on July 9th 2014 telling people about the awesome-ruby project:
// Detect dark theme var iframe = document.getElementById('tweet-486779655681503232-59'); if (document.body.className.includes('dark-theme')) { iframe.src = "https://platform.twitter.com/embed/Tweet.html?id=486779655681503232&theme=dark" }

The rapid growth signals continued a couple of days later on July 6, 2014 when @avelino launched awesome-go. The initial commit reads:

A curated list of awesome Go frameworks, libraries and software. Inspired by awesome-python.
Whereas other awesome-lists had referenced awesome-php as their OG awesome inspiration, awesome-go had taken inspiration from the awesome-python project that was launched just a week prior.

The next day (July 7th) awesome-shell was launched by Caleb Xu. People throughout the GitHub ecosystem had apparently took notice of the awesome-list trend and they were joining with lists of their own.

Awesome-lists Filled With awesome-lists

By July 8th, there were enough awesome-lists out there with enough exposure to inspire the first awesome-list of other awesome-lists.

awesome-awesomeness was started by Alexander Bayandin as what he described as:

A curated list of amazingly awesome awesomeness
The list collected all of the above awesome-lists that came before it in one convenient place.

On July 10th of that year, the awesome-list trend continued with the arrival of awesome-devenv. In the initial commits Dotan J. Nahum highlighted the progression:

A curated list of awesome tools, resources and workflow tips making an awesome development environment. Inspired by [awesome-go](https://github.com/avelino/awesome-go), which was in turn inspired by [awesome-python](https://github.com/vinta/awesome-python).
On July 11th, another awesome-list aggregate was started when Sindre Sorhus launched awesome, which was described as:

“A curated list of awesome lists.”

It’s notable that one of the lists in this project’s first commit was frontend-dev-bookmarks. This list was started by Tim Navrotskyy on Jun 22, 2013, a year before the explosive growth of 2014.

The frontend-dev-bookmarks project obviously did not use the awesome- naming convention and it’s not clear that it was inspired by the budding awesome-list trend. It appears that this was a parallel, similar effort to curate useful information, as Tim suggests in the initial commit:

A badass list of frontend development resources I collected over time. Pull requests are welcome.
The pull of the awesome-list ecosystem was so strong, that even parallel efforts such as this one were pulled in.

Awesome-lists Become a “Thing”

On the same day Sindre Sorhus launched awesome, he also launched awesome-nodejs which was described as:

A curated list of delightful Node.js packages and resources. Inspired by the [awesome](https://github.com/sindresorhus/awesome) list thing.
Awesome-lists had arrived at scale.

They were officially “thing”.

What Caused the Wild Summer of 2014?

I reached out to several of these early awesome-list creators to understand what prompted the rapid growth during that summer of 2014.

I assumed there must of been an event or conference that put the awesome-list concept on display to the entire dev community, but it turns out that it was completely organic. This was a trend that caught on thanks to social media sharing and algorithms.

Balancing Scale and Quality

One of the interesting corollaries of awesome-list adoption was the challenge in maintaining them. How does one ensure that the links are correct? How do you identify links that become broken over time?

This was something that the early adopters thought about, with Dotan of awesome-devenv sharing an article at the end of 2015 explaining how he used Travis CI to automatically review and validate awesome list content.

Why “awesome”?

As we referenced at the beginning of this article, Jamie York used the word “awesome” to describe the very first awesome-list: “Here's some awesome PHP libraries that are awesome. Yes, so awesome I've used the word three times! You should be using them already:”

Awesome was used as an emotional measure of how delightful a resource of piece of content was. If it wasn’t delightful, then it didn’t belong on the list. The word “awesome” captured the ethos of the awesome-list movement and solidified the key distinction between collection and curation. The objective was to curate only the best content, and leave the other stuff out.

As Sindre Sorhus puts it in his contribution guidelines:

[Make sure the list] only has awesome items. Awesome lists are curations of the best, not everything.

Closing Thoughts

The rest, as they say, is history. Awesome lists are here to stay as an important part of GitHub culture. Collectively, these projects have gained millions of GitHub stars and they hav proven to be a valuable set of resources for the dev community and beyond.

The prolific growth of the awesome-list trend highlights the value of thoughtful content curation, and emphasizes the collaborative nature of open source.

You're awesome for sticking around until the end! If you've already come this far and have an extra 8 seconds to spare, I’d appreciate it if you would give awesome-opensearch a star!

Thank you!

I'm Zevi, a global marketing and growth advisor. I help early-stage companies become awesome with their organic growth.

If you're looking for more amazingly genius growth and marketing wisdom - subscribe to my Growth Notes (launching soon).

The world's first directory for dev content creators

Zevi Reinitz — Fri, 23 Feb 2024 12:43:59 +0000

Introducing influencer.dev

Let's start from the end - I've launched a platform called influencer.dev - a community initiative to showcase the world's best developer content creators.

Developer content is officially a thing

Let's understand why this is important.

You’re probably reading this post on Dev.to - a platform that enables technical content creators to share quality content with a dev-centric audience.

I was one of the early adopters of the platform and I’ve watched the community quickly grow to well over 1 million members.

The growth of Dev.to is part of an upward trend across the board in developers creating and publishing content. It’s great seeing developers push content on YouTube, podcasts, X (Twitter) spaces, newsletters, and blogging platforms, and it’s even better watching niche audiences growing around the content they produce.

It’s safe to say that developer content creation is officially a thing.

Dev-focused brands are noticing

For devtool companies and other developer-focused brands, this is a big deal. Collaborating with relevant content creators can be a great way to push tools or products to a technical audience in an authentic, organic way. The ability of these creators to speak with clarity, authority, and consistency about their areas of expertise makes them trusted advisors to the people who consume their content and a valuable resource to the companies who want to promote their dev-focused products.

So, there are more developers creating content, and more dev-focused brands looking to collaborate with the right content creators.

The problem is that it's hard for these two groups to find each other.

And that’s exactly why we’ve launched influencer.dev.

A marketplace dedicated to dev content creators.

There are lots of generic “influencer marketplaces” out there, servicing everything from clothing brands to food products to medical equipment.

But generic solutions don’t work for developers.

So I’m building a directory dedicated entirely to developers. Legit developer content creators can showcase their work and their expertise so that others in the community can easily find people to follow, learn from, and collaborate with.

Currently, there’s no cost and no strings attached. It’s simply the resource I wish I had found a year ago, and I hope this will bring value to all sides of the marketplace.

How it works

The platform is really simple, by design:

- If you create content for developers: get listed on the site. It’s free. Just fill out the application form with your details. We review each applicant to keep the list high-quality and spam-free. Once you get approved you’ll get your very own showcase page.
You’ll also be invited to join our Discord community (launching soon) and gain access to upcoming events and additional resources for improving your content strategy and overall brand-building.

- If you’re a dev-marketer or dev-focused brand: sign up (for free) to receive updates and to tell us about upcoming projects and job opportunities you’re trying to fill. We’ll circulate your offers to our creator community to help you find the right folks, quickly.

- If you’re a curious developer: Browse our list to find new voices to learn from and follow.

"Sounds cool. But I probably don't have enough followers!"

Just to be clear - audience size doesn’t matter and we don't care how many followers you have. Our goal is to help promote authentic, quality content creators at all stages of their journey. So as long as you can demonstrate that you are publishing quality, technical content for a technical audience under your own name, we'd be thrilled to include you in our showcase.

To keep things simple, you’re eligible to get featured in our directory if you check the following boxes:

✅ You are currently and consistently creating quality content for developers (you need to be able to show off your work to other people)

✅ You have specific technical areas of expertise that you focus on with your content

✅ You publish your content on mainstream platforms under your personal name/brand (and not only as a ghostwriter)

✅ You are open to working with dev-focused brands/companies if the right partnership presents itself

So what's next? How can I join?

I'm grateful for the early feedback and the offers I've received from the community to help/collaborate on this.

We already have some very impressive creators on the platform (including @pradumnasaraf @bretfisher @andrewbaisden @anmolbaranwal @francescoxx @sauain @code42cate and more!) - we're just getting warmed up...

Here's how you can get involved:

If you're creating content, join the platform!
If you're a dev marketer or a dev-focused company, introduce yourself so we can help
Follow us on X
Follow us on LinkedIn
Contact me and share your ideas and suggestions

👀 Under the Hood at DevHunt 🚀

Zevi Reinitz — Tue, 26 Dec 2023 07:36:33 +0000

The Challenge of Launching DevTools

One of the unique challenges for any DevTools company is finding the right platforms for launching the product.

There are many places to launch products in general, but DevTools by definition have a unique audience and that renders many of the standard launch platforms less relevant and less effective.

That's why I was pleasantly surprised when I discovered DevHunt - a product launch platform built by developers for developers, focused solely on launching DevTools to a relevant audience.

Launching Livecycle on DevHunt

In my experience, the best way to learn about a new platform is to use it myself. And the second best way is to speak to the founders directly about what motivated them to build it in the first place.

So this week, I'm checking both of these boxes at the same time:

Livecycle is Live on DevHunt this week (🚀🚀Shameless plug... please upvote Livecycle on DevHunt!!🚀🚀)
I reached out to DevHunt founder John Rush to learn more about his career and his motivation for building a dev-centric product launch platform.

This is the first installment of a launch-in-public diary that I'll be sharing so that other dev tools companies can (hopefully) learn and benefit from our experience.

My Conversation with DevHunt Founder John Rush

How did you get started as a developer?

I was building electronics since I was 5 years old and started coding when I was 12. I also studied computer science so I’m a typical coder who did it since he remembers himself.

You clearly have a lot of product ideas and you’ve built a bunch of them… How do you decide when an idea is good enough to actually build?

I only build stuff I really wanna use myself, but can’t find anything on the market that suits my needs 100%.

What does your early go-to-market process look like? How do you start promoting the product to developers and get those first 100 users?

I use X a lot. Trying to make a viral tweet that’s not a promotion, but indirect promotion. I post on Hacker News, Hackernoon, Devto, Product Hunt, Dev Hunt and 100 more directories.

Why did you decide to build DevHunt? What makes it unique?

Product Hunt is a closed company. They have no dialog with the maker community. This is unacceptable for such a platform. Everyone complains, including me. This leads to issues, often we see products cheating there. The last drop for me was when I got the #2 spot of the day because the top product was cheating with fake upvotes, it seemed obvious based on indirect metrics (such as upvote speed). That day I decided to make Dev Hunt and make it 100% open and transparent. The community loves it. We won PH product of the day and we have grown every week since the launch.

Can you give some tips on how developers can get the most out of a DevHunt product launch?

Promote it on social media, direct messages to friends, blog posts and add the Dev Hunt banner on your site. If all 15 tools do that, it means we merge all audiences and actually cross-promote these products. On top of that, the generic Devhunt audience checks all the tools. So in total, these actions create great traffic.

Beyond the initial launch, winning on DevHunt means you stay on the home page for years. This is so valuable for a brand and traffic, I can’t even describe it. Your tool is among the best tools in a short list visible all year long, every day to every visitor of DevHunt.

Can you share an epic failure you experienced as a developer? What did you learn from it?

Every time I put too much effort and time into coding a product, it fails. There is one product we spent almost a year building and when we launched, we got 0 users, because users didn’t really need it. We closed down that company later.

Building and testing so many products requires a lot of positivity and optimism. How do you maintain a positive perspective even when things seem to be going wrong?

I’m an optimist by nature. I think founders must be optimistic. If not, I’d rather not start a business, because almost everything I do fails, and almost every decision I make is wrong, but sometimes I’m right and sometimes my products are useful, these moments make me happy enough to go grind further forever.

Tell us about a new project you're excited about or something new you're learning

My goal for 2024 is to have 100 projects launched in total. I am at 20 now. So I need to launch 80 more. The one I’m working on right now is a tool to make websites/directories/CVs/roadmaps out of Google Sheet or Notion. Super simple. No advanced cms. Also I’m launching indexgoogle.com this week and listingbott.com next week.

What is the best piece of advice you’ve ever received?

Kill your EGO

More About John Rush

Bio:
16 years in the startup world. 25 failures. 4 successes in VC funded startups. Pivoted into the bootstrapped indie world in 2023.

20+ projects:
Marsx.dev, Unicornplatform.com website builder, Devhunt.org Open Source PH alternative for dev tools, SeoBotAI.com SEO on 100% autopilot, zero actions needed), Listingbott.com lists a tool on up to 1000 directories with 1 click for traffic/backlinks, AllGPTs.co most popular custom GPT directory in the world, filmgrail.com cinema SaaS platform - powers cinemas on all continents, processing over $50M in ticket sales a year, lorem.space image placeholder api, marketsy.ai **e-commerce and marketplaces powered by AI, **uigenerator.org generate UI mockups for your website, cofondr.com cofounder as a service for busy solo makers, indexgoogle.com index your new pages really fast, in just hours, saasemailer.com dead simple emailers/CRM for solo makers, nextjsstarter.com directory of all NextJS starters and boilerplates, startupstools.com startup tools used by famous makers, osssoftware.org vetted OSS alternatives for the tool you pay for, My newsletter >>> 100xfounder.beehiiv.com

Marketing Tips for Developers 💡

Zevi Reinitz — Mon, 20 Nov 2023 21:46:13 +0000

TL;DR

I'm an experienced dev marketing leader
I'm launching a new content series to show developers the marketing skills they can learn/improve to make them more successful
You're invited to follow along and enjoy.

Developers hate marketing.

That's why there's so much content by dev marketers showing other dev marketers how to promote dev-centric stuff without annoying the technical audience in the process.

It's probably also why there's very little such content for developers themselves, showing them how to improve and leverage their own marketing skills. After all, why in the world would a developer need to know anything about marketing?

But this is a misconception.

Because like it or not, these days, we are all in marketing (yes - even you).

A few quick examples that might sound familiar:

Are you an open-source developer trying to get contributors for your new project? You'll need some marketing skills for that.
Trying to make your portfolio/CV stand out so you can land a job? Here too, you'll need marketing.
Want to publish more content and build some domain authority? Yep. Marketing.
Want to grow and monetize your social presence? Maybe become a DevRel one day? You guessed it. Marketing.

In my experience and IMHO, improved marketing skills will move the needle for virtually any developer at any level.

I show developers how to become good marketers.

For the past 2+ years, I've led go-to-market efforts at Livecycle - a dev-focused company solving the 'endless feedback loop' problem with tools that enable developers to share work instantly and collect feedback in context.

At this point, I have a ton of experience - not only in marketing to developers, but also in coaching developers on how to become natural marketers themselves.

The opportunities I've had to share relevant marketing insights, strategies, and tactics with the dev community have been so impactful that I've decided to open it up to a wider audience through this content series - "Marketing for Developers".

Some of the topics I'm planning to cover:

Developing a personal brand
Product launches for dev-oriented products
How to increase traction for your open-source project
How to grow and leverage your social media presence
How to improve your content creation and distribution
How to send cold emails to developers without getting hate mail in return
And much more...

Feel free to follow me here. You can also subscribe to the email list and get more detailed and exclusive content about these topics.

And if there are specific questions or topics you'd like me to address, please reach out or drop them in the comments below.

Speed Up Hackathon Collaboration 🏃🤝

Zevi Reinitz — Sun, 12 Nov 2023 12:11:21 +0000

The 2023 Docker AI/ML Hackathon

Docker recently completed their AI/ML Hackathon. Participants were encouraged to build solutions that are innovative, applicable in real life, use Docker technology, and have an impact on developer productivity.

Eligible submissions could also include non-code proof-of-concepts, extensions that improve Docker workflows, or integrations to improve existing AI/ML solutions.

All submissions were AI/ML projects or models built using Docker technology and distributed through DockerHub, AI/ML integrations into Docker products that improve the developer experience, or extensions of Docker products that make working with AI/ML more productive.

Optimizing Hackathon Speed and Productivity

Most hackathons begin and end with a simple directive - participants build something and submit it before the deadline.

But in this year's AI/ML Hackathon, Docker took things a step further. Participants were treated to a wide range of sessions focusing on helping participants build higher-quality products.

And in this context, we were thrilled that Docker asked us to present our Livecycle Docker Extension as a tool that Hackathon participants can use to achieve a blazing-fast collaborative experience. Instead of getting held back by staging servers and CI builds, the Livecycle extension lets teams share the latest changes with one another instantly, while code is still sitting on your local development environment. And with the built-in collaboration tools, Hackathon Squads can save tons of time building great products with the Livecycle extension.

Check out the complete session (given by our CTO @yshayy) on how to use the Livecycle extension for Hackathon collaboration:

And check out the Livecycle Extension here.

DEV Community: Zevi Reinitz

Top 5 Elasticsearch Consulting Companies in 2026

How We Selected These Firms

Comparison Snapshot

Top Specialized Elasticsearch Consulting Firms

Top Global IT and Business Consulting Firms for Elasticsearch

Common Use Cases for Elasticsearch Consulting

Example: Automation and Optimization Through Pulse

FAQs

Final Thoughts

Wix’s xEngineer Is Changing The Definition of "Shift-Left"

Wix’s Big AI Engineering Announcement

Why This Is Bigger Than Just Wix

Where This Shift Shows Up First

What Wix’s Announcement Actually Signals

How xEngineering Reframes Shift-Left

What AI Actually Changes for DevOps and SRE Teams

Why This Resonates With Us at Pulse

Build an AI Agent And Win 💸

Announcing The "Agents Showdown"

Overview

The Bounty

Judging Criteria

Eligibility and How To Enter

Developer Resources

3 Issues That Remote MCP Developers Should Avoid

1. OAuth redirects only work on localhost

2. Missing .well-known OAuth metadata or misconfigured tool discovery

3. Unreliable server availability

The Good News: Testing is Easy With Portia

A Bit More About Portia

[Boost]

Celebrating The Top Search-Tech Voices for 2025 🏆

Finding Search Tech Industry Leaders

Why We Put This List Together

How Do We Decide Who Makes the List?

How to Nominate Someone to Get Featured

Check this out..

💡 The Untold History of GitHub Awesome-Lists 🤯

Zevi Reinitz ・ Jan 22

💡 The Untold History of GitHub Awesome-Lists 🤯

My Progress From Consumer → Maintainer

Researching the Origins of awesome-lists

Where it All Began

Early Traction

The Wild Summer of 2014

Awesome-lists Filled With awesome-lists

Awesome-lists Become a “Thing”

What Caused the Wild Summer of 2014?

Balancing Scale and Quality

Why “awesome”?

Closing Thoughts

The world's first directory for dev content creators

Introducing influencer.dev

Developer content is officially a thing

Dev-focused brands are noticing

A marketplace dedicated to dev content creators.

How it works

"Sounds cool. But I probably don't have enough followers!"

So what's next? How can I join?

👀 Under the Hood at DevHunt 🚀

The Challenge of Launching DevTools

Launching Livecycle on DevHunt

My Conversation with DevHunt Founder John Rush

How did you get started as a developer?

You clearly have a lot of product ideas and you’ve built a bunch of them… How do you decide when an idea is good enough to actually build?

What does your early go-to-market process look like? How do you start promoting the product to developers and get those first 100 users?

Why did you decide to build DevHunt? What makes it unique?

Can you give some tips on how developers can get the most out of a DevHunt product launch?

Can you share an epic failure you experienced as a developer? What did you learn from it?

Building and testing so many products requires a lot of positivity and optimism. How do you maintain a positive perspective even when things seem to be going wrong?

Tell us about a new project you're excited about or something new you're learning

What is the best piece of advice you’ve ever received?

More About John Rush

Marketing Tips for Developers 💡

TL;DR

Developers hate marketing.

I show developers how to become good marketers.

Speed Up Hackathon Collaboration 🏃🤝

The 2023 Docker AI/ML Hackathon

2. Missing `.well-known` OAuth metadata or misconfigured tool discovery