Forward Deployed Engineer applicants have rated the interview process at Invisible Technologies with 3.3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 25% positive. To compare, the company-average is 30% positive. This is according to Glassdoor user ratings.
Candidates applying for Forward Deployed Engineer roles take an average of 14 days to get hired, when considering 4 user submitted interviews for this role. To compare, the hiring process at Invisible Technologies overall takes an average of 32 days.
Common stages of the interview process at Invisible Technologies as a Forward Deployed Engineer according to 4 Glassdoor interviews include:
Phone interview: 29%
One on one interview: 29%
Background check: 14%
Personality test: 14%
Skills test: 14%
Here are the most commonly searched roles for interview reports -
Met with recruiter for the first screen and then went directly to Technical rounds.
The two technical rounds consisted of a system design interview and a coding challenge, both of which were one hour long.
Unsure why there wasn't a meeting with a hiring manager or member of the team you'd be on prior to the technical rounds, rather unprecedented in my experience and poorly organized in that regard.
Didn't get past the coding round even though I didn't find it particularly challenging, didn't use my time efficiently due to failed communication from the interviewer.
Unfortunately, the doors have closed for me with this role, even though i've done work like this 100 times, but more doors will open as I go through this process again.
Here's hoping there is some minimal change so the process is easier for other people moving forward.
Interview questions [2]
Question 1
System Design
Wasn't anything like "design Uber" or "make the Reddit API"
Was a solution their team had recently worked on regarding reporting metrics, so you didnt really need to worry about some of the things you'd see in other SD interviews like load balancing or scaling, at least not for this particular question.
2 python questions
Wasn't informed there were two questions so i spent too much time on the first question and ran out of time for the second one.
Should be okay if you know iteration, dictionaries, arrays, and python math operators regarding division
I applied online. I interviewed at Invisible Technologies (New York, NY) in Feb 2026
Interview
Started with a recruiter screen, then another call with a tech lead, then a call with a principal engineer and then one with one of their operations leaders. I passed all of them and then they flew me to be interviewed by their client which is a large private equity firm in NYC. Up to this point they had signaled I was good for the position and they were excited to work with me. They had told me the NYC conversation would be mostly about fit but it turned into a system design interview.
Their customer did not want to hire me and therefore invisible did not hire me.
Be advised that they have not refunded me for my trip to NYC even after months of back and forth.
Interview questions [1]
Question 1
Design an AI system that handles emails and routes them to the right teams.
I applied through a recruiter. The process took 2 weeks. I interviewed at Invisible Technologies (New York, NY) in Apr 2025
Interview
1: interview with recruiter to make sure youre a good fit(could be a second recruiter interview with a senior but I was pushed past that part)
2: Two technicals, one coding and one architectural interview
3: behavioral
4: Final with CTO
Interview questions [1]
Question 1
medium/hard algorithms questions, 3 questions, had to at least solve 2 of them and the 3rd if you had time it seemed.
Architectural was based on a system they already had, pretty interesting to build out with the interviewer
I applied through a recruiter. I interviewed at Invisible Technologies in Feb 2025
Interview
Met with recruiter and then immediately had two technical interviews, one coding/leetcode, the next system architecture. I got rejected, and here's a snippet of the email verbatim:
However, after careful consideration, we’ve decided not to move forward. [INSERT FEEDBACK AS TO WHY NOT MOVING FORWARD].
I'm glad I wasn't given the opportunity to work for a company as careless as this one,
Interview questions [1]
Question 1
JSON manipulation leetcode problem; system architecture involving developing new REST APIs