This week, I concentrated on improving the user experience from the applicant’s point of view—more especially, on uploading resumes. I achieved this by using a Supabase storage bucket, fittingly called “resumes.” Particularly in keeping an orderly and effective HRM application, this strategy enables a simplified and safe way of preserving applicant documentation.
Control of the kinds of files accepted during file uploads helps to prevent any possible problems. I opted to limit uploads for our HRM program to PDF and DOCX formats. These formats are globally accepted and guarantee that, independent of the device or software used for viewing them, the content is kept as intended. I also defined a 500 KB file size limit. Practical factors drove this choice; for instance, my one-page CV runs under 200 KB. Common among more seasoned candidates, two-page resumes can be accommodated by the liberal 500 KB limit.
I changed our Prisma structure on the backend to include a string field holding the URL of the uploaded résumé. This element is absolutely essential since it connects the applicant’s profile to their resume, thereby enabling recruiters to quickly access and check records. These developments not only improve the candidate user experience but also increase the general dependability and functioning of our HRM system. Emphasizing both user experience and technical efficiency keeps top importance as we keep developing this project. In next week’s update, I will display the resume to the recruiter and parse the skills listed.
I have also been trying to teach my teammates to use Github’s pull request feature. pull requests allow our team to do code review in a structured way to prevecnt mishaps as we merge our code together.
References:
YouTube. (n.d.). Image from the video “ozaK3rNppbM”. YouTube. Retrieved from https://www.youtube.com/watch?v=ozaK3rNppbM