Smart Engineering & Design Solutions · 2023 – 2024
EmpowerCRM
A healthcare-staffing ATS/CRM that recruiters run their day inside: jobs, sourcing and client hospital accounts.
- Role
- Software Engineer: issue fixes, feature extensions and CRM maintenance
- Timeline
- Jul 2023 – Jun 2024
- Company
Smart Engineering & Design Solutions
- modules maintained
- 7modules maintained
- candidate records
- 500+candidate records
- release changelog, every update
- 1release changelog, every update
Overview
The problem
EmpowerCRM is the tool healthcare-staffing recruiters work inside all day: posting jobs, sourcing candidates and tracking client hospital accounts. A bug or a slow-to-ship feature request blocks their pipeline directly.
My job wasn't to design the product; it was to keep it reliable and moving — fix what recruiters reported, build the features they asked for, and extend existing modules without breaking the flows the team already relied on.
What I built
Highlights
Issue fixes, fast
Triaged and fixed reported bugs across the Dashboard, People, Companies, Jobs, Sourcing and Tasks modules, shipped on a cadence recruiters could see for themselves.
Feature requests
Turned recruiter asks into shipped features — list-view responsiveness, job-posting changes and pagination improvements among them — logged in an in-app announcements panel each release.
Jobs & sourcing
Extended the Jobs pipeline (lead, open, closed, won) and the Sourcing search-task flow that feeds new candidates into it.
People & companies
Worked on the People and Companies modules recruiters use to track candidates, hiring managers and client hospital/medical-center accounts.
Tasks & dashboard
Kept the task queue and dashboard (open jobs, today's tasks, release announcements) accurate as the underlying modules changed.
Engineering
Decisions that shaped it
- Treated this as a maintenance engineering job: small, targeted changes over rewrites, since the app carried live recruiter traffic every day.
- Shipped fixes and features behind an in-app changelog, so the team could see what changed each release without a separate release process.
Screens
