writesonic logo
Writesonic· Full Stack Developer

WriteSonic | Full Stack Developer - Interview Experience

Posted
21 May 2025
292 reads

Summary

I interviewed with WriteSonic for a Full Stack Developer role across four rounds covering technical concepts, frontend coding, system design, and open-ended technical discussion. Although the final feedback was not positive, it was a valuable learning experience.

How it went

I had a chance to interview with WriteSonic for Full Stack Developer Role.

A third party agency reached out to me informing that your profile seems impressive and they are sending it to WriteSonic for screening. Within 3 days, I got a call that I have been shortlisted and asked the availability for interview.

Round 1: Technical Round

  • Find output of given JS code. Tested knowledge of promise, event loop and callback queue.
  • Find output of given react code. Tested knowledge of batching.
  • What is Event loop
  • Difference between concurrency and parallelism.
  • What is virtual dom and why its used.
  • ACID properties
  • AWS RDS benefits
  • Why choose next.js Framework
  • Microservices and Monolithic advantages and disadvantages

Round 2: Frontend Coding Round

  • Given a problem statement, Asked to code the basic frontend (No CSS) with proper functionality. Code should be modular, clean and working. Modified it according to the Follow-ups.

Round 3: Design Round

  • Asked to design a flow when user uploads any document in chatgpt and receives the response in text format. Gave a High level design about the services involved, Rate-limiter, load balancing, database, storage, cache, messaging queue etc. After that, we dived deep into the functionalities of each services, limitations, failure handling, extensibility etc. There were some limitations that a user can't upload more than 10k documents, user after uploading 1 document, cannot upload before a certain interval.

Round 4: Technical Discussion - Open ended

  • This was sort of a technical discussion. Given 1000 unlinked blogs, Design a flow or algorithm to perform internal linking among those blogs efficiently. Had a good discussion regarding the functions required, data structure, ML algorithm to extract anchor tags, score computation etc. At the end, told to design postgres db schema for the same.

Result - Final round feedback was not positive. Overall, it was a great learning experience.

Questions asked (11)

  1. 01

    JavaScript Promise, Event Loop, and Callback Queue Output

    Data Structures & Algorithms

    Find output of given JS code. Tested knowledge of promise, event loop and callback queue.

  2. 02

    React Batching Output

    Data Structures & Algorithms

    Find output of given react code. Tested knowledge of batching.

  3. 03

    What is Event Loop?

    Data Structures & Algorithms

    What is Event loop

  4. 04

    Difference between Concurrency and Parallelism

    Data Structures & Algorithms

    Difference between concurrency and parallelism.

  5. 05

    Virtual DOM and its Use

    Data Structures & Algorithms

    What is virtual dom and why its used.

  6. 06

    ACID Properties

    Data Structures & Algorithms

    ACID properties

  7. 07

    AWS RDS Benefits

    Data Structures & Algorithms

    AWS RDS benefits

  8. 08

    Why Choose Next.js Framework?

    Data Structures & Algorithms

    Why choose next.js Framework

  9. 09

    Microservices vs. Monolithic Advantages and Disadvantages

    Data Structures & Algorithms

    Microservices and Monolithic advantages and disadvantages

  10. 10

    ChatGPT Document Upload System Design

    System Design

    Asked to design a flow when user uploads any document in chatgpt and receives the response in text format. Gave a High level design about the services involved, Rate-limiter, load balancing, database, storage, cache, messaging queue etc. After that, we dived deep into the functionalities of each services, limitations, failure handling, extensibility etc. There were some limitations that a user can't upload more than 10k documents, user after uploading 1 document, cannot upload before a certain interval.

  11. 11

    Efficient Internal Linking for 1000 Unlinked Blogs

    System Design

    Given 1000 unlinked blogs, Design a flow or algorithm to perform internal linking among those blogs efficiently. Had a good discussion regarding the functions required, data structure, ML algorithm to extract anchor tags, score computation etc. At the end, told to design postgres db schema for the same.

Know someone preparing? Send it to them:WhatsAppLinkedInX

Interviewed at Writesonic recently?

Write up your rounds while you still remember the questions. It helps the next person more than you would think.

Share your experience
Discussion 0

Questions for the author, or how your own interview compared.

Join the discussion

Sign in with Google to comment or ask the author a question.

No comments yet

Be the first to share your thoughts and start the discussion!