Ho presentato la mia candidatura tramite un'altra fonte. Ho sostenuto un colloquio presso Rentable
Colloquio
The irony of interviewing at an 'IQ' company is that the front-line recruiter was completely disengaged, mentally somewhere else, and had less technical fluency than a basic GPT-2 model running on a dead battery. They did a fantastic job reading a rigid script, but the moment the conversation shifted to actual architectural depth, her system completely crashed. During the call, I offered standard enterprise feedback regarding the long-term scalability of visual, UI-driven automation tools (Make/n8n) versus robust code environments (Cursor/Claude Code). This structural nuance complete overload for her. If you deviate from the script or provide any actual engineering substance that isn't explicitly written on her prompt sheet, then expect the pipeline to get blown up. Got the generic automated rejection a few days later. If you actually know how to build at scale, be prepared for a distracted gatekeeper who is entirely out of their depth in the modern AI/automation space.
Ho presentato la mia candidatura tramite un'agenzia di reclutamento personale. Ho sostenuto un colloquio presso Rentable
Colloquio
A phone screen, hiring manager interview, interview with design, product sense then interview with CTO and CEO. All was pretty straightforward but the CEO is a bit … says things like “you can always build faster without making trade offs.” He also seems to have no trust in his team. Good luck!
Domande di colloquio [1]
Domanda 1
How do you make the team work as fast as possible?
Ho presentato la mia candidatura tramite un selezionatore. Ho sostenuto un colloquio presso Rentable nel mese di ott 2025
Colloquio
The interview process was very time-consuming. Total of 5 interviews, and 2 different take home home assessments. It started with an HR screen, followed by a short 45-minute technical take-home, a systems design interview, a hiring manager interview, and then a longer take-home assessment that was supposed to take 1–2 hours but realistically took closer to 4–5. Not too difficult, typical data engineering stuff, python sql, docker, APIs, etc..., but just a bit time consuming. The final step was a two-hour interview split between discussing the take-home with a staff engineer and another conversation with the hiring manager.
Throughout the process, the feedback I received was overwhelmingly positive — the team even mentioned my take-home was flawless and there wasn’t much to critique. I was led to believe I was a final candidate, but after a week of silence, I received a short message from the recruiter saying they had decided to hire someone at a more junior level due to budget changes.
Overall, the interview process was professional and technically fair, but the experience was frustrating given the significant time investment and lack of follow-through after such positive feedback.
Pros: Engaged team, thoughtful technical challenges, strong communication early in the process.
Cons: Excessive time commitment, poor closure, and last-minute change in hiring scope.
Domande di colloquio [1]
Domanda 1
They asked questions about distributed systems, system design, etc...