· 1 min
experience
the short version is that i have been the first engineer somewhere three times. the full list, with dates, is on the career page — these are the three that shaped how i build.
founding engineer · brekfuz
- built the answering layer, where source permissions are resolved before generation rather than after it
- one answer splits by clearance: the cleared part in the channel, the restricted remainder to the asker alone
- held the tenant boundary in the database rather than in application code, and made the services refuse to boot without it
founding ai engineer · hey amara
- moved the message-queuing layer off redis and onto rabbitmq, and reworked every path through it
- built the email generation subsystem on a multi-source retrieval pipeline over vector similarity search
- built the compaction that holds a long conversation inside its token budget by summarising into a schema, not prose
applied ai engineer · ultrasafe ai
- six extraction engines over every clinical document, reconciled by vote instead of trusting one parser
- three representations per chunk — dense, sparse and late-interaction — so an exact drug name survives what an embedding blurs
the work itself, with the decisions attached, is in building. the version with dates in a table is the résumé.