Fliggy logo

Fliggy interview questions

From 1 candidate account, updated Oct 12, 2026

Candidate accounts
1
Rounds on average
1
Rounds in every loop
1

How the loop works

This guide draws on 1 first-hand interview account from Nowcoder. Candidates describe about 1 round on average, most often technical interviews.

These 1 writeup cover software engineering roles. All of them were posted under a forum handle, so we could not verify the authors’ identities.

See open roles at Fliggy

Interview experiences at Fliggy

Java Backend Engineer (Intelligent Customer Service)

Outcome not shared

Experienced. 1 round. Shared by 橘子皮375 on nowcoder, 1970-01-01

  1. 1First roundTechnicalAbout an hour of project discussion, backend and JVM questions, then two live coding tasks: merging sorted lists in constant space and an LRU cache.Covered: Platformization tradeoffs, Message queues, RPC service discovery, JVM memory allocation, OOM and Full GC troubleshooting, Linked lists, LRU cache

Fliggy interviews: FAQ

What is the interview process like at Fliggy?
This guide draws on 1 first-hand interview account from Nowcoder. Candidates describe about 1 round on average, most often technical interviews.
What topics does Fliggy test in interviews?
Commonly reported topics include Platformization tradeoffs, Message queues, RPC service discovery, JVM memory allocation, OOM and Full GC troubleshooting, Linked lists.

These guides summarize public, first-hand interview experiences shared by candidates. They describe the shape of each loop and the topics that came up, not a leaked question bank, and every experience links back to its original source. Processes change often. Treat this as directional prep, not a script.