Job search
GIS Portfolio for Applications: Tell a Spatial Story and Verify Every Shared Layer
Show your spatial reasoning through a coherent StoryMaps project, explain data and method limits, and verify the audience of every shared dependency.
Give a GIS portfolio a clear spatial question, explain how the data and analytical choices answer it, and verify that the intended reviewer can open its dependencies. An ArcGIS StoryMaps page should let a reader follow your reasoning without guessing which layers are missing or which conclusions the data cannot support.
LandOffer publishes this guide and offers job-search tools. We reviewed public Esri documentation on October 22, 2026; we did not publish a story, change permissions or test a private ArcGIS account. The examples below use invented places, counts and item labels. Compare recent roles on LandOffer to choose a project question relevant to the work you want to demonstrate.

Give the portfolio a question with a defensible answer
Start with a question narrow enough to explain on one opening screen. “Which inventory zones still need condition checks?” is more useful than “My GIS projects.” It establishes a denominator, a comparison and a possible next action. It also gives the reviewer something concrete to challenge: what counts as checked, where did the inventory come from, and why are those boundaries appropriate?
Choose a question that makes your own contribution visible. If you cleaned attributes, reconciled duplicate records and selected a classification, explain those steps. If a teammate designed the survey or supplied the geometry, credit that work. A sophisticated map borrowed from a class project does not establish that you designed its analysis.
Plan the reader's path before arranging visual blocks. Open with the question, introduce the inputs, show the method and result, then explain what would change your interpretation. Give the map a specific job in that sequence so a reviewer can locate your analytical contribution without searching through a general career biography.
Write captions that carry meaning even before the interactive element loads. Name the comparison, observation period and missing-data rule in ordinary language. Make the exact values available in a readable table or narrative, and explain the legend without relying on color alone. If the display has several selectable views, say which question each view answers. A reviewer should be able to understand the main finding without discovering a hidden control or reproducing your entire workflow. This also gives you a concise explanation to use when discussing the project aloud.
For an application, connect this project to a responsibility in the posting: data stewardship, spatial analysis or communicating an operational finding. Name the tools you actually used, then spend the space explaining the GIS decisions that changed the answer.
Keep a source record for every analytical input
Record each dataset's owner, item identity, coverage period, retrieval date, relevant fields, coordinate system and permitted use. Separate the date the data describes from the date you downloaded it. A recently updated item page can still contain older observations.
Esri's item-details documentation identifies descriptions, terms, credits, owners, IDs and sharing levels as useful item information. Sublayers can carry their own sources and metadata. Open those details when a service contains several layers; a useful parent title does not resolve the provenance of every component.
In your project notes, distinguish copied attributes from derived fields. Define a derived percentage with its numerator and denominator. Describe exclusions and missing values before presenting a comparison. If you joined points to polygons, explain the boundary rule and how unmatched or duplicate records were handled. Do not claim a spatial join when you only received an already aggregated table.
Use a representation suited to the question. Normalized percentages can answer a coverage question; raw counts answer a workload question. They may rank areas differently. If distance or area matters, justify the coordinate system and method instead of treating a basemap's appearance as analytical evidence. No amount of attractive symbology repairs an undocumented denominator.
Worked spatial story: an incomplete bench inventory
This completed specimen is entirely fictional. Leila wants to demonstrate how she explains a data-quality problem. She creates four imaginary inventory zones and supplies the following aggregate counts herself. There are no real locations, field visits or residents. The calculation is ordinary arithmetic on a toy table, not a tested ArcGIS analysis.
Project question: Where should the next round of inventory verification begin, if the immediate goal is to reduce the number of benches without a recorded condition check?
| Invented zone | Listed benches | Recorded checks | No recorded check | Coverage |
|---|---|---|---|---|
| A | 30 | 24 | 6 | 80% |
| B | 20 | 8 | 12 | 40% |
| C | 40 | 32 | 8 | 80% |
| D | 10 | 6 | 4 | 60% |
| Total | 100 | 70 | 30 | 70% |
Her calculation defines unchecked inventory as listed benches minus recorded checks. Coverage is checks divided by listed benches. Zone B therefore has 20 − 8 = 12 unchecked records and 8 / 20 = 40% coverage. Across all zones, 70 / 100 = 70%; averaging the four zone percentages would instead give 65%, because that would give unequal inventories equal weight.
Finished opening and result excerpt: “Thirty of the hundred listed benches have no recorded condition check. Zone B contributes twelve of those records, the largest count, and also has the lowest coverage at 40%. I would begin inventory verification there under the stated goal. This finding concerns documentation completeness. It does not establish that any bench is damaged, unsafe or unavailable. A different goal, such as inspecting a particular asset type, would require additional evidence.”
Completed story sequence: The opening states the question and synthetic scope. The second section explains the four invented zones and the count definitions. The third pairs a coverage map concept with the count table above. The last section presents the excerpt, the inventory limitations and the next information needed. All geometry would be illustrative; no distance, travel-time or neighborhood inference is made.
Leila's map specification uses the same coverage classes for all zones and a legend that spells out “recorded checks / listed benches.” Each proposed pop-up includes both counts, the derived coverage and the synthetic-data notice. The map's caption sends readers to the table for exact values rather than asking them to estimate percentages from color.
Finished methods note: “Inputs are an original synthetic aggregate table and an invented zone sketch. No external data license or real coordinate reference system is asserted. I calculated four proportions and the weighted overall proportion. I did not perform geocoding, buffering, network routing or a spatial join. Unrecorded checks remain unknown; they are not coded as failed inspections.”
Under these invented counts and the stated documentation objective, B is the first verification candidate; the example does not estimate a real inspection priority. The artifact demonstrates denominator selection, honest method reporting and a restrained recommendation. It does not demonstrate field-survey skill or an implemented web application. That distinction helps a hiring conversation stay grounded in work she can explain.
Treat the story, map and layers as separate audiences
Esri's sharing guidance distinguishes organization, group and public audiences. An organization-only layer still requires organization membership; copying its URL into a public story does not grant that membership. Write the intended audience into your project record, then inspect each dependency against that audience.
The StoryMaps publishing documentation says its builder checks related maps, layers and themes for sharing mismatches and prompts for adjustments when permissions allow. That check is not available when you change the story's sharing from the ArcGIS content or item page. Draft changes also remain separate from the published version until republished.
Use the nested items-used list described in the item documentation to trace dependencies. Record individual layer identities rather than writing “map checked.” List relevant sublayers individually, then add the basemap service, theme and each externally hosted media item with its own audience finding. Access and permitted reuse are different questions: a resource can load while its terms still require attribution or restrict your intended use.
Do not solve a blocked dependency by widening someone else's audience or exposing project data. Identify the owner and the missing decision. A smaller portfolio made entirely from permitted original material is preferable to a polished story with unresolved dependencies.

Worked sharing audit: a public story with hidden dependencies
This second specimen is a fictional audit of a proposed portfolio, not a record of an actual published site. Mateo's intended reader is an external recruiter without organization membership. The item labels below are invented and cannot be opened. His notes describe a hypothetical configuration supplied for the exercise.
| Dependency | Recorded audience | Rights or ownership note | Completed finding |
|---|---|---|---|
| ST1 story | Everyone | Mateo's narrative | Public wrapper alone is insufficient |
| WM1 web map | Everyone | Mateo's composition | Trace underlying items |
| FL1 bench inventory | Organization | Training-team owner | External access unresolved |
| FL2 zone boundaries | Everyone | Original toy geometry | Audience fits this exercise |
| FL3 reference points | Private | Another project owner | Exclude from public handoff |
| BM1 basemap | Unknown | Credits and service terms not recorded | Verification outstanding |
| TH1 theme | Everyone | Original styling | No audience mismatch recorded |
| MD1 embedded video | Unknown | Hosting audience undocumented | Replacement or verification needed |
Completed audit result: Hold the public portfolio handoff. WM1's public status does not cure FL1 or FL3. BM1 and MD1 remain unknown, not passed. The proposed story is unsuitable for the intended reader on the supplied facts; no actual recipient-access test has occurred.
Finished internal memo: “The audience target is an external reader with no organization credentials. I can document public settings for ST1, WM1, FL2 and TH1 only. I will remove FL3 from the proposed composition and replace FL1 with my original synthetic inventory if its inclusion remains necessary. I will record basemap credits and applicable terms, then either verify the embedded video's intended audience or substitute an original permitted still with an explanatory caption. I will not change the training team's data permissions. Completion remains pending until the revised dependency list and reader-access observation agree.”
Finished reviewer note, UNSENT: “This project examines inventory completeness using synthetic data. The handoff is currently on hold while I replace restricted dependencies. I can provide a short text explanation of the question, calculation and limitations without requiring an organization login. I will supply a portfolio link only after the revised version has an appropriate access route.”
The useful outcome is an explicit hold with named remedies. It avoids calling a screenshot proof of a functioning map, or treating an authenticated owner's successful view as an external recipient's experience. Removing one layer also means checking whether its legend entry, caption or conclusion still appears elsewhere in the story.
Make the final handoff explainable and maintainable
Before sending an authorized portfolio, inspect its intended reader view and record the version, date and what actually loaded. Follow the narrative, map interactions, pop-ups, credits and supporting links. A successful landing page is only the beginning. Describe any deliberate static fallback clearly so it cannot be mistaken for an interactive analysis.
Keep the source table, calculation notes and a dependency inventory alongside your own project files. When a dataset, legend, audience or conclusion changes, revisit the other pieces it affects. Esri documents that unpublishing a story does not check or reset dependent items' sharing. Ending access to the wrapper therefore requires separate attention to dependencies.
For the application itself, state your contribution, the question answered and the principal limitation in a few sentences. Give a reviewer enough context to decide what to open and what to ask. Keep a dated record of unresolved items instead of describing them as completed work.
Use recent roles on LandOffer.ai to choose one GIS responsibility to demonstrate, then give the reviewer a concise spatial finding, its supporting evidence and a clearly documented access route.
Sources and Further Reading
- Esri: Publish, revise, and share — current StoryMaps builder and dependency-sharing documentation, checked October 22, 2026.
- Esri: Share items — audience distinctions and public URL context, checked October 22, 2026.
- Esri: View and use items — item identities, metadata, nested dependencies and terms, checked October 22, 2026.


