Mateusz Kocioła
// summary
Self-taught software engineer with 4+ years building test automation, internal tooling, and CI/CD for validation-critical systems — currently automating GPU driver validation at Intel. Comfortable across Linux, Python, and Ansible as well as the full web stack; equally at home owning infrastructure or shipping a polished product end to end.
// experience
Core contributor on a four-person team that built an end-to-end automated GPU validation environment from scratch, supporting driver validation ahead of release.
- Owned all test automation — machine provisioning, test execution, and results/database handling (Ansible, Python) — reaching production use in under 6 months.
- Automated real-world user-scenario validation (driver benchmarks, games, desktop applications) across multiple GPU generations, replacing largely manual workflows.
- Implemented and automated GPU virtualization testing using SR-IOV.
- As the work grew to integrate more projects and a wider validation scope, kept building automation and new features across the team's tooling (Ansible, Python) — including multi-cluster test orchestration with Slurm — while co-owning all CI/CD.
- Driving the consolidation of separate tools into a single platform integrated with existing internal testing infrastructure; tooling relied on daily by multiple teams.
Sole owner of a fuzz-testing initiative for internal microservices — inherited from a stalled start and brought into production.
- Raised fuzz-testing coverage from ~5% to 70%+ across Node.js (and some C++) microservices.
- Built and optimized CI/CD pipelines to run fuzzing continuously, reusing already-fuzzed inputs to cut redundant runs.
- Automated code-coverage reporting.
Developer on an internal HPC (high-performance computing) testing environment, building automation and internal tooling while helping the team level up.
- Scaffolded three internal full-stack web apps to automate team workflows — ticket creation, test execution, and regression finding; two became durable, daily-use team tools.
- Trained teammates in web development so they could extend these tools independently.
- Tuned low-level, bare-metal performance settings (environment configuration, CPU/GPU pinning) to increase workload throughput.
- Automated synchronization with internal testing services (Python, GitHub Actions) and integrated open-source and in-house HPC applications.
- Maintained and extended the environment (Bash, Python) across multiple Linux distributions (RHEL, SLES, Ubuntu); handled debugging, issue isolation, and code review.
Run a one-person web studio building static websites for individuals and small businesses end to end — design, development, client management, and post-launch support.
- Design and build static sites with Astro, Tailwind, and Figma, consistently scoring 95+ on Google PageSpeed Insights.
- Deliberately ship static architecture so clients can't break their own sites — minimizing maintenance and support overhead.
- Own the full engagement from scoping to ongoing support; recently brought on a collaborator to take on more work.
// selected projects
- Minesweeper: Refined The classic, redesigned for iPhone.
- mkociola.github.io Portfolio website
- SwiftLedger A personal-finance ledger app built in Swift.
- weird-grep A weird multithreaded grep
- CUT A multithreaded CPU usage tracker, written in C
- typer An app to test your typing abilities
// skills
- Languages
- C / C++ · Python · Bash · TypeScript · Swift
- Systems
- Linux (RHEL · SLES · Ubuntu) · Ansible · Slurm · Docker · SR-IOV
- Web
- Astro · Tailwind · Vue · Node.js · Figma
- Practice
- CI/CD · GitHub Actions · Test automation · Fuzz testing · HPC