
Two candidates describe 84.51 degrees software engineer interviews as conversational and fundamentals-focused. Both report a behavioral or HR conversation, then a technical portion with coding or Java plus SQL, and both ended without an offer.
$130K
Avg. Base Comp
$145K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Candidates describe the 84.51 degrees software engineer interview as relaxed and conversational, with a technical portion built around fundamentals, SQL and practical coding rather than tricks. Both reports come from people who did not receive an offer, so treat them as a small sample.
One candidate, who interviewed for an internship, started with a behavioral round. The interviewer walked through the resume and asked about motivation for joining 84.51 and how the candidate saw its culture. The technical assessment that followed had one coding problem and one SQL question, which the candidate called straightforward. The advice was to practice basic LeetCode problems, be solid in a chosen language and know SQL.
A second candidate, who interviewed for a full-time software engineer role, began with a friendly HR screening call. An on-campus interview with several engineers came next. Several scheduled interviewers did not show up. The candidate described the questions as conversational and focused on the resume, hobbies and interests. The technical questions covered Java and SQL, including a design-oriented prompt about building a basic REST endpoint. The candidate found them surface-level and said the process moved quickly.
To prepare, be ready to explain your resume projects and why 84.51 appeals to you. Also practice SQL queries, basic coding in your strongest language and simple REST API design. Expect a personable discussion more than a deep algorithm grind, but do not skip fundamentals, since both candidates still faced technical questions.
Synthesized from 2 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 84.51 degrees process.
The interview process was pretty relaxed overall. The first round was behavioral, and it really felt like they wanted to get to know me as a person rather than grill me on technical minutiae. The interviewer walked through my resume, asked about my motivations for joining the company, and genuinely seemed interested in understanding what drew me to 84.51 and how I felt about their culture. There was even a lighter question thrown in just to keep things conversational. The whole vibe was calm and welcoming—you could tell they valued cultural fit and personality alongside skills.
After that, I moved into the technical assessment, which was straightforward. There was a coding problem and a SQL question, neither of which was particularly difficult. It felt like they were testing whether I had the fundamentals down rather than trying to stump me with obscure algorithms or complex queries. The key was just being solid with whichever language I chose and having decent SQL knowledge. Honestly, the whole process felt designed to be approachable—they weren't trying to make it unnecessarily hard. If you're prepared with basic LeetCode practice and comfortable with SQL, you should be fine on the technical side.
Prep tip from this candidate
Brush up on fundamental LeetCode problems and make sure you're comfortable with SQL queries—the technical round is straightforward and tests basics rather than tricks. For the behavioral, just be genuine and personable; they care a lot about culture fit and how you'll mesh with the team, so let your personality show.
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 84.51 degrees
What kind of model would be best to allocate the correct number of agents, and what metrics would you check?
| Question | |
|---|---|
| Your Strengths and Weaknesses | |
| 2nd Highest Salary | |
| String Shift | |
| Largest Salary by Department | |
| Duplicate Rows | |
| Data Pipelines and Aggregation | |
| Payment Data Pipeline | |
| Hurdles In Data Projects | |
| Area Under the ROC Curve | |
| Ranking Metrics | |
| Skyscanner Partner ETL | |
| Production Model Monitoring | |
| Words in Encrypted String | |
| RAG Strict Source Control | |
| Using APIs for Downstream Tasks | |
| Text Search System | |
| Why Do You Want to Work With Us | |
| Solo ML Deployment | |
| Unstructured Data Pipeline (ETL) | |
| Scalable Data Pipelines | |
| SFTP Pipeline | |
| Closest SAT Scores | |
| Employee Salaries | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Subscription Overlap | |
| Monthly Customer Report | |
| Top 5 Turnover Risk | |
| Random SQL Sample |
Synthesized from candidate reports. Individual experiences may vary.
One candidate reports a friendly, low-pressure HR screening call that focused on their background. Expect to explain your experience and interests clearly. This step was described for the full-time role, so internship candidates may see it differently.
Candidates report conversational interviews that walk through the resume and ask about motivation for joining 84.51 and views on its culture. One also describes questions about hobbies and interests outside work. A lighter question was mixed in to keep the tone casual.
Both candidates report a technical portion built on fundamentals. The internship candidate describes one coding problem and one SQL question. The full-time candidate describes Java and SQL problems, including designing a basic REST endpoint. Both found the difficulty modest, so prepare for fundamentals.
The full-time candidate describes a longer on-campus session scheduled with the director of engineering and other engineers. Several interviewers did not show up. Formats may vary by role, so confirm the schedule with your recruiter.