D
DEKA Research & DevelopmentSoftware Engineer
Updated Feb 24, 2026

DEKA Research & Development Software Engineer Interview Experiences 2026

Real, anonymous reports from people who interviewed for Software Engineer at DEKA Research & Development, newest first and distilled into what to expect across the loop.

Get your personalized DEKA Research & Development 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
8 months ago
Average Neutral Manchester, NH

After a recruiter-stage conversation, I later had a direct technical phone call with my hiring manager. It wasn’t a generic intro chat—it went straight into technical fundamentals like pass-by-reference vs pass-by-value, stack vs heap memory, and object-oriented programming. I remember feeling like I was being tested for real fluency rather than familiarity.

A week or so later I went in person. They covered travel expenses, and the interview was built around a whiteboard. I worked through pseudo code related to bit and string manipulation, and then I was asked to walk through my senior design project. There was also a conceptual object-oriented programming question that I didn’t handle well.
9 months ago
Average Negative Manchester, NH

The process started normally: a website application followed by a phone screen, then a virtual interview with the hiring manager on Teams. During the early rounds, including the hiring manager and junior engineers, things went pretty well.

The tone changed when senior members of the manufacturing team joined. Their questions felt unrelated to the role, and it came across like they weren’t really engaging with my resume or experiences—one of them spent much of the time looking at their phone. When the interview was nearing the end, the hiring manager came back in, and one interviewer asked how I thought I had done, adding that I should have been better prepared for future interviews. That was genuinely unsettling.

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 & Timeline

The interview process typically begins with an HR screen, followed by a technical phone interview, and culminates in an onsite interview that can involve multiple team members. Candidates noted that the structure was generally clear, but experiences varied regarding the pacing and organization of the process.

HR screenTechnical phoneOnsite interview

Technical Assessment

Candidates faced a range of technical questions, including coding problems, object-oriented programming concepts, and specific technologies related to their background. The technical depth varied, with some candidates feeling adequately challenged while others found the questions to be straightforward or lacking in rigor.

Coding problemsOOPTechnical depth

Behavioral & Experience Questions

Interviews often included behavioral questions focused on past experiences, teamwork, and problem-solving approaches, with interviewers looking for coherence and relevance to the role. The tone was generally friendly, although some candidates reported feeling dismissed or unengaged by certain interviewers.

Behavioral questionsTeamworkPast experiences

Candidate Engagement & Atmosphere

Overall, candidates described the interview atmosphere as welcoming and supportive, though some reported instances of disengaged interviewers or chaotic environments that negatively impacted their experience. The level of engagement from interviewers varied significantly across different rounds.

Supportive atmosphereEngagementInterview environment

Communication & Follow-Up

Candidates expressed mixed feelings about communication throughout the process, with some experiencing delays and vague updates, leading to frustration. Clear communication was noted as a positive aspect when present, while disorganization in follow-ups detracted from the overall experience.

CommunicationFollow-upDisorganization

Outcome & Feedback

Most candidates did not receive offers, and feedback varied from constructive to unsettling, with some feeling that their performance was unfairly judged or that they were not treated with respect. The outcome often left candidates feeling disappointed, regardless of their technical performance.

OutcomeFeedbackRespect