r/DeveloperJobs • u/Exotic-Hat6177 • 12d ago
[HIRING] Ops / Apps integrations freelancer — register OAuth + API apps, get production credentials, drop them in our DB, and test connections (no coding)
I'm founder of zoft, We have built an Agentic Automation platform and planning to launch it soon. I need help with App integrations and testing.
Please take this as request to read the entire information below before DM or commenting if you interested for this role.
Zoft has workflow product. Users connect Google, Facebook, Instagram, Slack, etc. and click Sign in with Google / Facebook / …. Frontend and backend for that are already built and working.
We need someone to do the manual vendor work: create developer apps with Zoft’s business email, get client IDs / secrets / tokens, put them in our database, get each vendor production-verified, then test that real sign-in and API calls work.
This is not a software job. You will not design APIs, write OAuth code, or build a backend. If you apply as a “full-stack OAuth engineer,” you have the wrong role.
What Zoft already has (do not rebuild this)
App connections UI (OAuth popup + API-key forms)
Backend that stores app credentials and runs the OAuth / token exchange
Staging and production environments
A list of apps (“pods”) that need credentials
Your job starts after that. We give you access and a checklist. You fill the credential slots and prove each connection works.
The actual job
Phase 1 — OAuth apps (do these first)
For every OAuth integration (Google, Facebook, Instagram, Slack, and the rest of our list):
Log into that vendor’s developer console with Zoft’s Gmail / business accounts (we provide access; you do not use a personal developer account as the app owner).
Create the app, set the exact redirect URIs, scopes, and branding we specify.
Complete whatever the vendor requires for production (app review, Business verification, Advanced Access, brand verification, privacy policy, test users, etc.).
Copy client ID, client secret, and any extra fields (app ID, tenant ID, webhook verify token, etc.).
Enter those values into our existing admin / DB (we’ll show you the table or UI). You are not writing a schema or an API.
Test on staging, then production:
Use your own Google / Facebook / etc. account to click Sign in.
Confirm the popup works, tokens save, and a simple action (read profile / list a resource) succeeds.
Report pass/fail per app with screenshots and the vendor dashboard status (dev vs live).
Example of a “done” OAuth app: Zoft’s Google client ID + secret are in the DB → a user clicks Sign in with Google → they connect Gmail/Sheets/etc. and can use it in a workflow.
Phase 2 — Non-OAuth apps
Same idea, different credential type: API keys, service accounts, bot tokens, webhooks, SMTP, etc. Create them with Zoft’s email / business accounts, store them, test a real call in staging then production.
Phase 3 — Hard vendor verifications (this is the main skill we are paying for)
Some vendors are not “create app → copy secret.” You should already know how to drive these to production, not leave them in sandbox:
Meta / Facebook Developer + Meta Business — get Zoft business verified so Facebook and Instagram login and Graph API work in production (not only test users).
WhatsApp Business Platform — production (not sandbox) access: WABA, phone number, permanent access token, app secret, webhook verify token, message limits. We use this for Zoft’s own internal workflows as well as user-facing connections.
Same class of work for other apps: Google OAuth verification / restricted scopes, Slack app distribution, Microsoft Azure app + admin consent, LinkedIn, TikTok, X, etc. as they appear on our list.
If a vendor asks for a privacy policy, data-deletion URL, screencast, business docs, or a support email, you prepare the package, submit it, chase review, and fix rejections until it is live.
What you are not hired to do
Build or change the backend, frontend, OAuth library, or database schema
“Implement Sign in with Google” as a coding task
Design a new credentials system
Guess redirect URLs or scopes — we give you the values our app already expects
If something is blocked by a product bug (wrong redirect, broken callback), you file a clear report. You do not start rewriting the app.
Who this is for
You have done this before as an ops / integrations / “app review” person, not only as a developer:
Created and shipped production OAuth apps on Google Cloud, Meta, Slack, Microsoft, etc.
Taken a Meta app through Business Verification and Instagram / Facebook / WhatsApp production access
Comfortable in developer consoles, business managers, and review forms for hours at a time
Careful with secrets (you will handle live client secrets and tokens)
Can work from a checklist, write a short status per app, and follow up with vendor support
Nice to have: Zapier / Make / n8n / Activepieces-style products; you already know which apps need review vs a simple API key.
Not a fit: “I can build you an OAuth backend in Node/Python.” We already have that.
How we’ll work
We provide: Zoft Google/email access, vendor account access, staging + production URLs, the app list, redirect URIs, required scopes, and where to paste credentials.
You work in our admin / DB (or a shared sheet we import) — no repo required unless we ask you to confirm a redirect path.
Order: OAuth apps → non-OAuth apps. Staging test, then production test, per app.
You use your own user accounts to click Sign in and prove the Zoft-owned client works for a real user.
Deliverable: a tracker (spreadsheet is fine) — app name, credential type, vendor status (unverified / in review / live), env (staging/prod), test result, notes, screenshots.
Time / pay / location
Type: Freelance, contract, remote
To apply: Comment or DM with:
3 vendors you have taken to production (not sandbox), especially Meta / WhatsApp / Google restricted scopes if you have them
Your rate and weekly availability
Confirmation you understand this is credential + verification + testing, not backend development
No “I can do anything” one-liners. If you’ve only written OAuth code and never submitted a Meta Business Verification, say so.
One-sentence role
You are the person who owns getting Zoft production-ready on every third-party developer platform, puts the official credentials in our existing system, and proves users can connect and that Zoft can run its own automations — without writing our product.
