Recently, I worked on showing parsed resume data on the frontend of my HRM (Human Resource Management) job application for my capstone project. My application depends on this function since it lets recruiters rapidly review and assess important information from resumes without having to download or open separate files.
First I concentrated on the backend, using Supabase to manage data storage and authentication. Following resume processing, I organized the obtained information in my Postgres database. Getting this data on the frontend, created with React and TypeScript, and showing it in an understandable way came next.
I created a neat and simple UI with well-ordered parsed data including work experience, education, and skill set. Every time a recruiter clicked to view an applicant’s profile, I dynamically obtained the resume data using React hooks. This enhanced general performance by lowering the demand for extra backend searches and thereby improving the user experience.
But while the Vercel project was under way, I ran upon some unanticipated problems. Particularly, I found that authentication seems to desync sporadically between Vercel and Supabase. Frustrating user experiences such sudden log-off or inability to access specific application portions followed from this. Following some research, I found that Vercel’s handling of serverless functions and environmental variables—which occasionally resulted in session management inconsistencies—was the source of the problem.
I looked at several ways to help with this, including adjusting Vercel’s configuration settings and trying several session management methods in Supabase. Although the problem is not totally fixed, I am actively looking for a strong answer to guarantee flawless authentication in all surroundings. Particularly in terms of the subtleties of various hosting platforms, this experience has been a great teaching tool in the complexity of running full-stack apps.