Next Mission Group Chrome Extension

I built an MVP Chrome extension for Next Mission Group around a concrete product problem: making military experience legible to civilian hiring workflows in real time—not as a one-off résumé rewrite, but in the browser, on the same pages where veterans already search and apply.

The work combined product flow, ontology design, heuristic scoring, LLM-assisted narrative, and production auth/API choices (Manifest V3, JWT connect flow, secrets kept off the client).

Highlights

• Manifest V3 extension with a side panel UX: sign in, maintain a profile, open a supported job posting, run a fit analysis, save results, and leave feedback.
• Job-board coverage for the MVP path: detection and parsing on LinkedIn, USAJOBS, Workday, Greenhouse, and Lever (with a pattern for adding more hosts).
• Ontology-backed mapping between military roles, civilian occupations, and transferable skills—separating a canonical backbone from an inferred layer so LLM suggestions can be reviewed and traced.
• Backend on Wix Velo for the MVP operational path: member auth integration, server-side API routes, and Wix Secrets (or env vars locally) so provider keys never ship in the extension bundle.

Problem

Military experience often does not align with how civilian roles are written: different vocabulary, credential expectations, and occupational categories. Veterans may be strong fits for a posting while still looking “off-profile” to both applicants and automated systems. The goal was to shrink that gap at the moment of job evaluation—not only after the fact on a separate site.

User flow

1. Install the extension and open the side panel.
2. Connect via the short-lived JWT flow tied to Wix Members (extension behaves like a first-party client without embedding API secrets).
3. Sync or edit profile data used for matching (roles, skills, history—details governed by product spec).
4. Navigate to a supported job posting; the extension detects the page type and extracts structured signals where possible.
5. Request an analysis: ontology + scoring produce an interpretable match; LLM copy is used where it adds explanation, with guardrails and provenance in mind.
6. Save outputs and optionally submit feedback to improve mappings and messaging over time.

Architecture (high level)

Security and operations

• No long-lived API keys in the browser; privileged calls go through your backend.
• JWT-based connect aligns the extension with the same membership model as the main site.
• Provider keys live in Wix Secrets (or local env for development), consistent with a path toward harderening for review / pilot.

Outcomes

The MVP establishes an end-to-end path: install → connect → profile → analyze → save → feedback, with documentation for ontology growth, human review of inferred edges, and broader military–civilian coverage over time. Quantitative pilot metrics (activation, analyses per user, qualitative hiring outcomes) can be layered in as releases move beyond internal and friendly-user testing.

Demo

MP4 (recommended) — Put your file in this same folder as index.md, e.g. content/work/next-mission-group-extension/demo.mp4. Optional poster image: demo.jpg (same base name; used as the thumbnail before play).

You can use any filename: change src above to match. Files in assets/media/ also work (use a path like my-folder/recording.mp4). A direct HTTPS link to an .mp4 works as src too.

YouTube — If you prefer, set demo_youtube_id in the front matter (the v= ID only) and uncomment the line below; remove or comment out the video shortcode above to avoid two players.

GitHub

Your public links entry points to github.com/londeree4. When the extension (or a mono-repo) is published under your account or an org, add a second code link in front matter with that repository URL so the header shows Extension source alongside GitHub profile.

Tools

JavaScript, Chrome Extension APIs (Manifest V3), Wix Velo, JWT auth, ontology modeling, heuristic scoring, LLM integration, product and architecture documentation.