Three candidates describe Here software engineer interviews: an HR call, then technical rounds on Java, JavaScript, data structures, containers and AWS. Reports differ by role, so prepare broadly.
$128K
Avg. Base Comp
$150K
Avg. Total Comp
2-3 rounds
Typical Rounds
14 days
Process Length
Candidates describe Here's software engineer interviews as technical and varied. The three reports cover different levels, so expect the topics to depend on the team and seniority.
The longer technical call is the clearest preparation target. One candidate who accepted an offer reports a roughly two-hour call that moved between architecture, containerization, Spark, Java, testing frameworks and mostly AWS. A question on why and when to use containers, how containerization works, and basic Docker stuck with them. They describe the interviewers as relaxed about gaps: saying "I don't know" and moving on worked for them.
An internship candidate reports an HR screen followed by a technical round. It asked them to implement a linked list from scratch and design a simple file system class, with discussion of methods and edge cases. A motivation question about joining Here was also part of the conversation.
A senior candidate who did not get an offer describes a different tone. They report JavaScript and TypeScript fundamentals such as hoisting, IIFEs and typeof, then Java 8 features such as functional interfaces, Runnable versus Callable and executors. The third round covered cloud services and Python. They felt the questions leaned toward recalling syntax rather than design trade-offs.
Practical preparation is to refresh language fundamentals for your stack, practice basic data structures and small class designs, and review Docker and AWS basics. Two candidates report about two weeks from application to offer.
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 Here process.
I went through three rounds at Here, and honestly, the whole experience felt misaligned from the start. The first technical round focused heavily on JavaScript and TypeScript fundamentals—stuff like hoisting, IIFE, and the typeof operator. The interviewer kept pushing on syntax and edge cases rather than diving into actual problem-solving or system design, which felt off for a senior-level role. There was a question about counting repeated elements in an array, but the real frustration came when the interviewer made a mistake and I caught it. Instead of acknowledging that, they just moved on, and the tone of the whole interview shifted. When they couldn't find footing in areas where I had expertise, they seemed to already have their mind made up, yet stretched the session to an hour and fifteen minutes anyway. It felt like going through the motions.
The second round went similarly sideways. This time it was Java 8 features—functional interfaces, Runnable vs. Callable, executor frameworks. Again, the focus was on reciting syntax from memory rather than understanding design or trade-offs. The interviewer seemed less experienced than the candidates they were interviewing, like they'd grabbed a random list of interview questions without thinking about whether they matched the role or seniority level. By the third round, things shifted to cloud services and Python, which made sense for a DevOps-adjacent position, but by that point the damage was done. I got through two rounds but didn't make it past the final one.
The whole process left me with a clear impression: Here's interview quality and preparation were inconsistent, and the culture signal I picked up—especially from the first interviewer's dismissive approach—wasn't encouraging. If that's how they treat candidates during interviews, I had no interest in finding out what the actual team dynamic would be like.
Prep tip from this candidate
If you interview here, expect inconsistent interviewer preparation and a heavy focus on syntax recall over conceptual understanding. Don't let an interviewer's dismissive tone or mistakes throw you off—stay professional and keep demonstrating your knowledge, but know that poor interview quality is a red flag about team culture.
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 Here
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Merge Sorted Lists | |
| Subscription Overlap | |
| Closest SAT Scores | |
| Monthly Customer Report | |
| String Shift | |
| Comments Histogram | |
| Prime to N | |
| Random SQL Sample | |
| Find the Missing Number | |
| Largest Salary by Department | |
| Rectangle Overlap | |
| Upsell Transactions | |
| Over-Budget Projects | |
| Retailer Data Warehouse | |
| Hurdles In Data Projects | |
| Minimum Change | |
| Recurring Character | |
| Scrambled Tickets | |
| The Brackets Problem | |
| Project Pairs | |
| Size of Joins | |
| Integer to Roman | |
| Total Spent on Products | |
| Sum to N | |
| Find the First Non-Repeating Character in a String | |
| Bagging vs Boosting | |
| Nearest Common Ancestor | |
| Level Of Rain Water In 2D Terrain | |
| Target Indices |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report applying online or through the Here portal and getting a call from HR. One describes a quick conversation of about fifteen to twenty minutes covering background, programming experience and motivation for the role. Expect it to be a screening step before technical interviews.
Reports vary by level. One accepted candidate describes a video call of roughly 40 minutes with basic algorithms, data structures and live coding. An internship candidate reports implementing a linked list and designing a simple file system class. A senior candidate reports JavaScript and TypeScript syntax questions and an array counting problem.
One candidate reports a call of nearly two hours covering architecture, containerization, Spark, Java, testing frameworks and AWS, with interviewers who accepted not knowing everything. A senior candidate reports a round on Java 8 features, including functional interfaces and executors. Breadth may matter more than depth on one topic.
The senior candidate who was not offered reports a third round on cloud services and Python. The internship candidate reports behavioral questions about motivation for joining Here, with hiring managers on camera off. Outcomes in these reports ranged from an accepted offer and a received offer to no offer.
