Developers for MongoDB® databases

Hire developers
who fit your team

Tell us what you need, and within 48 hours we’ll introduce developers for MongoDB® databases, 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 data, the apps that read it, 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

Data models, queries, upgrades, and the replica sets behind them.

Data models

Documents shaped by how each screen reads them, with rules on each collection.

Queries and indexes

Indexes matched to each query, the slowest found with the profiler, and their plans read.

Aggregations

Reports built as aggregation pipelines, run where they don’t keep the app waiting.

Upgrades

One major version at a time, every driver checked first, each step tried on a copy.

Replica sets and backups

Members kept in step, the switch rehearsed, and restores tried on a schedule.

Shards

Collections spread across shards by a key chosen from how the app reads and writes.

Moves

Data brought over from the database you have now, one collection at a time, each result checked against it.

Planning a new data model, or a bigger move? 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 deployments together, from the data models and the queries to the replica set, the backups 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 add rules to collections that already hold years of documents?

Yes. They add each rule so it notes what doesn’t fit before it refuses anything, fix the documents it finds, then turn refusing on.

Can they keep our reports from slowing the app?

Yes. They build each report as an aggregation pipeline with indexes that fit it and, where a report can read data a moment behind, run it on a secondary member set aside for reading, so the app’s own reads aren’t kept waiting.

Can they spread our data across more servers when one isn’t enough?

Yes. They choose a shard key from how your app reads and writes, try it on a copy first, and spread the collection a step at a time.

Can you take on the whole project instead?

Yes. That starts with a written review of your deployment, its busiest collections and the queries that matter, and a proposal for a first step, such as one collection reshaped around the screen that reads it most.

Engineering

MongoDB® is a registered trademark of MongoDB, Inc. Webair is independent of MongoDB, Inc., and isn’t sponsored by, endorsed by or affiliated with it.

Let’s build it better

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

Thanks, we’ll be in touch soon.

{{ ctaStatus }}