Hotplate Software Engineer Interview Experience — A 70-Minute "Build Anything" Feature Round, Rejected After Onsite

Hotplate·Software Engineer·Nov 2026
OnsiteHR ScreenTechnical ScreenRejectedeasy

Bay Area startup

  1. Phone Screen - 30 mins - a call with the CEO, he asked about my background
  2. Coding Round - 40 mins - not LeetCode, it was a Codeforces problem, solved in one pass
  3. Onsite Rounds - 2 rounds, feature building (70 mins) + system design (70 mins)

Let me go into detail on the feature building round. You bring your own laptop and you can use AI. The interviewers were the CEO and 2 employees together.

Interviewer: I'm sending you a folder via email. There are no requirements. Build anything you see fit.

Me: what's in the folder?

Interviewer: you can figure it out. maybe ask AI

I told CC to read the folder and figure out the context, and I also looked through it myself.

It was one folder with 10 logs. Each log was a JSON array containing conversations between some users and some agents. There was also a file called manifest.json in the folder that described the user attributes (userId, avatar URL, conversation id) and the agent attributes (the agent's role, the agent's color, etc.).

I figured the first step had to be getting the requirements clear.

Me: ok so this seems to be conversations between some users and some agents. I think an application built on this data would be an internal tool or an admin tool where they can inspect the logs. What do think of that?

Interviewer: sure. an admin tool sounds cool. and what features will this admin tool have? what do you think an admin tool would need?

Me: i think admin tools prioritize clarity over style. I'm thinking of a table with filter, search, and pagination. And for each row, you can click into it and a modal will pop up on the right, and you will be able to see the full exchange. what do you think of that?

Interviewer: cool. I think that sounds good. Why use a table? And What features would an admin want on this table?

...I'm skipping the back-and-forth here. I kept trying to pin down what the problem statement actually was and what the interviewer wanted, and he just kept saying ok and then handing the decision back to me.

In the end we settled on just building a UI table + modal and rendering this data, and that was it. CC produced a lot of slop, so I decided to disable most of the UI components with feature flags, and then I suggested a settings page so users could customize the dashboard.

Along the way I asked whether this dashboard needed accessibility or mobile responsiveness. The interviewer said no.

Claude Code was writing code too slowly, so I asked if I should write integration tests, and the interviewer said no.

The rest of the time I just tweaked the UI and tweaked styles. And then I really didn't know what else to do. The dataset he gave was really tiny, and there was nothing meaningful to do with it. I figured if this data were coming back from a backend, the frontend's job would just be to display it, so I kept asking the interviewer in different ways what exactly he wanted me to do, and the answer was always: build whatever you want.

After the 70 minutes, the interviewer just said "unfortunately we won't be moving forward with the next round." He gave two reasons:

  1. you didn't scrutinize the code that the ai produced
  2. we think you could have done more meaningful features

Rant:

This was a really baffling interview. There was basically no context, no requirements, no stack, and they never made clear what the format was or what they actually wanted to see. At first I thought they were testing my ability to understand context, then I thought they were testing my UI/UX planning, and later I thought they were testing how I use AI. Even now I still haven't figured out what I was supposed to do.

While writing this I'm also reflecting on whether I misread it. I've done mostly frontend work before, and normally when I see data like this my first instinct is to assume it's data returned from a backend API and then figure out the frontend interactions. Maybe the interviewer wanted me to build a full-stack application? Build a backend, make some endpoints and services to process their data? Then why not say up front that this is a 70 min hackathon, build a full stack application? That way I could have let loose and gone wild with it.

Published

Curated and edited by PracHub

Practice the questions from this interview

Discussion

Sign in to join the discussion. The author is notified of every comment.

Loading comments…

Interview at a glance

Company
Hotplate
Role
Software Engineer
Rounds
HR Screen → Technical Screen → Onsite
Outcome
Rejected
Difficulty
easy
Interview date
Nov 2026
Questions from this interview
1 question

Related interview experiences

Explore more interview rounds, questions, and outcomes.

Browse interview experiences