Developers for PostgreSQL® databases

Hire developers
who fit your team

Tell us what you need, and within 48 hours we’ll introduce developers for PostgreSQL® 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 database, the apps that use 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

Schemas, queries, upgrades, and the backups behind them.

Schemas

Tables, keys and constraints, each change reviewed and made in steps the app keeps running through.

Queries

The ones that take longest, found in the database’s own statistics, with their plans read and indexes added where they help.

Upgrades

Each minor release applied soon after it’s out, and every major version tried on a copy before the real move.

Backups

Continuous archiving kept running, and each backup restored to a server of its own on a schedule, timed.

Standbys

Replication kept in step, and the switch to a standby rehearsed.

Access

Each app connecting as its own role, rows kept to the customer they belong to where tables are shared, and every connection encrypted.

Moves

Data moved from the database you have now, table by table, each result checked.

Planning a new database, 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 databases together, from the schema and the queries to the backups, the standbys 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 find out why our database is slow?

Yes. They read the plans of the slowest queries from the database’s own statistics, add or change indexes where they help, and tune vacuuming for the busiest tables.

Can they test that our backups restore?

Yes. They restore your backups to a separate server on a schedule, write down how long each took, and fix what doesn’t come back.

Can they change our schema without stopping the app?

As far as each change allows, yes. They plan each change in steps that keep the app running, build indexes without blocking writes where PostgreSQL offers it, and try each step on a copy first.

Can you take on the whole project instead?

Yes. That starts with a written review of your database, its backups and the queries that matter, and a proposal for a first step, such as a restore to a separate server, timed.

Engineering

Postgres, PostgreSQL and the Slonik Logo are trademarks or registered trademarks of the PostgreSQL Community Association of Canada, and used with their permission. Webair is independent of the PostgreSQL Community Association of Canada and the PostgreSQL Global Development Group, and isn’t sponsored by, endorsed by or affiliated with either.

Let’s build it better

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

Thanks, we’ll be in touch soon.

{{ ctaStatus }}