Phool.co Software Engineer Interview: Rounds, Questions and Preparation

What the job involves

A software engineer at an Indian unicorn or high-growth startup like Phool.co builds and ships features across the stack, often owning a small service or module end to end. Expect to write production code, debug live issues, work with product and operations teams, and iterate quickly based on user feedback. The role rewards speed, ownership, and comfort with ambiguity over perfect process.

Role and technical knowledge

1. 1

   Explain the difference between an array and a linked list. When would you choose one over the other in a startup codebase?

   Cover memory layout, access time, and insertion or deletion cost. Add a practical example like a queue for order processing where linked lists help with frequent inserts.

2. 2

   What happens when you type a URL into a browser and press enter? Walk through the full request flow.

   Mention DNS lookup, TCP handshake, HTTP request, server processing, and rendering. Show you understand where caching and load balancers fit in.

3. 3

   How would you design a simple REST API for a flower ordering system with products, carts, and orders?

   Name resources, HTTP methods, status codes, and a basic schema. Discuss idempotency for order creation and pagination for product lists.

4. 4

   What is the difference between SQL and NoSQL databases? Which would you pick for a fast growing e commerce startup and why?

   Compare schema flexibility, scaling, and consistency. Give a reasoned choice, for example SQL for orders and NoSQL for product catalog or session data.

Practical scenarios and problem solving

1. 5

   A feature you built is working in staging but failing in production. How do you debug it?

   Describe checking logs, environment variables, data differences, and recent deploys. Show a systematic approach from reproduction to fix and verification.

2. 6

   You need to add a new payment method to an existing checkout flow with minimal disruption. How do you approach it?

   Talk about reading existing code, writing tests, feature flags, and rolling out gradually. Mention handling failure cases and user communication.

3. 7

   Your team lead asks you to optimize a slow API endpoint. What steps do you take?

   Start with measurement using profiling or query logs. Then suggest indexing, caching, reducing payload, or async processing, and verify with benchmarks.

4. 8

   You are given a bug report with vague steps to reproduce. How do you handle it?

   Show you ask clarifying questions, try to reproduce, narrow down the cause, and write a test to prevent regression. Mention documenting findings for the team.

Behavioural and teamwork

1. 9

   Tell me about a time you had to learn a new technology quickly for a project or hackathon.

   Use the STAR method. Focus on how you prioritized learning, built a small prototype, and delivered something working under a deadline.

2. 10

   Describe a situation where you disagreed with a teammate on a technical approach. How did you resolve it?

   Show respect for the other view, use data or a small experiment to decide, and commit to the final decision even if it was not yours.

3. 11

   Give an example of a project where you took ownership beyond your assigned tasks.

   Highlight initiative, like fixing a bug you noticed, improving documentation, or helping a teammate. Connect it to startup values of ownership and speed.

4. 12

   How do you handle feedback that your code needs significant changes?

   Show you separate ego from code, ask questions to understand, and treat review as a learning opportunity. Mention a specific instance if possible.

HR and motivation

1. 13

   Why do you want to work at a high growth startup like Phool.co instead of a large established company?

   Talk about impact, learning speed, and wearing multiple hats. Show you understand the company's mission and the ambiguity of startup life.

2. 14

   Where do you see yourself in three years as a software engineer?

   Be honest but align with growth in technical depth and ownership. Mention wanting to mentor juniors or lead a small module, not just a title.

3. 15

   What are your salary expectations for this role?

   Research typical fresher ranges for Indian startups. Give a range based on skills and location, and say you are open to the overall package and learning.

4. 16

   Do you have any questions for us?

   Ask about the tech stack, team structure, code review culture, or how success is measured in the first six months. Avoid questions only about perks.