Harris Geospatial Solutions logo
Harris Geospatial SolutionsSoftware Engineer
Updated Mar 18, 2017

Harris Geospatial Solutions Software Engineer Interview Experiences 2026

Real, anonymous reports from people who interviewed for Software Engineer at Harris Geospatial Solutions, newest first and distilled into what to expect across the loop.

Get your personalized Harris Geospatial Solutions Software Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
Build my free plan
Hot & recentNewest first
> 1 year
Average Positive United States

I went through a two-stage process that turned into an offer later than I expected. I was contacted for a phone interview where I spoke from a conference room on speaker, and two engineers and two managers conducted the conversation. After that phone screen, I came in for an onsite interview.

Right after the onsite, I was told I didn’t get the job at the time, but that I’d be considered for another position. I had to wait, but eventually I was presented with an offer for that new role and accepted. What stood out to me was that the first decision wasn’t the final word—there was enough interest to keep me in the loop when an opening aligned better.
> 1 year
Easy Neutral Canada

My onsite day was straightforward and fairly structured. I arrived, and there was a short tour that highlighted the labs before everything moved into a conference room where the interviews were based. The whole setup felt professional and efficient.

The interview conversations themselves were centered on my knowledge base and experience, followed by a bit of general discussion. In some parts, I was asked situational questions about how I approach challenging problems and what my work ethic looks like, and the day included both technical questions and more behavioral prompts. I didn’t feel like I was being grilled, and the tone matched the fact that the feedback timeline was quick.

Unlock every Software Engineer interview experience

Real Software Engineer interview experiences
  • Difficulty, sentiment and outcomes
  • New reports added every week
See all experiences
Share your interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.

What to expect

Distilled from the reports

Interview Structure & Flow

The interview process typically consists of an initial phone screen followed by an onsite interview, often with a panel format including various team members. Candidates noted that the flow was generally professional, with some experiencing delays or logistical issues.

Phone screenOnsite interviewPanel format

Technical Evaluation

Interviews included a mix of technical questions related to the role and situational prompts to assess problem-solving skills and work ethic. Candidates were expected to demonstrate both technical proficiency and adaptability during discussions.

Technical questionsProblem-solvingAdaptability

Behavioral & Cultural Fit

Behavioral questions were common, focusing on past experiences and how candidates would fit within the team culture. Many candidates felt that interpersonal skills and the ability to connect with interviewers were valued more than just technical knowledge.

Behavioral questionsCultural fitInterpersonal skills

Feedback & Decision Timeline

Candidates reported varying experiences with the feedback timeline, with some receiving quick responses while others faced delays and uncertainty about outcomes. It's important to be prepared for potential waiting periods after interviews.

Feedback timelineDecision delaysUncertainty

Recruiter Interaction

Initial interactions with recruiters were generally positive, with candidates describing them as friendly and transparent about the process and job requirements. This initial contact often set the tone for the rest of the interview experience.

Recruiter interactionTransparencyInitial contact

Overall Candidate Experience

While many candidates found the interview process to be low-stress and straightforward, some noted logistical hiccups and a lack of clarity during the process. Overall, candidates felt the experience was professional but could benefit from improved organization.

Candidate experienceLogistical issuesProfessionalism