- A recruiter reached out to me. - I had an interview with him - I received home assignment for JS algorithm optimizations task - didn't have time to solve it efficiently enough
I applied through an employee referral. I interviewed at Fingerprint
Interview
The interview went well, being quite standard and relatively high-level.
However, the take-home assignment is an absolute joke. After submitting a functional project, I was informed that it was not functional, but without any further details. The more I pushed for an explanation, with proof that it worked when they tested it, the more defensive they got and hit me with “our decision is final”.
Lady, I was over your company the second y’all couldn’t explain what was wrong.
The use of an assignment at all and the refusal to provide any useful feedback shows how little they value people’s time, and how incompetent the interviewing team was.
Interview questions [3]
Question 1
[Take Home]
Service providers offering free trials often face the issue of trial abuse, where
individuals or entities exploit these offerings in unintended ways. This typically
involves creating multiple accounts using different email addresses or other
credentials to repeatedly access the free trial, allowing them to use the service for
free over an extended period.
Your Task
Your challenge is to develop a web application that safeguards the signup process
against trial abuse for a fictional service offering free trials.
Deliverables
●
●
●
A publicly deployed URL for your web application with an accessible
root ( index ) page.
The page should include two text fields (username and password) and
a signup button.
Upon clicking the signup button, the user should be redirected to either:
➔
A /success page displaying an h1 with the text "Signed up successfully.
"
➔
A /failure page displaying an h1 with the text "Signup failed: ,"
where is a placeholder for one or more reasons why the signup
failed.
Requirements
1. One-Time Signup:
■ A user can sign up only once (Hint: Use visitorId).
■ On a successful signup, the user should be redirected to the
/success page.
■ Any subsequent signup attempts should redirect the user to the
/failure page.
2. Bot and Malicious User Detection:
●
Prevent signups from bots or users employing techniques such
as incognito mode, browser tampering, privacy settings, VPN,
or TOR.
●
These attempts should be redirected to the /failure page.
3. Browser Compatibility:
●
The application must work correctly on the latest versions of Firefox
(with default settings) and Chrome (with AdBlock Plus installed).
4. Implementation Details:
●
●
●
Focus on functionality rather than styling.
Username and password validation can be ignored.
Use TypeScript for the implementation (preferred).
Implement JS callback completion for different types of tasks that complete at different times, and aggregate the results without blocking. Basically JS callback hell
