Add cover letter for HSP Group Principal AI Engineer

2026-06-10 23:21:08 +02:00
parent 5feae3b2a1
commit 0ddee94590
2 changed files with 81 additions and 0 deletions
@@ -0,0 +1,81 @@
+%-------------------------
+% Cover Letter — HSP Group, Principal AI Engineer
+%-------------------------
+\documentclass[a4paper,9pt]{article}
+\usepackage{extsizes}
+
+\usepackage[a4paper,left=2.5cm,right=2.5cm,top=2.5cm,bottom=2.5cm]{geometry}
+\AtBeginDocument{\fontsize{10.5}{14}\selectfont}
+\usepackage[utf8]{inputenc}
+\usepackage[T1]{fontenc}
+\usepackage{helvet}
+\renewcommand{\familydefault}{\sfdefault}
+\usepackage[hidelinks]{hyperref}
+\usepackage{fontawesome5}
+\usepackage{xcolor}
+\input{glyphtounicode}
+\pdfgentounicode=1
+
+\pagestyle{empty}
+\setlength{\parindent}{0pt}
+\setlength{\parskip}{8pt}
+
+%-------------------------------------------
+\begin{document}
+
+%---------- HEADER ----------
+\begin{center}
+  {\LARGE\textbf{Adam Ladachowski}} \\[4pt]
+  {\small Warsaw, Poland \enspace|\enspace Remote \enspace|\enspace EU Citizen} \\[3pt]
+  {\small
+    \faIcon{envelope}\enspace\href{mailto:adam@saiden.dev}{adam@saiden.dev} \quad
+    \faIcon{github}\enspace\href{https://github.com/aladac}{aladac} \quad
+    \faIcon{linkedin}\enspace\href{https://linkedin.com/in/aladac}{aladac} \quad
+    \faIcon{phone}\enspace\href{tel:+48535329895}{+48\,535\,329\,895}
+  }
+\end{center}
+
+\vspace{12pt}
+
+\begin{flushleft}
+{\small June 10, 2026}
+\end{flushleft}
+
+\vspace{2pt}
+
+\textbf{Re: Principal AI Engineer --- HSP Group}
+
+\vspace{4pt}
+
+Dear Hiring Team,
+
+I'm writing to express my interest in the Principal AI Engineer role at HSP Group. I build AI agent systems for a living --- not as demos, but as the primary way my team ships software. I believe that experience maps directly to what you're building at Gateway HR.
+
+\textbf{What I bring:}
+
+\begin{itemize}
+  \setlength{\itemsep}{4pt}
+  \setlength{\parsep}{0pt}
+
+  \item \textbf{Production agent orchestration.} I designed and operate a multi-host platform with specialist agents (code, infrastructure, communications) that dispatch tasks across machines, maintain persistent memory, and execute multi-step workflows autonomously. This isn't a proof-of-concept --- it's how I develop daily.
+
+  \item \textbf{RAG at scale.} My semantic memory system (SQLite + vector embeddings, 5{,}500+ entries) powers hybrid retrieval across code, documentation, and operational knowledge. I've built the full pipeline: ingestion, chunking, embedding, hybrid FTS5/cosine search, and agent-facing retrieval APIs.
+
+  \item \textbf{Multi-agent SDLC integration.} I run dedicated agents for GitHub automation (issues, PRs, project boards), infrastructure management, and communications --- operating in parallel, reporting to a dispatcher. The pattern you describe (separate agents for planning, coding, testing) is my daily workflow.
+
+  \item \textbf{20 years of B2B SaaS.} Ruby/Rails across telecom, media, proptech, and event ticketing. I've built platforms from zero as sole engineer (Roomzilla), scaled them to 180K+ users across 90 countries (Jampack), and led teams through major refactors and migrations.
+
+  \item \textbf{Open source proof of work.} Six public repositories demonstrating the stack: browser automation for AI agents, voice cloning, LoRA fine-tuning pipelines, and developer tooling --- all shipped and maintained at \href{https://repos.saiden.dev/aladac}{repos.saiden.dev/aladac}.
+
+\end{itemize}
+
+I'm drawn to HSP Group because you're applying AI to a domain with real regulatory complexity --- exactly the kind of problem where agents need guardrails, validation, and human oversight baked in from the start. The ``architects of intent'' philosophy you describe in the role is how I already work and how I believe engineering teams should evolve.
+
+I'd welcome the opportunity to discuss how my experience building these systems from scratch can accelerate AI adoption across your engineering organization.
+
+\vspace{16pt}
+
+Best regards,\\
+Adam Ladachowski
+
+\end{document}