Backend Engineer, Integrations

The mission

Awasi finds out which apps, agents, and integrations have access to a company's systems, then puts the controls in plain English in Slack. None of that works without integrations that are complete, current, and safe to act through.

• You will own that layer: the connectors that discover access across Google Workspace, Slack, GitHub, Notion, and Linear, the sync that keeps the picture current, and the actions that revoke a grant or lock an account when someone says so.

What you will do

• Build and own the connectorsDesign and ship the integrations with Google Workspace, Slack, GitHub, Notion, and Linear: OAuth flows, admin APIs, audit logs, and webhooks. Every one of them has quirks; you will learn them and encode them so nobody else has to.
• Discover OAuth and agent accessEnumerate third-party apps, service accounts, bot users, MCP connections, and AI agents, and normalise what each one can reach into a single model of access that the rest of the platform can reason about.
• Keep the picture currentBuild the sync engine: incremental polling, webhook ingestion, rate-limit handling, backfill, and reconciliation, so a new grant shows up in minutes and a revoked one disappears.
• Make actions safeImplement revoke, suspend, and lock actions as idempotent, auditable operations with dry runs and rollbacks. A founder typing "revoke Gavin's AWS access" in Slack is trusting this code.
• Watch email access continuouslyDetect forwarding rules, delegated mailbox access, and suspicious grants as they appear, and raise them with enough context to act on in one tap.
• Handle credentials properlyDesign token storage, rotation, and least-privilege scopes for every provider. Secrets never touch a log line.

What we are looking for

• Integration scar tissue4+ years shipping production backends, with real time spent inside third-party APIs: OAuth 2.0 and OIDC, pagination and rate limits, webhook verification, partial failures, and vendor APIs that change under you.
• Python fluencyComfortable in a modern async Python codebase with typed models, background workers, and Postgres.
• Identity and access literacyYou know the difference between a scope, a role, and a grant, and you can read a SaaS admin API and tell which of them it actually exposes.
• Care for correctnessYou write idempotent operations by reflex, think in terms of reconciliation rather than one-shot sync, and test the failure paths first.
• Bias for shippingYou would rather get one connector complete and trustworthy this week than five half-done by the end of the quarter.

Bonus points

• You have built on the Google Workspace Admin SDK, the Slack platform, or the GitHub Apps API before.
• Experience with SCIM, directory sync, or identity providers like Okta and Entra.
• You have shipped an MCP server or client, or wired AI agents up to real tools in production.

Who will thrive here

• The completionistYou are not done when the happy path works. You are done when the connector handles every account shape you can find and fails loudly on the ones you cannot.
• The translatorYou turn five vendors' five different ideas of a permission into one clear model and can explain it to a founder in a sentence.
• The operatorYou like owning something end to end, from the OAuth consent screen to the alert that fires in Slack.

About Awasi

Awasi is a venture-backed startup building a different kind of security company — one that gives high-growth teams the freedom to build with AI and the security to put it to work.

• We are a small, high-intensity team based in San Francisco and backed by some of the best builders in the valley.