Pedro Simon

• Built and expanded a 510(k)-cleared Software as a Medical Device that makes clinical-review decisions on behalf of physicians and qualified staff across roughly 1.6 million plasma units a year for Parachute. It covers everything from enforcing a required test after the check-in questionnaire to evaluating incoming results and deciding what happens to each unit. The work it automates used to take a qualified reviewer 5 to 15 minutes per result set, with 2 to 4 sets per unit.
• Tech-led Lab Enhancements, which brought the number of samples drawn per donation down from 2 to 4 to as few as one while still running the same test panels. That saves plasma, vials, and processing time across all 1.6 million units a year.
• Re-architected the core test-results schema. The old one was denormalized and hardcoded, and it had caused production performance problems the team kept patching with brittle, expensive SQL views. The new model is normalized and leaves room to support more blood products and processes down the line.
• Built a component system in Rails ViewComponents, Tailwind, and Stimulus that's now reused across three apps, and contributed heavily to the company design system, including 15+ version upgrades and leading the Tailwind v4 migration. This sped up UI work across teams.
• Carried a large React-to-Rails migration, moving dozens of screens to ViewComponents and Hotwire/Stimulus. The old React-over-GraphQL setup was hard for the team to reason about and a steady source of bugs, so leaning into Rails conventions let us ship faster with fewer of them. Along the way I set up reusable patterns like FlowStepComponent and PageComponent that the rest of the team built on. Earlier I also helped move a React Native check-in kiosk toward the web so it was easier to change and matched the rest of our stack.
• Built a workflow engine from scratch for the operational processes that live outside the core blood-product system, like logging an adverse donor event. It works a bit like n8n: a form builder with conditional fields, multi-step flows with actions that change system state in between, a visual drag-and-zoom editor, versioning, and publishing.
• When the client acquired a new center, built a system in about a month to import that center's donors and their visit history on the fly, with Snowflake-backed matching and configurable lookback windows.
• Work as the senior IC on a team of five, setting technical direction and reviewing the team's work. I also share my AI engineering workflow regularly, for example walking the team through how I take a Jira ticket from start to finish with Cursor and Claude.

• Built Stakin's institutional staking dashboard from scratch as the only engineer on it. It pulls a client's addresses across 30+ blockchains into one portfolio view, with real-time APRs, portfolio history, and tax reports clients rely on for filing with their governments. Around 200 institutional clients were using it when I left.
• Ran blockchain data analysis to power the dashboard's portfolio metrics, APRs, and reporting across all those networks.
• Designed and shipped an OpenAPI that partners use to integrate against the dashboard's data.
• Led an SEO-focused redesign of the marketing site and pulled the company blog into it, which made the content easier to find and a better path into the staking products.

• Built a staking app for a proof-of-stake validator. It connected to users' wallets, pulled data directly from the blockchains, and surfaced it through dashboards. Built with Viem, Wagmi, and RainbowKit.
• Designed a referral system on top of the chain: stakers who delegated with a referral memo earned extra rewards, giving the validator a built-in growth loop.

• Helped build the integration layer that let Epion connect to different EHRs through a single adapter pattern, covering Epic, Cerner, and Athenahealth. It pulled in demographics, medications, allergies, and patient history.
• Built a telemedicine app during COVID (Twilio, React, Redux, Material UI) in about six weeks. It went live to real patients and providers for virtual visits.
• Led the frontend team, around 15 engineers at its largest, and built the company design system in React, Storybook, and Chromatic. The kiosk, mobile-web, and telemedicine apps all used it, which made spinning up new screens much faster.
• Built and maintained a browser extension for providers that surfaced things like appointments and patient context right inside Epic, Cerner, and Athenahealth.

• Ran my own software practice alongside my full-time roles. The main project was a production e-commerce and retail-management platform (Next.js, Nest.js) for a retailer, covering POS, inventory, and warranties, plus payment, shipping, and maps integrations. It handled real day-to-day operations.
• Owned the work end to end and eventually grew it into a team of five.

• Built full-stack features in React and Scala (Play) for an investment-portfolio tool at a large US bank. It interviewed investors to figure out their risk profile and then suggested opportunities. I also handled the DocuSign integration.
• Acted as the React champion for the team, shaping frontend patterns and best practices. Improved routing with the History API, stabilized the e2e tests, and cut frontend compile times through Webpack tuning.

• My first engineering job, at a software studio in Rosario, and where I cut my teeth. I worked across a lot of different client projects: management systems for architecture firms, an ERP for a food manufacturer, a ticketing app with an interactive stadium map for a local football club, and a good amount of web design.
• Built ERP modules from scratch with Zend, Doctrine, and JavaScript/Knockout, and helped tighten up the team's development practices.

Universidad Tecnológica Nacional

Engineer's degree in Information Systems · 2012–2017