Find Interview Questions for Craft Silicon

Right Answer:
The common status codes in HTTP responses are:

- **200**: OK
- **201**: Created
- **204**: No Content
- **400**: Bad Request
- **401**: Unauthorized
- **403**: Forbidden
- **404**: Not Found
- **500**: Internal Server Error
- **502**: Bad Gateway
- **503**: Service Unavailable

Right Answer:
API testing is the process of verifying that an application programming interface (API) functions as expected, ensuring it meets the requirements for functionality, reliability, performance, and security. Tools that can be used for API testing include Postman, SoapUI, JMeter, RestAssured, and Swagger.

Right Answer:
HTTP methods are standardized request types used in APIs to perform actions on resources. The main methods are:

1. **GET**: Retrieve data from a server.
2. **POST**: Send data to a server to create a new resource.
3. **PUT**: Update an existing resource on the server.
4. **DELETE**: Remove a resource from the server.
5. **PATCH**: Apply partial modifications to a resource.

These methods define the action to be performed on the specified resource in the API.

Right Answer:
A web service is a standardized way of allowing different applications to communicate over the internet using protocols like HTTP. It provides a method for applications to exchange data and perform operations. An API (Application Programming Interface) is a set of rules and tools that allows different software applications to interact with each other. A web service is a type of API that specifically uses web protocols to enable this interaction.

Right Answer:
Webhooks are user-defined HTTP callbacks that are triggered by specific events in a web application, allowing real-time data transfer. They differ from APIs in that APIs require a request to be made to receive data, while webhooks automatically send data when an event occurs without needing a request.

Right Answer:
We prioritize features or tasks in an Agile sprint using a combination of factors like business value, risk, effort/size, dependencies, and urgency. Product Owner usually leads this, using techniques like MoSCoW (Must have, Should have, Could have, Won't have) or story pointing, to ensure the most valuable items are tackled first.

Right Answer:
"In one project, we underestimated the complexity of integrating a new third-party API. This caused us to miss our sprint goal. To address this, we immediately re-estimated the remaining work, broke down the integration into smaller, more manageable tasks, and increased communication with the API vendor. We also temporarily shifted team focus to prioritize the integration, delaying a lower-priority feature for the next sprint. Finally, in the sprint retrospective, we implemented a better vetting process for third-party integrations to avoid similar issues in the future."

Right Answer:
A product backlog is a prioritized list of features, bug fixes, tasks, and requirements needed to build a product. It's managed through regular refinement, prioritization, estimation, and updates based on feedback and changing business needs, often facilitated by the Product Owner.

Right Answer:
To facilitate effective sprint retrospectives, I would:

1. **Set the Stage:** Create a safe and open environment where the team feels comfortable sharing.
2. **Gather Data:** Collect information about what went well, what didn't, and any challenges faced during the sprint.
3. **Generate Insights:** Facilitate a discussion to identify root causes and patterns.
4. **Decide on Actions:** Collaborate to define specific, actionable, measurable, achievable, relevant, and time-bound (SMART) improvements.
5. **Close the Retrospective:** Summarize action items and assign owners.
6. **Follow Up:** Track progress on action items in subsequent sprints to ensure continuous improvement.

Right Answer:
The Agile Manifesto values:

* **Individuals and interactions** over processes and tools.
* **Working software** over comprehensive documentation.
* **Customer collaboration** over contract negotiation.
* **Responding to change** over following a plan.

That is, while the items on the right have value, we value the items on the left more.