The interview experience was good, but unfortunately, they revoked the position. They said a current employee was getting promoted for the role. I still would love to re-interview here. In my case, HR was very responsive, and I had a chance to interview with one of the renowned SDK developers, who held a very high position.

HM Round:

1. Introduction about your projects in detail.
2. Why you want to change now?
3. Team composition and day-to-day activities.
4. Any situation where you had a difference of opinion with your peers and how did you handle that.
5. What are you planning for your future in terms of professional goals?
6. What do you think about open-source applications if you compare them with enterprise applications?
7. Have you contributed to any open source?
8. Do you know how to work with GitHub?
9. How do you keep yourself updated with changing tech updates?
10. What do you look for in a team in which you work?
11. Do you openly communicate your thoughts to other peers or people while working?
12. How do you help your juniors in case of any issues?
13. Which tech stack are you familiar with (Terraform, Azure, e.g.)?
14. Lastly, which one would you choose between Ghost or Alien and why?

1st Technical Round:

1. Intro about yourself, and it should include projects that have served other developers (e.g., NuGet packages, etc.). They want to understand why you are looking for a change.
2. Have you contributed to any open source?
3. Which development tool is your favorite and why?
4. Based on the above introduction, related questions if any.
5. Have you worked with CI/CD pipelines? If so, how have you worked and whether you created them or not.
6. Have you worked with Terraform?
7. Have you worked with PowerShell?
8. What do you think should be an approach towards designing an SDK, thinking about a good developer experience?
9. What kind of security do you think should be in place in terms of APIs and SDKs?
10. A CodeSignal coding question: First, we have to explain the approach. Second, we have to code and pass all the test cases if possible. But the main focus is on the approach and thought process.
11. Another scenario-based coding question where we have to design an API with a few HTTP Methods. Here, they want to see the approach and considerations while designing an API as a service to other clients.
12. In between, there can be a few questions and conditions that can be asked or updated based on your approach.

8* CodeSignal:

Problem Description You are given an array of strings, names, representing filenames. The array is sorted in order of file creation, such that names[i] represents the name of a file created before names[i+1] and after names[i-1] (assuming 0-based indexing).

All files must have unique names. Files created later with the same name as a file created earlier should have an additional (k) suffix in their name, where k is the smallest positive integer (starting from 1) that does not appear in previous file names.

Your task is to iterate through all elements of names (from left to right) and update all filenames based on the above rules. Return an array of proper filenames.

Example Input: names = ["doc", "doc", "image", "doc(1)", "doc"]

Output: ["doc", "doc(1)", "image", "doc(1)(1)", "doc(2)"]

Similar LeetCode question: https://leetcode.com/problems/making-file-names-unique/description/

9* API Design Question:

API

1. GET /api/Applications # Get all Applications
2. GET /api/Applications/{id} # Get an Application by ID
3. POST /api/Applications # Add a new Application
4. DELETE /api/Applications/{id} # Delete an Application
5. PUT /api/Applications/{id} # Update an existing Application

Request Body | Response Body

1. None | Array of Applications
2. None | Application
3. Application | Application
4. None | None
5. Application | None