Site Architecture

A plain-language overview of how FindMyJob is built and where your data goes.

Last updated: September 2026. This is a safe, public-level description — internal operational details are not published.

What you use: the web app

A single-page web application that runs in your browser. Every page you see — search, profiles, job posting, dashboards — is this app talking to our backend over HTTPS.

Where data lives: a managed backend

All records (accounts, profiles, job listings, messages, subscriptions) are stored in a managed cloud database with per-record access rules. For example, the database itself — not just the interface — enforces that only you can edit your own profile, and only you can read your messages.

Application logic: serverless functions

Anything sensitive or complex — payment checkout, payment fulfillment, contact form delivery, candidate search gating, resume parsing, and admin statistics — runs in server-side functions that we control and that validate every request.

Payments: Stripe

Checkout is hosted by Stripe. After a successful payment, Stripe notifies our backend, which re-verifies the payment with Stripe before unlocking the purchased feature. Subscriptions can be canceled anytime from your account settings.

AI features: language models

AI match scoring, resume polishing and tailoring, and skill extraction send only the inputs needed for the request (e.g., your resume text or a job description) to a language-model service. Aggregated job listings are collected from public web sources and always attributed to their original source. We never send one user's private data into another user's requests.

Automation: scheduled jobs

Automated daily processes expire job listings past their post date, send saved-search job alert emails to premium members, and run a site health check. Failed processes never silently delete or modify data.

What we deliberately leave out of this page

Internal endpoints, infrastructure details, monitoring thresholds, and anything that would help an attacker. If you need more technical detail for a legitimate reason (e.g., a partnership or security review), contact us.