This guide draws on 5 first-hand interview accounts from Nowcoder. Candidates describe about 2 rounds on average, most often technical interviews, system design and a hiring manager interview.
These 5 writeups cover software engineering roles. All of them were posted under a forum handle, so we could not verify the authors’ identities.
New grad. 1 round. Shared by 在抱佛脚的芝士很完美 on nowcoder, 2026-09-14
1Second roundTechnicalLong project deep dive on an agent system followed by locking, storage and JVM performance troubleshooting questions.Covered: Agent tool calling, LangGraph orchestration, Observability, Vector database choice, Prompt iteration, Distributed locks, Row vs column storage, CPU and load troubleshooting
Backend Engineer
Outcome not shared
New grad. 1 round. Shared by 在抱佛脚的芝士很完美 on nowcoder, 2026-09-17
1Third roundTechnicalAgent platform scaling and reliability design questions followed by behavioral and career questions.Covered: Multi-tenant agent isolation, Agent memory persistence, Trace storage at scale, Large table optimization, Consistent hashing, Incremental re-execution, Agent error handling, LLM cost reduction, Conflict handling, Career path
Frontend engineer
Outcome not shared
New grad. 1 round. Shared by 牛客419260978号 on nowcoder, 2026-09-24
1First interviewTechnicalMostly conversation with some fundamentals and two coding tasks. Passed to round two.Covered: Light project questions, Ensuring AI code quality, BFS coding, Array to tree coding
Backend developer
Received an offer
New grad. 4 rounds. Shared by 噗噗通通 on nowcoder, 2026-09-29
1First interviewTechnicalBackground questions followed by Java, data structure and web security fundamentals.Covered: Motivation for Java and backend, Open source and learning sources, Floating-point precision, Thread safety and HashMap put flow, Deduplicating ten million numbers with bitmaps or HyperLogLog, SQL versus NoSQL, Index use with two single-column indexes, XSS defense
2Second interviewTechnicalForty minutes of rapid-fire knowledge questions across Java, algorithms, databases and networking.Covered: Java primitive sizes and BigDecimal, Atomicity and volatile, Dynamic proxies and GC, Thread interruption, Sorting a hundred million bounded integers, Linked-list cycle and XOR single-number, AVL versus red-black trees, Deadlock conditions, Normal forms and isolation levels, Joins, HTTP codes and network layers
3Third interviewTechnicalA fifty-minute deep dive into networking, JVM, storage and middleware choices from the project.Covered: TCP handshake and teardown, Blocking, non-blocking and async I/O, epoll, JVM collectors and generational GC, MySQL locking and high availability, Sharding and hash scaling, Redis hot data, distributed locks and CAP, Message queue delay versus scheduled jobs, Elasticsearch internals, Coin change
4Fourth interviewSystem designA shorter round on distributed systems and microservice resilience plus motivation.Covered: HTTP versus RPC, Token bucket and microservice rate limiting, LSM tree versus B+ tree, I/O-bound scheduling, Service fault isolation and recovery, Multi-tenant database design
Frontend Engineer
Outcome not shared
New grad. 2 rounds. Shared by 牛客419260978号 on nowcoder, 2026-10-08
1Second roundTechnical55 minutes of project deep dives and scenario design questions with no coding.Covered: Speech-to-text pipeline, Reconnection handling, React streaming SSR, Tauri IPC, Virtual scrolling, Canvas rendering for huge tables, Chunked uploads with Web Workers, Reviewing AI-written code, Dashboard filter design, Out-of-order responses
2Third roundHiring managerA 20-minute talk on motivation and overall fit with a few technical concepts.Covered: Motivation for frontend, JSBridge, React Native, WebGL vs WebGPU, AI coding usage, Memory issue debugging, Job priorities
Fanruan interviews: FAQ
What is the interview process like at Fanruan?
This guide draws on 5 first-hand interview accounts from Nowcoder. Candidates describe about 2 rounds on average, most often technical interviews, system design and a hiring manager interview.
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.