I applied online. I interviewed at WorkFlex in Feb 2026
Interview
Applied for a remote full-stack engineering role. The process started with a timed 2.5-hour coding challenge (Java Spring Boot + Angular), submitted via private GitHub repository. Received detailed written feedback from the engineering team on both backend and frontend — feedback was specific, constructive, and positive overall. Was then invited to a recruiter screening call. During the call, the recruiter discussed specific contract details: named the EOR partner for my country, confirmed the annual salary, explained the benefits package including equity and a monthly wellbeing budget, described the onboarding process, and outlined the next interview rounds. The tone was clearly "closing" — as if I was already moving forward. The recruiter said she would confirm the next interview date the following day.
The next afternoon — less than 24 hours after discussing compensation, contract structure, and onboarding timelines — I received a one-paragraph rejection email referencing other candidates with stronger English skills. No follow-up call, no second interview, just a template. The gap between what was communicated during the screening and what arrived the next day was significant. A word of caution for candidates based in countries where the company has no legal presence: the cost of hiring through a third-party employer service may work against you behind the scenes, even if your technical performance is strong. Nobody will flag this during the process — you will simply receive a generic rejection with a different reason. To the hiring team: if contract terms, salary, and onboarding details are shared with a candidate during a screening call, that candidate will reasonably assume they are progressing. Either align internally before making those commitments, or stop making them.
Interview questions [1]
Question 1
Timed take-home coding challenge: build a full-stack workation management application in 2.5 hours using Java, Spring Boot, Angular, and SQL. Submitted via private GitHub repo. Evaluated on completeness, architecture, code quality, and testing.