I appreciated the initial outreach, as it showed interest in my profile. Unfortunately, after missing the initial call (due to scheduling conflicts) and promptly responding with my availability, the communication stopped entirely. Despite several polite follow-up emails over the next few weeks inquiring about next steps, I received no response. After more than a month, the recruiter finally replied, noting that my profile had positive feedback but the team had been holding the position for another candidate who ultimately accepted the offer. The extended period of silence made the process feel disorganized and left me uncertain about my status. A quick update or acknowledgment during that time would have been helpful and more in line with standard professional practices. Pros: Initial recruiter outreach was proactive and indicated a good fit for my skills. Cons: Lack of timely communication after the initial contact. Advice to Management: Consider implementing better protocols for candidate updates, even if brief, to respect applicants' time and enhance the overall candidate experience. This could help maintain a positive reputation in a competitive talent market.

class Person { public string FirstName { get; set; } public string LastName { get; set; } } static class PersonExt { public static string FullName(this Person p) { return $"{p.FirstName} {p.LastName}"; } } 5) Are you familiar with any design patterns, such as singleton, builder, or template method? If so, please explain one design pattern and then write code that demonstrates it.