Developers for Apache Kafka®

Hire developers
who fit your team

Tell us what you need, and within 48 hours we’ll introduce developers for Apache Kafka®, matched to your work, so you choose who joins your team.

Thanks, we’ll be in touch soon.

{{ heroStatus }}

You’re in good company

A few of the companies we’ve worked with.

How hiring works

From the first call to their first day, you decide each step.

  1. You tell us.

    Tell us about the work

    A short call about your events, the apps that write and read them, and who you need. The first call is free.

  2. We introduce.

    Meet developers matched to it

    Within 48 hours, we introduce developers whose experience fits, with the work each has done.

  3. You choose.

    Choose who joins

    You talk to each one and decide who starts.

  4. They start.

    Start on a date you agree

    They join your team in your tools, and work in your time zone.

What they work on

Topics, consumers, connectors and upgrades, and the clusters behind them.

Topics and keys

Partitions, keys and retention chosen from how each topic is read.

Producers and consumers

Writes confirmed by the copies they need, readers that keep up, and their lag watched.

Connectors

Data moved between the cluster and your databases, each connector watched.

Stream processing

Apps that count, join and check events as they arrive.

The metadata move

Clusters moved from Apache ZooKeeper™ to KRaft, the way Apache Kafka now keeps its metadata, rehearsed on a copy first.

Upgrades

Brokers, controllers and clients moved to a supported release, a step at a time.

Access and monitoring

Encrypted connections, rights for each app, and alerts that say what to check.

Planning a new event stream, or a bigger move? Event streaming engineering

Ways to hire

One developer

Full time, by the month, working as part of your team.

A small team

Developers who look after your clusters together, from the topics and the consumers to the connectors, the access and the next upgrade.

How each is paid for: PricingWhen each way of working fits: Engagement Models

Working in your team

They work the way your team already does.

  • Your tools. Your own chat, tickets and code repository, so you see the work as it happens.
  • Your hours. They work in your time zone, on hours you agree before anyone starts.
  • Your access. You decide what they can reach, and remove it when they leave.

Tell us who you need

A few details are enough to start. We’ll reply by email to arrange a short call.

What should they work on?

{{ eWork }}

How many developers?

{{ eDevs }}

When should they start?

{{ eStart }}

{{ eHName }}

{{ eHMail }}

{{ eHSend }}

{{ hireThanks }}

We’ll be in touch by email, and introduce developers matched to your request within 48 hours.

Questions worth asking

How soon can a developer start?

We introduce developers matched to your work within 48 hours. Once you’ve chosen, they start on a date you agree.

Can we interview them first?

Yes. You talk to each developer and choose who joins.

Will they work in our time zone?

Yes. They work in your time zone, on hours you agree before anyone starts.

What does it cost?

It depends on the experience you need and how long you need them. Your proposal sets out the monthly fee and how you pay before anyone starts.

Pricing

Can they tell why a consumer keeps falling behind?

Yes. They read its lag partition by partition, check how often its group rebalances and how long each event takes, then fix the slowest step first.

Can they control which apps read which topics?

Yes. They give each app its own sign-in and rights on only the topics it uses, and encrypt the connections between apps and the cluster.

Can they connect our databases to the stream?

Yes. They set up connectors that bring changes in and send events out, and watch each one so a stopped connector is noticed.

Can you take on the whole project instead?

Yes. That starts with a written review of your cluster, its busiest topics and the apps on either side of them, and a proposal for a first step, such as one consumer group brought back in step with its topic.

Event streaming engineering

Apache Kafka, Kafka, Apache ZooKeeper, ZooKeeper, Apache and the Kafka logo are either registered trademarks or trademarks of The Apache Software Foundation in the United States and other countries. Webair is independent of The Apache Software Foundation, and isn’t sponsored by, endorsed by or affiliated with it.

Let’s build it better

Tell us about your topics, the apps that write and read them and the work ahead, and we’ll introduce developers who can start there.

Thanks, we’ll be in touch soon.

{{ ctaStatus }}