Photogrammetrist Interview Questions

The interviewer wants to know whether you can gather and organize the right source material before a map is built. Start with the kinds of sources you have used, then walk through one project: what the map was for, which sources you collected, how you checked their dates and accuracy, and how you organized them so the team could use them. Sample answer: "On a county trail map update, I pulled the latest aerial imagery, the parks department's survey notes, easement records and the previous edition of the map. The survey notes and the old map placed one trailhead in different spots, so I checked the imagery, confirmed the survey was newer, and noted the change in our source log. I stored everything in one project database with the date and origin of each layer, which made the final review much faster." Pitfalls to avoid: listing source types without an example; skipping how you judged which sources were reliable; claiming experience with data types you haven't used.

The interviewer wants to see that your design choices follow from the map's purpose, not habit. Build your answer around one map. Start with who would use it and how, such as printed field sheets or a web viewer. Then explain each choice in that light: the scale needed to show the detail that matters, a projection that keeps the right property for the task, a layout that puts the key information first, and colors that read clearly, including for people with color vision deficiency. End with how you wrote the specs down and checked that production followed them. Sample answer: "For a flood-risk map meant for public meetings, I used a scale that showed individual streets, the local state plane coordinate system to keep distances accurate, and a simple legend in one corner. I chose a sequential blue scheme that still worked in grayscale, then printed a test copy and had a colleague check it against the spec sheet." Pitfalls to avoid: naming settings without saying why; ignoring the audience or output size; forgetting how you confirmed the final product met the specs.

The interviewer wants to know whether you have a reliable quality-control habit, since errors on a published map can mislead users or cause legal problems. Describe your process step by step, and show that it is repeatable, not a final glance. Cover what you compare the map against, the kinds of errors you look for, and who else reviews it. Sample answer: "I work from a checklist built from the project specs. First I confirm every required layer and label is present and that the legend, scale bar, north arrow and source notes are correct. Then I spot-check feature positions against the source imagery and survey data, and look closely at edges where layers meet. I run automated checks for gaps and overlaps in the data, and I ask a colleague who hasn't worked on the map to read it fresh, because they catch things I stop seeing. Anything we fix goes in the project log." Pitfalls to avoid: describing only a visual look-over; leaving out source comparisons; saying you never find errors.

The interviewer wants to know whether you can turn source imagery and data into accurate map products, and how comfortable you are with the equipment involved. Walk through your workflow in order for one product: the inputs you start from, how you set up the stereo models or software, how you extract or edit features and terrain, and how you check the result. If your experience is mostly digital, say so and explain how it relates to older stereoplotting methods. Sample answer: "Most of my work is in digital photogrammetry software. For a recent terrain model, I loaded overlapping aerial images with their orientation data, checked the stereo model against ground control points, then collected breaklines along streams and ridges. After generating the surface, I compared it with spot elevations and edited areas where trees had thrown off the heights. Then I produced contours and a shaded relief for the final chart." Pitfalls to avoid: listing every product without walking through one; skipping quality checks; overstating experience with equipment you've only seen.

The interviewer wants to see how careful you are and what you do once you find a problem. Use Situation, Task, Action, Result: set up the project, say what you were responsible for, describe how you noticed the error and traced its cause, and explain the outcome and what you changed to prevent it again. Sample answer: "I was preparing a utility map for a city client. While checking the final layers, I noticed water lines along one street ran through building footprints. I traced it to a dataset that had been delivered in a different coordinate system and reprojected incorrectly. I fixed the projection, rechecked the other layers from that source, and found one more affected. We delivered on schedule, and I added a step to our intake checklist to confirm the coordinate system of every incoming dataset." Pitfalls to avoid: choosing an error so small it shows little; leaving out how you found the cause; skipping what you changed afterward.

The interviewer wants to learn how you compare conflicting sources and choose information that fits a map's purpose and accuracy needs.

Build your answer around Situation, Task, Action, Result. Briefly describe the disagreement between the survey notes and older map and your responsibility for resolving it. Spend most of the answer on your checks of each source's date, method, accuracy and relevance. Explain the choice you made, the result and what you learned.

For example: "I was updating a map when survey notes placed a road junction differently from an older map. I needed to choose a location supported by the source records. I checked the coordinate systems, survey method and dates. The notes documented a later road change, so I used the surveyed location and recorded why I set aside the older location. The finished map showed the updated junction with a traceable source. I learned to check what changed before assuming one source was wrong."

Avoid assuming the newest source is always best, choosing whichever source is easiest to use, or describing the team's decision without explaining your own checks.

The interviewer wants to know whether you can manage heavy data without slowing projects down or damaging the source. Explain your approach as a workflow: how you organize files, how you limit processing to what the project needs, how you keep originals safe, and how you check the output. Give a sense of the data's size and the methods you used, without overstating. Sample answer: "On a highway corridor project we received lidar covering many miles of road. I kept the original files read-only and worked from copies split into tiles along the corridor. I built indexes so the software could display data quickly, clipped everything to a buffer around the road, and processed tiles in batches with a script. After classifying ground points, I checked a sample of tiles against survey checkpoints before merging results. A simple naming system and a log kept versions straight across the team." Pitfalls to avoid: naming software without explaining the method; ignoring version control; skipping how you checked accuracy.

The interviewer wants to see whether you keep learning and can judge when a new method is worth adopting. Use Situation, Task, Action, Result: what you were doing before, why you looked at something new, how you learned it and tested its accuracy, and what changed. Sample answer: "Our team mapped small construction sites from aerial photos that were often a year out of date. I suggested trying drone imagery for one site. I took a short course, worked with a certified drone pilot, and set out ground control points. I processed the images into an orthomosaic and compared it with surveyed checkpoints to confirm it met the project's accuracy needs. The client got a current base map soon after the flight, and we wrote a short procedure so others could repeat it." Pitfalls to avoid: describing a tool without saying why it helped; skipping how you checked accuracy; claiming expertise after one try.

The interviewer wants to know whether you do the right thing when it is inconvenient, and how you handle pressure to cut corners.

Use Situation, Task, Action, Result. Describe the pressure or temptation without naming people, explain the choice you made and why, and how you handled the conversation. Keep the focus on your actions, not on judging others.

Sample answer: "Near the end of a quarter, a coworker asked me to record a sale as complete even though the customer hadn't signed yet, so our numbers would look better. I told them I wasn't comfortable doing that and suggested we tell our manager the deal would close the following week. My manager agreed it should wait. The customer signed early in the new quarter, and our records stayed accurate."

Pitfalls: Don't say your ethics have never been tested. Avoid stories that make you sound self-righteous or that share confidential details. Don't pick an example where you went along with the wrong choice and stop there.

The interviewer wants to see that you weigh options carefully instead of going with the first idea, and that your reasoning leads to better results.

Use Situation, Task, Action, Result. Describe the problem, list two or three options you considered, and give the main strength and weakness of each. Explain which you chose and why, then describe the impact.

Sample answer: "Our team needed a faster way to answer common customer questions. I compared three options: hiring a part-time assistant, writing a help page, or creating email templates. Hiring was quick but costly. A help page would take longer but reduce calls over time. Templates were cheap but only sped up our replies. I recommended the help page, with templates as a short-term fix. Within a few months, repeat questions fell noticeably."

Pitfalls: Don't list options without saying what you compared them on. Avoid choosing an option without explaining the trade-off. Don't leave out the impact.

The interviewer wants to see that you keep an eye on your work area or data, notice problems early, and act on them.

Use Situation, Task, Action, Result. Describe what you were checking and how often, what signaled the problem, and the steps you took right away. Include who you told and what you did to stop it happening again.

Sample answer: "I review our inventory report every Monday. One week I saw that one item's stock had dropped far faster than usual. I checked the order records and found a duplicate order that had shipped twice to the same customer. I told my supervisor, contacted the customer to arrange a return, and asked our systems team to block duplicate orders. The return came back the following week, and we haven't seen the problem since."

Pitfalls: Don't pick a problem someone else found and you only fixed. Avoid stopping at the fix without saying how you prevented a repeat. Don't stay vague; name what you were monitoring.

The interviewer wants evidence that you listen to understand, not just to reply, and that it makes a difference to your work.

Use Situation, Task, Action, Result. Show what careful listening looked like: letting the person finish, asking follow-up questions, and repeating back what you heard. The outcome should show that listening caught something you would otherwise have missed.

Sample answer: "A manager from another department asked for a monthly report and said they wanted it faster. Instead of starting right away, I asked what they used the report for. They mentioned twice that they only looked at two of the columns. I confirmed that with them, built a one-page summary of just those figures, and it took a third of the time to produce. They used the summary format from then on."

Pitfalls: Don't just describe yourself as a good listener without an example. Avoid an answer where you talk mostly about what you said. Don't leave out the outcome the question asks for.

The interviewer wants to see that you can work well with a team while still bringing your own judgment, and that you know when to speak up and when to go along.

Start with a short answer about how you balance the two, then give one example. A good example shows you sharing your own view, listening to others, and then supporting the team's decision even if it wasn't yours.

Sample answer: "I try to form my own view first, share it clearly, and then commit to whatever the group decides. On one project, the team wanted to launch a new form right away. I thought we should test it with a few users first and explained why. We agreed on a one-week trial. Testing found a confusing field, we fixed it, and the full launch went smoothly."

Pitfalls: Don't present yourself as someone who always goes along or always insists on your own way. Avoid a story where you ignored the team's decision. Don't skip the example.

The interviewer wants to know how you plan your time and handle competing demands, and whether you meet deadlines.

Use Situation, Task, Action, Result. Name the specific challenges, such as overlapping deadlines or interruptions. Describe the steps you took to plan and protect your time, and what you did when something came up. End with the results the question asks for.

Sample answer: "During one busy week, I had a report due Thursday, two new team members to train, and my usual daily tasks. I mapped out the week on Monday, scheduled training for the mornings when things were quieter, and blocked two afternoons for the report. When an urgent request came in Wednesday, I asked a colleague to cover one training session. The report went in a day early, and both new team members finished their training on schedule."

Pitfalls: Don't just list time-management tools. Avoid a story where you met the deadline only by working through the night. Don't skip the challenges.

The interviewer wants to see how you work with others to line up schedules, tasks, and handoffs, and whether you learn from times it didn't work.

The question asks for two stories, so keep each one short. For the success, explain who was involved, how you kept everyone in step, and the result. For the less successful one, say what went wrong, your part in it, and what you now do differently.

Sample answer: "For an office move, I set up a shared timeline with the facilities, technology, and department leads, and held a 15-minute check-in each week. Everyone was set up and working by Monday morning. Earlier, on a smaller project, I assumed a vendor knew our deadline and didn't confirm it. Their delivery came two days late. Since then I confirm key dates in writing with everyone involved."

Pitfalls: Don't spend all your time on the success. Avoid blaming others for the one that went wrong. Don't skip what you learned.

The interviewer wants to see that you keep up with what is happening around your work and use that knowledge to help the organization prepare.

Use Situation, Task, Action, Result. Explain what the problem was, how you came to understand it early (reading, training, talking with others), what you recommended, and how the organization responded.

Sample answer: "I read in an industry newsletter that a key supplier planned to stop making a part we used in several products. I checked with our purchasing team, confirmed the news, and researched two replacement parts. I shared a short summary with my manager, and we ordered extra stock of the old part while we tested a replacement. When the supplier stopped production months later, we switched over without any delays to customers."

Pitfalls: Don't take credit for spotting something everyone already knew. Avoid a story where you noticed the problem but did nothing. Don't leave out how you learned about it.

The interviewer wants to see whether you can work with little supervision, set your own direction, and still deliver.

Use Situation, Task, Action, Result. Pick one of the two options in the question rather than trying to cover both. Explain why no one was directing the work, what you decided to do on your own, and how you kept yourself on track. Show the result and how others responded.

Sample answer: "Our team's files were spread across several shared folders, and finding old documents took a long time. No one owned the problem, so I proposed a simple folder structure and naming rule to my manager. With their OK, I moved the files in short sessions over three weeks, between my regular tasks, and wrote a short guide. People stopped asking where files were, and new hires used the guide in their first week."

Pitfalls: Don't describe going around your manager without telling anyone. Avoid a task you were closely supervised on. Don't make the story about doing something only because it was required.

The interviewer wants to know whether you step up without being asked and can handle the extra load without letting your regular work slip.

Use Situation, Task, Action, Result. Say why you took on the extra work, then focus on how you managed it: what you planned, what you set aside or handed off, and who you kept informed. Finish with the result for both the new duty and your usual work.

Sample answer: "When our team lead went on leave, I offered to run the weekly status meeting and track open issues on top of my own tasks. I blocked an hour each Friday to update the tracker and asked my manager which of my lower-priority tasks could wait. Over six weeks every meeting ran on time, my own deadlines held, and the lead kept the tracker format when they came back."

Pitfalls: Don't describe extra work you were simply ordered to do. Avoid claiming you did it all with no trade-offs. Don't leave out how your usual work was affected.