<?xml version="1.0"?>
<rss version="2.0">
   <channel>
      <title>My padlet by Farid Diaz</title>
      <link>https://padlet.com/fdiazb23/lyefyn8hhbb54fan</link>
      <description></description>
      <language>en-us</language>
      <pubDate>2024-09-17 14:06:18 UTC</pubDate>
      <lastBuildDate>2024-09-17 15:26:44 UTC</lastBuildDate>
      <webMaster>hello@padlet.com</webMaster>
      <image>
         <url></url>
      </image>
      <item>
         <title>Farid Diaz Vertel </title>
         <author>fdiazb23</author>
         <link>https://padlet.com/fdiazb23/lyefyn8hhbb54fan/wish/3123784520</link>
         <description><![CDATA[<p>This ethical dilemma touches on two crucial points; freedom of expression and the company's reputation. Below I will answer the questions according to my opinion:</p><p><br></p><p>Do you choose to hire the candidate despite his controversial posts on social media, knowing that it could damage the company's reputation and generate tension in the workplace?</p><p>In my opinion, personal beliefs and expressions on social media do not always reflect a person's professional behavior. It is important to differentiate between personal opinions and the behavior of the individual. It is essential for the company to foster an open work environment where the different opinions of its workers are respected, as long as it does not harm their colleagues and the company's image.</p><p><br></p><p>Or do you prefer not to hire the candidate, knowing that it could be seen as a violation of their rights and perpetuate a culture of censorship?</p><p>The other option is not to hire the candidate because of his attitudes on social media, as the company wants to protect its brand and internal harmony. In this case I would say that the company tries to ensure that its employees reflect the values ​​that characterize the company.</p>]]></description>
         <enclosure url="" />
         <pubDate>2024-09-17 15:03:29 UTC</pubDate>
         <guid>https://padlet.com/fdiazb23/lyefyn8hhbb54fan/wish/3123784520</guid>
      </item>
   </channel>
</rss>
