Andrew Persad, lead software engineer
Built to spec. Measured before it ships.
By day I lead frontend work on platforms serving 9 million users at HP, with prior builds for Eli Lilly and Amazon. At night I design, build, and run my own products end to end: five shipped and live, from a payroll engine tested to exact dollars to a group decision app rebuilt at one sixth its original size.
now: lead software engineer, open to lead roles
Selected work
03 of 05 studiesFork In The Road (written case study)
A group decision app that ends the "where should we eat" spiral. One link, everyone votes, no accounts required: guest identity is an HMAC-signed cookie holding zero personal data, and live results stream over Server-Sent Events.
The v2 rewrite deleted six of every seven lines, including whole subsystems that worked but were not the product, and runs with zero cron jobs: deadlines are enforced lazily on every read.
113k → 20k LOCoverlapp (written case study)
Group scheduling that finds when everyone is actually free. Members sync their real calendars or add recurring blocks by hand, and the group gets a live availability heatmap with proposals and quorum voting.
Recurrence expansion is hand-written plpgsql running inside Postgres, and privacy is enforced at the database layer: the group sees that you are busy, never why.
2 built · 1 livePersadPay (written case study)
Household payroll with real compliance consequences: statutory tax math, W-2 and W-3 generation, and NYS-45 quarterly filings for an actual household employee.
The tax engine cites IRS Publication 926 and NY DOL rules inline, and unit tests assert exact dollar amounts, including the scenarios where year-to-date wages cross a cap mid-payment.
6 filing artifacts
How I work
fig. 02 / three rulesDeletion is a feature
My favorite number in my favorite project is negative: a 113,000 line app rebuilt as 20,000 lines that do more. Scope discipline is a design tool, not an afterthought.
The unhappy path is the product
Empty, loading, and error states are where software actually lives. They get designed on purpose and tested in CI, in both color modes, instead of being discovered by users.
Measured beats claimed
Accessibility and performance run as build gates, not intentions: axe scans in light and dark, Lighthouse floors, and a bundle monitor. If a change slips, the build fails before anyone sees it.
Open to lead roles
I am looking for a lead software engineer seat where product judgment matters as much as delivery. The fastest way to reach me is the contact form. I reply within a day or two.