Three candidates describe LogMeIn/GoTo software engineering interviews: a take-home assignment, a C++ technical deep dive, and a three-round online process for a fullstack role. Here is what each reported and how to prepare.
$115K
Avg. Base Comp
$166K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Candidate reports for LogMeIn/GoTo software engineering roles differ a lot by team, so prepare for the specific role you applied to. Three candidates describe three different processes, and none of them is a general template.
One software developer candidate described a recruiter call followed by a take-home assignment that the recruiter said could be finished in an evening. The candidate says the real scope was much larger, and the tasks were not conceptually hard but needed many hours to implement fully. The candidate then received an automated rejection with no feedback. If you get a take-home, budget more time than the stated estimate and ask about scope early.
A C++ candidate reported an HR call, then a roughly two-hour technical interview with two senior C++ engineers, then an hour-long management and behavioral round. There was no live coding. The engineers walked through code on screen share and asked the candidate to reason about its output. Topics included virtual pointers, vtables, memory layout, smart pointers, RAII, the standard library and SOLID principles. There was also a code review of intentionally messy code. This candidate put the time from first contact to decision at about two weeks.
A fullstack candidate for the GoTo Budapest team described three online rounds: a 30-minute HR chat, a 90-minute technical interview and a 60-minute team-fit conversation. Questions were conceptual: class versus interface, abstract classes, dependency injection, design patterns, garbage collection, flexbox versus grid, basic JavaScript, and whether Next.js is a framework or a library. This candidate was not contacted after the final round.
All three outcomes were rejections or silence, so practice explaining fundamentals out loud rather than only defining them.
Synthesized from 3 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Logmein process.
The process kicked off with an HR call that covered my background, salary expectations, and company details. The timezone difference with the US-based recruiter made scheduling a bit awkward, and my salary expectations didn't quite align with their range, but I decided to continue anyway. The technical interview came next with two senior C++ engineers, and it was intense. There was no live coding — instead they walked me through code on screen share and asked me to reason about output and behavior. A lot of the technical discussion focused on inheritance and the underlying mechanics: virtual pointers, vtables, memory layout, how inheritance actually works under the hood. Then they switched gears to a code review exercise with intentionally messy code, which honestly made it harder to spot the good parts than the bad ones. I had to suggest improvements and explain my thinking. Beyond that, we covered smart pointers, modern C++ idioms, the standard library, RAII principles, and SOLID design principles — basically a comprehensive tour of C++ depth. The whole thing ran about two hours. After that, I had a management and behavioral round with two managers that lasted around an hour, covering personality fit and standard interview questions. The team was genuinely nice and the process moved quickly — from initial contact to final decision was about two weeks. I ended up getting rejected, which made sense given that my C++ fundamentals weren't as sharp as they needed to be for this level of role.
Prep tip from this candidate
If interviewing for a C++ role here, be prepared for deep technical questions on memory layout, virtual function mechanics, and modern C++ standards like smart pointers and RAII — these weren't surface-level discussions but core concepts they expect to be second nature.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Logmein
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Merge Sorted Lists | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Monthly Customer Report | |
| Random SQL Sample | |
| String Shift | |
| Rolling Bank Transactions | |
| Customer Orders | |
| Top 3 Users | |
| Comments Histogram | |
| Raining in Seattle | |
| Minimum Change | |
| Find the First Non-Repeating Character in a String | |
| Bagging vs Boosting | |
| Flight Records | |
| Prime to N | |
| Upsell Transactions | |
| Download Facts | |
| First Touch Attribution | |
| Job Recommendation | |
| Daily Retention Summary | |
| Find the Missing Number | |
| Recurring Character | |
| Scrambled Tickets | |
| Hurdles In Data Projects | |
| P-value to a Layman | |
| Find Bigrams |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an initial recruiter or HR call. One covered background, salary expectations and company details, and another was a 30-minute conversation described as friendly. Expect to discuss your experience and compensation range early, though the format may vary by team.
One candidate was given a take-home assignment after the recruiter call. The recruiter described it as an evening's work, but the candidate says it took far longer because of the number of functionalities required. It may not appear in every process. If you get one, ask about scope and plan extra time.
Candidates report technical rounds of about 90 minutes to two hours. The C++ candidate described screen-share code reasoning, vtables, memory layout, smart pointers, RAII and a messy-code review. The fullstack candidate reported OOP, dependency injection, design patterns, garbage collection and frontend questions. Topics likely depend on the role.
Two candidates describe a final conversation about fit. The C++ candidate had about an hour with two managers on personality and standard interview questions, and the fullstack candidate had a 60-minute team-fit interview. Prepare typical behavioral examples. One of the two candidates reported hearing nothing after this stage.
