<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: AlexisAguirre</title><link>https://news.ycombinator.com/user?id=AlexisAguirre</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Wed, 02 Sep 2026 08:28:57 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=AlexisAguirre" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by AlexisAguirre in "Ask HN: Who wants to be hired? (September 2026)"]]></title><description><![CDATA[
<p>Location: Córdoba, Argentina
Remote: Yes, remote only
Willing to relocate: No
Technologies: TypeScript, React, Next.js, Node, GraphQL with Apollo, Playwright, Python, SQLite, Postgres, LLM agents, MCP servers, RAG, promptfoo evals, OpenTelemetry
Résumé/CV: <a href="https://portfolio-aguirre-alexis.vercel.app" rel="nofollow">https://portfolio-aguirre-alexis.vercel.app</a>
Email: aguirrealexis.cba@gmail.com<p>I do not trust what I have not verified, including my own code.<p>Full-stack dev, 5+ years, last year building LLM products rather than demos. Everything below is something I found by auditing my own work, not by reading about it.<p>intent-gate — <a href="https://www.npmjs.com/package/intent-gate" rel="nofollow">https://www.npmjs.com/package/intent-gate</a>
A job posting with hidden instructions got my CV pipeline to write ten years of Kubernetes into my resume. Technology I have never touched. The system prompt told it to use only what was in my facts file and it obeyed the posting instead. What stopped it was a deterministic validator comparing every named technology against ground truth, no model in the loop. A prompt is a request. A check is a guarantee. I published the routing pattern as a library.<p>job-hunter — <a href="https://github.com/ale-aguirre/claude-job-hunter" rel="nofollow">https://github.com/ale-aguirre/claude-job-hunter</a>
Autonomous job search agent running on my own search. It taught me that my own verifier was lying to me. It counted a URL redirect as a successful application. Aggregate confirmation sat at 78 percent and looked healthy, until I graded per channel and found four integrations at 100 percent and one at zero out of sixty, silently dead for months. The average was hiding it. That number was on my CV and I removed it.<p>DocUnify — production, private
Document comparison SaaS running at an Argentine auto parts manufacturer, 72 employees, in a domain audited against IATF 16949 and ISO 9001. Two people there use it for their actual work. The part I would defend under questioning is the semantic reclassification after the LLM call, because the model kept flagging paraphrases as real differences and embeddings catch that.<p>This week — <a href="https://github.com/theam/facility/pull/242" rel="nofollow">https://github.com/theam/facility/pull/242</a>
Merged a fix into an open source AI SDLC project and filed two issues, one about an agent being able to write the field that marks its own check as platform verified. I reproduced the bug on my own machine first and my first repro was a false negative, because bash was eating the backslashes in my test payload.<p>English C1 written, B2 spoken. Open to full-time or contract.</p>
]]></description><pubDate>Tue, 01 Sep 2026 15:59:09 +0000</pubDate><link>https://news.ycombinator.com/item?id=49523815</link><dc:creator>AlexisAguirre</dc:creator><comments>https://news.ycombinator.com/item?id=49523815</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49523815</guid></item></channel></rss>