Geodetic Computator Interview Questions

The interviewer wants to know how you check that survey work meets the project's specifications and the standards that apply. Organize your answer around your process: what you compare the data against, the checks you run, and what you do when something fails.

Sample answer: I start by reading the project specs so I know the required accuracy, datum, and deliverables. After fieldwork, I review closures on traverses and level loops, then run a least squares adjustment and look at the residuals and error ellipses for anything outside tolerance. For GNSS work, I check session lengths, repeat observations, and ties to published control. I compare the results with the spec and write a short quality report. If a point fails, I trace it back to the field notes before deciding whether to reobserve it.

Pitfalls to avoid: listing software without explaining the checks, skipping how you handle failures, and claiming one standard applies everywhere, since requirements vary by client, agency, and state.

The interviewer wants to hear a clear, ordered survey process and sound choices about methods and checks. Walk through the steps from planning to the final deliverable, and explain why you pick each method.

Sample answer: I begin with the purpose of the survey and the accuracy the client needs, then research existing control and records for the area. Next I plan the method: GNSS for wide areas and control, a total station where there is tree cover or close detail, and leveling where elevations must be tight. In the field, I tie into known control, take redundant measurements, and keep careful notes and photos. Back in the office, I process and adjust the data, check it against the accuracy target, and compute positions, areas, volumes, or contours. Then I prepare the drawings or files and a short report on methods and accuracy.

Pitfalls to avoid: skipping the planning and research step, describing measurements with no checks or redundancy, and naming tools without saying why they suit the job.

The interviewer wants to see that you can take a tract survey from records to final figures, and that you check your work. Use Situation, Task, Action, Result.

Sample answer: A county needed the position and area of a large rural parcel before selling part of it. I started with the deed, earlier plats, and nearby published control. In the field, we used static GNSS to set control points, then RTK and a total station to locate the corner monuments, two of them in heavy woods. One corner did not match the record, so I compared the evidence with the adjoining surveys and reviewed it with the licensed surveyor in charge before the final position was set. I computed the boundary and area and ran an independent check from a second control point. The figures agreed within tolerance, and the plat went to the county with a report on our methods.

Pitfalls to avoid: skipping how you checked the results, glossing over conflicts with records, and assuming boundary rules are the same in every state.

The interviewer wants to see that you can plan fieldwork so the data meets the specs the first time, even when time is short. Describe your process in order and how you set priorities.

Sample answer: I start with the project's accuracy requirements, because they set session lengths and how many repeat observations each point needs. Next I review the sites with maps and imagery, and send someone for reconnaissance where access or sky view is uncertain. I build a session plan that spreads repeat observations across different times of day, assign receivers and crews, and check equipment and batteries the day before. For priorities, I schedule the hardest sites to reach and the points other work depends on first. I keep a buffer day for weather and reobservations, and I review the data each evening so problems are caught while crews are still nearby.

Pitfalls to avoid: a plan with no room for reobservations, ignoring site access and permissions, and listing steps without saying how you decide what comes first.

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 how your survey expertise can help management make a better project decision.

Choose a real recommendation you gave to management. Explain the project need, the evidence behind your advice, and your own role in presenting it. End with management's decision and the benefit you could verify. Translate technical details into their practical effect.

Sample answer: "On a highway project, the plan was to reuse an older control network. My checks against new observations showed discrepancies beyond the project's accuracy requirements. I took the comparison to our survey manager and used a simple map to explain the possible effect on grades and alignments. I recommended checking and replacing the affected control before the design survey continued. The manager agreed to revise the plan. Later checks showed that the new control met the project's accuracy requirements."

Avoid telling a story about advising a client when the question asks about management, burying the recommendation in jargon, or claiming benefits you did not follow up enough to confirm.

The interviewer wants to learn whether you can apply new positioning technology in a way that produces a useful, reliable improvement for a survey project.

Use Situation, Task, Action, Result. Set out the project need and the technology or method you introduced. Explain your own role in trying it, the checks you used before relying on it, and the benefit you observed. Finish with what you learned about when to use it.

For example: "Our crew was considering a new GNSS correction service for a control survey. I helped test it before we used it for project observations. I compared its results with known control and repeated observations at different times. I also reviewed the correction records when results varied. The checks helped us identify where the service gave results within the project's tolerance. We used it in those areas, which reduced setup work. I learned to judge the method by field checks rather than advertised accuracy."

Avoid listing features without a project example, claiming benefits you did not observe, or treating a new method's results as reliable without validation.

The interviewer wants to learn whether your coaching helped a field crew member or junior surveyor build a useful survey skill.

Build your answer using Situation, Task, Action, Result. Briefly describe the skill gap and your coaching role. Spend most of the answer on what you demonstrated, how the person practiced, and how you checked progress. End with the change in their work and a lesson about teaching.

For example: "A junior crew member was unsure how to record GNSS antenna heights. I needed to help them make reliable entries in the observation log. I demonstrated the measurement and explained the reference point, then watched them repeat it and explain their steps. We reviewed their next logs together. They began making consistent entries without reminders. I learned that asking someone to show the steps reveals more than asking whether they understand."

Avoid vague claims that you are a good mentor, taking credit without explaining your role, or describing improvement without evidence from the person's survey work.

The interviewer wants evidence that you inspect carefully and that your checks catch problems before they grow.

Use Situation, Task, Action, Result. Say what you were inspecting and why, what you noticed, how you traced the cause, and what happened after you reported or fixed it.

Sample answer: "During a routine walk-through, I noticed a small puddle of fluid under one of our machines. It wasn't on the checklist, but I wiped it up and checked again an hour later, and it was back. I followed the line and found a fitting that had worked loose. I tagged the machine, reported it to my supervisor, and maintenance replaced the fitting before the end of the shift. If it had failed during a full run, we would likely have lost most of a day."

Pitfalls: Don't claim you never miss anything. Avoid stories where you found a problem but didn't report it. Don't skip how you confirmed the cause.

The interviewer wants evidence that you test things carefully and use what you find to make them better.

Use Situation, Task, Action, Result. Explain what you tested and why, how you set up the test, what the results showed, and what you changed. End with how you measured the improvement.

Sample answer: "Customers kept saying our online order form was confusing, so I was asked to look into it. I had five coworkers who had never used the form place a test order while I watched and took notes. Four of them got stuck on the same shipping step. I suggested moving that step and rewording two labels, then ran the same test again. All five finished without help, and complaints about the form dropped over the next month."

Pitfalls: Don't describe a change made on a hunch with no test. Avoid skipping how you checked the result. Don't use jargon without explaining it.

The interviewer wants to see that you solve problems in a careful, evidence-based way rather than by guessing.

Use Situation, Task, Action, Result. Describe the problem, the idea you formed about its cause, how you tested that idea by changing one thing at a time, and what the results showed.

Sample answer: "Samples from one of our machines kept failing a quality check, but only on some days. I suspected temperature, so I recorded the room temperature and the test results for two weeks. The failures lined up with the warmest afternoons. I then ran test batches at two set temperatures, changing nothing else, and the pattern held. We moved the heat-sensitive runs to the mornings and added better cooling, and the failures stopped."

Pitfalls: Don't jump to a fix without testing the cause. Avoid changing several things at once and claiming one of them worked. Don't use technical terms without a plain explanation.

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 an honest self-assessment and evidence that your writing is clear enough for the job.

Give a direct rating, then back it up with the kinds of writing you do and one example. Mention how you make sure your writing is clear, such as knowing your reader, keeping it short, and proofreading. If there's an area you're improving, say what you're doing about it.

Sample answer: "I'd rate my writing as strong for everyday work. I write emails, short reports, and how-to guides for my team. Before I send anything important, I ask myself what the reader needs to do with it, put that first, and reread it once out loud. Last year I rewrote our team's onboarding guide, and new staff said it was easier to follow. I'm still working on keeping longer reports concise."

Pitfalls: Don't give a rating with no evidence. Avoid rating yourself as perfect. Don't claim writing experience you couldn't show if asked for a sample.

The interviewer wants to know whether you can explain ideas clearly to a group and handle the room.

Use Situation, Task, Action, Result. Describe the audience and the purpose, how you prepared, and how you kept people engaged. Be honest about how it went, including questions you didn't expect and how you handled them.

Sample answer: "I presented a proposal for a new scheduling process to a group of about 15 managers. I kept the slides to five, led with the problem it solved, and practiced with a colleague who asked tough questions. During the meeting, one manager asked about costs I hadn't covered. I said I would follow up, and I sent the figures the next morning. The proposal was approved for a three-month trial."

Pitfalls: Don't say it went perfectly with no details. Avoid focusing only on your nerves. Don't skip how you handled questions or feedback.