This one is mainly intended to document my recently completed Circle 's interview experience sharing, from the OA to the subsequent interview rhythm, question type, preparation mode, all try to speak clearly and can be landed, after the preparation of similar fintech positions for students to do reference.Circle overall process bias engineering, Coding question style is also relatively close to the real business development, rather than the pure brush type of questions.
Opening: two CodeSignal OA's arrive at the same time
In mid-May I received two CodeSignal OA links almost on the same day, corresponding to the two positions I applied for. Both sets of tests were Industry Coding Assessment Type.
Each Assessment has only one big question, but it requires you to write complete code, pass all hidden tests, and have a clean code structure. You can choose any language you want, Java, Python, C++.
Before the test starts, the system will ask you to check the local environment (camera/screen/sound) and confirm the IDE configuration. At first I thought it was just a normal CodeSignal environment, but Circle gives you "half sandbox + half local IDE", so you should familiarize yourself with the practice mode beforehand, otherwise you'll be a bit confused in the official test.
OA Recall of questions and overall difficulty
While I can't remember the exact title (and Circle doesn't allow leaks), the overall style is:
- Deviation from engineered implementations (e.g., handling multiple module inputs, integrating logic, being aware of boundary cases)
- It's not a small amount of code.
- It's more like you're writing a "landable feature."
This kind of OA does not require much algorithmic depth, but it is very examined:
- Code readability
- Whether the choice of data structure is justified
- Is the process logic rigorous
- Ability to write a runnable engineering-level function within a time limit
For students who are used to writing one or two line trick solutions for LeetCode, this kind of OA is a new challenge.
Approximate pace of follow-up interviews
After passing the OA, Circle will schedule the normal interview process:
- Behavioral / Culture Fit
- Technology Coding Round -- LC + business logic at medium level of preference
- System / Architecture Discussion -- Lightweight system design
- Team Match
Interviewers are generally fast paced, questions are given straight, no beating around the bush, and your answers should be structured and clear about your trade-off.
Passing experience sharing: how I steadily walked through Circle OA + VO this time
This time, the Circle process was quite long: two CodeSignal OA, three rounds of VO (Coding, System Design, Behavioral). To be honest, if I rely on myself, I will probably turn over in the middle of the process. But this time, I left the preparation of OA and VO to Programhelp Do the overall planning and the results are obvious.
I use the "No Trace Online" assist in the OA phase.
Circle's CodeSignal takes the route of big engineering problems, with a large amount of code and complex structure, which is not the same idea as brushing problems at all.Programhelp's teacher will synchronize my screen in real time through the untraceable way, and help me to plan the data structure, module splitting, boundary processing, and sorting logic in advance, and the whole process basically looks like a particularly experienced senior brother is standing beside me and constantly reminding me: "framework first", "types should be unified", "this case should pay attention to the date format", "this place should be O(n)". The whole process is basically like an experienced senior brother standing next to me and constantly reminding me: "write the framework first", "the type should be unified", "this case should pay attention to the date format", "this place should be O(n) write this place in O(n) format".
Program inputs and outputs, formatting requirements, and hidden tests all helped me tread very firmly.
In the end both OA's were AC'd at once, and I knew in my heart of hearts: it would be hard to write that cleanly on my own.
For the VO stage, I used the "VOReal-time voice assistance"
Circle's VO is not difficult in the questions, but in the structure, completeness and clarity of expression. Especially in System Design, if your thoughts are a little bit messed up, the other party will ask you questions to death.
Programhelp's VO assistants will remind me of key points in real time on my headset as I speak, for example:
- "Let's start with the conclusion and then expand on the details."
- "Now on to data flow."
- "Make up a trade-off."
- "Take the SLA out of the conversation."
- "Coding writes core logic first, don't get carried away by boundaries."
These tips won't answer for me, but they will prevent me from getting "disconnected" on key points.
Especially for System Design, when I was being pressed to the point of having no structure, as long as the assistant said "pull back to the target before disassembling the components", I could immediately stabilize my thoughts.
A few tips for students preparing for Circle
- CodeSignal environment must be familiarized in advance
- Engineering structure is more important than algorithms
- Behavioral preferably presses a set of "SBO / CAR" structures in advance.
- System Design answers: Problem → Goals → Architecture → Details → Monitoring
- If you are prone to messing up your expression, it is advisable to simulate a few rounds in advance
I wish you all the best of luck in getting through the interviews and getting the Offer of your choice!
