Job search
Build an Airtable Job Tracker That Links Each Interview to the Correct Application
Two completed fictional relationship and migration examples keep same-company roles separate, quarantine ambiguous links and verify the limits of the local fixtures.
Build the tracker around two different things: an application to a specific role and an interview belonging to that application. Give each application a stable identifier, then link every interview to the corresponding record. A company name alone is insufficient when you are applying to two teams at the same employer.
LandOffer publishes this guide and offers job-search tools. We checked Airtable’s public documentation on October 21, 2026, and created only local fictional CSV fixtures. We did not create an Airtable base, import records, connect a calendar or access recruiter information. Use jobs posted in the past 24 hours to discover opportunities, then keep each submitted application distinct in your tracking.

Model applications separately from interview events
In an Applications table, make one record represent one application to one role. Keep Company, Role, Applied date, Job posting URL and Application status there. Use a user-assigned Application ID such as APP-041 as a stable reference. This is your own identifier, not an Airtable internal record ID.
In an Interviews table, make one record represent one interview event. Store an Interview ID, Stage, Start, Time zone, Event status and a link to its application. An application can have several interviews; an interview in this design belongs to exactly one application. If the employer genuinely combines two processes, hold that exception for clarification rather than silently assigning the event to both.
These tables answer different questions. “Application submitted” describes the role-level process. “Technical interview rescheduled” describes an event. Updating an interview’s stage should not automatically mark the entire application successful or unsuccessful. Keep such decisions explicit unless you later design and verify a suitable workflow.
Airtable supports reciprocal record links. Use them to inspect the application’s interviews, then verify that individual records are actually connected.
Configure a helpful picker without treating it as a database constraint
In Interviews, add Link to another record, target Applications and name it Application. Turn off Allow linking to multiple records for that picker; retain multiple interviews on the application side.
There is a material limitation: Airtable’s relationship FAQ says that switch only restricts the record picker. Copy/paste and automations can still create multiple links, and switching the option off does not repair existing links. The design therefore needs an explicit review for missing or multiple application links; the setting is not a hard integrity guarantee.
Similarly, limiting the picker to a view is a selection aid, not a rule preventing every other record from being linked. Review actual links even when the picker shows only “Active applications.”
Add Company and Role as lookup fields in Interviews, using its Application link as the source. Airtable says lookups require both a linked-record field and actual record connections; an empty lookup can indicate missing links. A lookup is not a fuzzy company-name search, and typing a role into a separate text column does not create a relationship.
| Table | Field and proposed purpose | Review rule for this design |
|---|---|---|
| Applications | Application ID, used as the primary value | Keep it unique and stable by your own review |
| Applications | Company and Role | Describe this particular application |
| Interviews | Interview ID | Identify the event independently of its date |
| Interviews | Application, linked to Applications | Exactly one existing application before treating the event as ready |
| Interviews | Company and Role lookups | Inspect the linked application rather than maintaining competing copies |
| Interviews | Start, Time zone and Event status | Keep scheduling details separate from application outcome |
Worked relationship: two Rainbridge roles, three interviews
Jonah and the companies below are fictional. He has two applications at Rainbridge and one at Copper Fen. The identifiers are deliberately different even when the company is the same.
| Application ID | Company | Role | Applied date |
|---|---|---|---|
| APP-041 | Rainbridge | Backend Platform | October 1, 2026 |
| APP-042 | Rainbridge | Developer Tools | October 3, 2026 |
| APP-043 | Copper Fen | Data Engineer | October 4, 2026 |
His completed interview relationship map is:
| Interview ID | Application link | Stage | Role shown by the intended lookup |
|---|---|---|---|
| INT-501 | APP-041 | Recruiter screen | Backend Platform |
| INT-502 | APP-042 | Technical interview | Developer Tools |
| INT-503 | APP-041 | System design | Backend Platform |
APP-041 has two interviews, APP-042 has one and APP-043 currently has none. Zero linked interviews does not establish that an application was rejected or that an event is missing; it describes this fixture’s recorded relationships.
A naive rule that chooses the first Rainbridge application would attach INT-502 to APP-041, the wrong role. Our local fixture demonstrates this wrong-role join without accessing Airtable. The corrected fixture uses the explicit Application ID and returns Developer Tools for INT-502. Those local joins test the proposed relationship map, not Airtable’s lookup interface.
Jonah’s completed decision is to use the application identifier as the link target and verify the role beside every scheduled event. He does not duplicate the Rainbridge company label into a relationship rule or move both applications into one row. If the invitation contains only the company name, he marks the application association unresolved until his own application records or organizer clarification identify the role.
A confirmed time change belongs to the interview record, while its application association remains the same. Keep the same application relationship when the confirmed event is rescheduled, and update the event record or preserve a separate cancellation history according to your chosen tracking convention. A fresh Interview ID is appropriate for a genuinely different event, not merely because a date was corrected.
Worked migration: accept three rows and quarantine three
Jonah is migrating a small spreadsheet. He first puts the incoming interview data in a local staging CSV, leaving his intended application list unchanged. This is a completed fictional migration review; no data was imported into Airtable.
The file contains six rows: the three mapped interviews above, an identical second copy of INT-503, INT-504 pointing to nonexistent APP-999, and INT-505 containing both APP-041 and APP-042. We ran a local validator over these fixtures, preserving the original inputs.
| Incoming issue | Local decision | Reason |
|---|---|---|
| INT-501, INT-502 and the first INT-503 | Three rows ready for the next review step | Unique event, one known application reference |
| Identical second INT-503 | Quarantine the duplicate copy | Do not create a second event from the same input |
| INT-504 → APP-999 | Quarantine | Do not invent an application to satisfy the reference |
| INT-505 → APP-041 and APP-042 | Quarantine | The intended one-application relationship is unresolved |
The result is three ready rows and three quarantined rows, with a planned destination containing three application records plus three interview records: six records overall. The local files also check a conflicting duplicate: when two rows share an Interview ID but disagree on time, both are held rather than silently accepting the first. Duplicate Application IDs are rejected by the local validation as well.
“Ready” means the stated local checks passed. It does not mean an Airtable import, actual event confirmation or permission review succeeded. Jonah still needs to inspect the destination field mapping and establish real linked records before relying on lookup values.
The ready CSV preserves the Application ID and original local start value, then adds a UTC instant and clearly labelled local company/role check columns. Those derived columns are evidence from our local join; they are not Airtable lookup fields. When configuring your own base, keep the raw application reference available for reconciliation, create the actual links, and let the configured lookup provide the destination’s role value. A prefilled text column that happens to display Developer Tools would not demonstrate that INT-502 is linked correctly.
For the conflicting-duplicate check, one copy of INT-501 says 10:00 and another says 11:00 on the same date. Both are held. The validator cannot know which invitation is current merely from their row order. Jonah would compare the organizer’s confirmed update before accepting a time, while retaining the interview’s identity. This prevents an apparently successful deduplication from silently selecting the wrong appointment. No organizer was contacted and neither fictional row was written to a live tracker.
Keep the application reference as plain staging text until it is validated. Airtable documents that converting text to a linked field can create new records when values have no existing match. It also parses comma-separated values as multiple links during conversion. An unresolved value is therefore something to review before conversion, not an invitation to let the tool create a placeholder application.
The primary Application ID in this design is intentionally the reference value. If you replace that primary value with a decorative company-and-role label, reconsider how incoming references will match. A different display name in a picker does not change the matching behavior of every integration or surface.
Airtable’s general import workflow and its CSV import extension are separate features. The extension is documented for paid plans and can merge using a selected field; its matching and new-record behavior require review. This guide does not require that extension or assume it is included with Free. Start with deliberate linking and inspection before introducing an import automation.

Preserve the appointment’s time zone
An application’s Applied date can be date-only; an interview’s Start needs the intended time and zone. Keep the original invitation’s date-and-time wording available for comparison, without copying unnecessary private meeting credentials into every tracker field.
Airtable’s time-zone guide says dates are stored in GMT and can be displayed in each collaborator’s local zone or a common configured zone. Different field configurations can consequently display the same instant differently. Review the Start field’s settings instead of assuming that a visible clock time is universally interpreted.
For Jonah’s fictional fixtures, INT-501 is October 22, 2026 at 10:00 in America/Los_Angeles; the corresponding UTC instant is 17:00. INT-502 is October 23 at 14:00 in that zone, corresponding to 21:00 UTC. INT-503 is October 26 at 09:00, corresponding to 16:00 UTC. We checked those three conversions locally using the named time zone.
These checks apply to those stipulated dates, not a permanent seven-hour offset for every appointment. They do not confirm a real meeting or install a reminder. If the organizer reschedules, compare the new invitation, the intended time zone and the linked application before updating your own record.
Keep capacity and access decisions separate from linkage
The current Free plan documentation lists 1,000 records per base, cumulative across tables. Three hundred application records and seven hundred interview records would use that allowance before adding any other table records. In another fictional planning example, 250 applications, 600 interviews and 100 tasks total 950, leaving 50 records against that documented limit.
This is capacity arithmetic, not a promise that every other Free feature or limit fits your workflow. A first-workspace Team trial can expose capabilities that are not part of the continuing Free plan. Check the actual workspace plan before relying on an extension or paid configuration option seen during a trial.
Keep the tracker’s audience limited to its purpose. A public view link is not needed merely to maintain your own application/interview relationships. Airtable documents exceptions to hidden-field behavior in shared views, including grouping or calendar fields and an option to show all fields in expanded records. Hiding a recruiter-note column is not a substitute for reviewing the actual sharing configuration.
Finish with a small inspection routine: every ready interview has one known application, its looked-up role matches the invitation context, and its time is understood in the intended zone. Leave an interview unassigned and flagged for review until the application reference is resolved. The tracker supports your decisions; it does not replace employer confirmation. Continue your broader search through LandOffer.ai while maintaining that separation.
Sources and Further Reading
- Linking records in Airtable
- Relationship types and the single-selection setting’s limitation
- Lookup prerequisites and actual record connections
- Importing third-party data
- CSV import extension availability and matching
- Airtable plan limits and trials
- Time zones and locales
- View sharing and hidden-field exceptions