Back to jobs

Build & maintain a small Google Cloud email-processing service (Gmail API + Anthropic API)

Search - API Integration · local_filter_skipped · UID ~022081765142472683122

Open Job

Job Details

Budget $? - $?/hr
ExperienceIntermediate
DurationUnknown
Weekly hoursMore than 30 hrs/week
Client countryAbout the client
Proposals20 to 50
Interviewing1
Invites sent0
First seenTue, Jul 28, 2026 10:51 AM
Last seenWed, Jul 29, 2026 12:47 AM

Description

Summary We have a fully scoped, documented build for a small always-on service and need a mid-level backend/cloud developer to build it and stay on to maintain it through to early 2027. The design is done — this is build-to-spec, not a discovery project. A detailed technical spec is available to shortlisted candidates. What it does: watches a shared Google Workspace mailbox via the Gmail API, reads PDF attachments, calls the Anthropic API to draft replies, places those drafts back in the mailbox for human review, sends instant acknowledgements for certain emails, logs everything to a Google Sheet, and monitors itself so we're alerted the moment it fails. Runs on: Google Cloud Run, triggered on a timer, secrets in Secret Manager. Scale: ~200 users across several client organisations, low weekly usage. Low traffic, but a live production service with real client commitments — reliability and fast recovery matter more than raw performance. Two things we care about most, because they're where this kind of build usually goes wrong: Auth. The service authenticates to a shared mailbox across two separate Google Workspace tenants, so domain-wide delegation is not available. Silent failure. We must be alerted when the service quietly stops working — e.g. the Gmail auth expires and emails stop processing with no error. We own the content and logic that goes into the AI calls, and all client relationships — you never need to understand our subject matter. You own the service itself: build it to spec, and stay responsible for fixing it when it breaks while it's live. Please answer the screening questions — we read them carefully and they matter more to us than the headline price. Budget: fixed price, paid by milestone. Propose your milestone breakdown and price against the scope above; full spec shared before we award. Ongoing support: please also quote a separate arrangement for outage response once live (retainer, on-call, or per-incident) with an expected response time. A build without this doesn't meet our need.

Skills

API Integration Python Google Cloud Platform Cloud Run OAuth Google Workspace

Notification History

ChannelTypeStatusSentError
No notifications.

User Actions

ActionActed at
No actions.