feat: [GSSoC-2026] Chrome Extension for Auto-Filling Job Applications (L3)

[deekshinowdu-collab]

Feature Request: Auto-Fill Chrome Extension

Background Context

Currently, the Auto-Fill Tool provides a stellar client-side resume builder and PDF parser. However, to fulfill the project's core namesake—Auto-Filling applications—we need a companion browser extension.

We have bootstrapped a Manifest V3 extension boilerplate in the /extension folder of the repository. This issue is to help expand it and map form inputs on key job boards (e.g., Greenhouse, Lever, Workday) using the parsed resume JSON schema.

---

What needs to be done:

1. Visuals & Icon Asset (Easy - L1)

• Design and integrate standard brand extension icons (16x16, 48x48, 128x128 png images based on the website logo) into /extension/ and configure them in /extension/manifest.json.
• Enhance CSS elements in popup.html to align with the core website aesthetics (fonts, colors, and layout spacing).

2. 🔌 Auto-Fill Fields Expansion (Medium - L2)

• Update /extension/content.js to parse more fields like Education history, Projects, and Work experience descriptions.
• Add regex selectors to correctly identify and inject inputs in common Application tracking systems (ATS) like Greenhouse, Lever, Workday, or Ashby.

3. Seamless Local Storage Integration (Hard - L3)

• Enable the extension to automatically detect when the user is on the Next.js web application and pull the active resume data from localStorage or Redux state. This saves the user from having to copy-paste their JSON structure manually.

---

Boilerplate Files in Repository to Reference:

• extension/manifest.json — Declares permission scopes and content scripts.
• extension/popup.html — Pop-up user interface panel.
• extension/popup.js — Saves data and triggers communication messages.
• extension/content.js — Logic injected into job portals to read inputs and set values.
• extension/README.md — Sideloading instructions for developers.

---

Contribution Guidelines

• Create separate PRs for sub-tasks if you want to keep them focused (e.g., separate PRs for "Add Icons", "Greenhouse mapping", "Lever mapping", etc.).
• Ensure your code does not run external API calls (respecting 100% privacy).
• Verify the extension sideloads without compilation errors in Chrome.