<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Dahlia</title>
    <description>The latest articles on DEV Community by Dahlia (@dahlia177).</description>
    <link>https://dev.to/dahlia177</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F1299540%2Fa29d5598-9364-49ed-b323-57877a3c8639.jpg</url>
      <title>DEV Community: Dahlia</title>
      <link>https://dev.to/dahlia177</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/dahlia177"/>
    <language>en</language>
    <item>
      <title>Screen resumes in minutes</title>
      <dc:creator>Dahlia</dc:creator>
      <pubDate>Wed, 06 Mar 2024 22:13:48 +0000</pubDate>
      <link>https://dev.to/dahlia177/screen-resumes-in-minutes-3e03</link>
      <guid>https://dev.to/dahlia177/screen-resumes-in-minutes-3e03</guid>
      <description>&lt;p&gt;I worked for a largish startup (140+ people) , and the biggest pain point I personally experienced when recruiting was the sheer volume of resumes I had to sift through. Between career fairs and online applications, at one point we had 3000+ applications for 4 SWE positions. The engineering team was still fairly small (30 people) and very selective, so we would usually manually look for certain schools, a master's degree, interesting personal projects etc.&lt;/p&gt;

&lt;p&gt;Unfortunately, at the scale we were at, it was virtually impossible to properly examine every resume. I was thinking about what would have helped me. I'm personally &lt;strong&gt;very against&lt;/strong&gt; "resume ranking" because I think it can be extremely biased, but I do think resume filtering is helpful, especially for roles with more defined criteria. I built a quick tool to test this (&lt;a href="https://distoresumes.streamlit.app/"&gt;https://distoresumes.streamlit.app/&lt;/a&gt;), and I'd love to hear thoughts / opinions.&lt;/p&gt;

</description>
      <category>recruiting</category>
      <category>ai</category>
      <category>llm</category>
      <category>discuss</category>
    </item>
    <item>
      <title>Automate your web app testing using ChatGPT ⚡️</title>
      <dc:creator>Dahlia</dc:creator>
      <pubDate>Sat, 24 Feb 2024 21:27:18 +0000</pubDate>
      <link>https://dev.to/dahlia177/automate-your-web-app-testing-using-chatgpt-11gj</link>
      <guid>https://dev.to/dahlia177/automate-your-web-app-testing-using-chatgpt-11gj</guid>
      <description>&lt;p&gt;In a nutshell:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;We built a web app and had to do lots of repeated manual testing after each push.&lt;/li&gt;
&lt;li&gt;Coding up tests early on just isn’t worth it, especially with the amount of updates they would need as the UI changes so frequently. &lt;/li&gt;
&lt;li&gt;BUT we have to test...&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;We built an LLM based tool that lets you write, run, and maintain tests for web applications in natural language. E.g., if you want to test the sign in flow, you would simply type "Sign in with email &lt;a href="mailto:test@example.com"&gt;test@example.com&lt;/a&gt; and password Passw0rd" and it would execute it for you plus show you a screen recording.&lt;/p&gt;

&lt;p&gt;Curious to hear thoughts here - is manual testing as much of a pain for other teams as it is for us?&lt;/p&gt;

&lt;p&gt;You can try it for free &lt;a href="//testing.distoai.com"&gt;here&lt;/a&gt; :) we would love to hear any and all questions / feedback!&lt;/p&gt;

</description>
      <category>chatgpt</category>
      <category>testing</category>
      <category>qa</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
