This layout is ideal for engineers who value clarity, design discipline, and thoughtful technical storytelling. It keeps the profile focused on systems thinking, contribution quality, and long-term craft.
I design and build distributed systems that serve millions of users with sub-100ms latency. My engineering philosophy centres on clarity over cleverness, correctness over speed, and simplicity as the ultimate sophistication.
Currently: Principal Architect at [Company Name] — designing the next generation of real-time data infrastructure.
Open Source
I believe that good open-source work is the most honest form of an engineering portfolio.
Active maintainer of:
artemis — A zero-dependency, sub-microsecond event bus in Rust. 2.4k ⭐
nullsafe — Type-safe nullable handling for Go, inspired by Haskell's Maybe. 1.1k ⭐
Open to: Principal / Staff Architecture roles at companies that take engineering craft seriously.
Not open to: Unpaid work, "equity only" arrangements, or roles that don't involve real systems problems.
<!-- ========================================================
🖥️ GitHub Profile README — The Minimalist System Architect
Clean, text-focused, philosophy-driven engineering identity.
======================================================== -->
# Priya Sharma
> *"Perfection is achieved not when there is nothing more to add, but when there is nothing left to take away."*
> — Antoine de Saint-Exupéry
---
Software Architect · Open Source Contributor · Systems Thinker
San Francisco · [priya.dev](https://priya.dev) · [priya@priya.dev](mailto:priya@priya.dev)
---
## Work
I design and build distributed systems that serve millions of users with sub-100ms latency.
My engineering philosophy centres on **clarity over cleverness**, **correctness over speed**,
and **simplicity as the ultimate sophistication**.
Currently: Principal Architect at **[Company Name]** — designing the next generation
of real-time data infrastructure.
Previously: Staff Engineer at [Prev Company] · Senior SWE at [Earlier Company]
---
## Open Source
Everything I build professionally informs what I contribute to publicly.
I believe that good open-source work is the most honest form of an engineering portfolio.
**Active maintainer of:**
- **[artemis](https://github.com/your-username/artemis)** — A zero-dependency, sub-microsecond event bus in Rust. *2.4k stars*
- **[nullsafe](https://github.com/your-username/nullsafe)** — Type-safe nullable handling for Go, inspired by Haskell's Maybe. *1.1k stars*
- **[schemagen](https://github.com/your-username/schemagen)** — CLI tool generating type-safe clients from OpenAPI 3.1 specs. *847 stars*
**Notable contributions:**
- Submitted 12 patches to the Linux kernel (networking subsystem)
- Core contributor to [envoy-proxy](https://github.com/envoyproxy/envoy) — merged 6 PRs
- Contributed SIMD optimisations to [ripgrep](https://github.com/BurntSushi/ripgrep)
---
## Technology
**Languages I trust:** Rust · Go · C · Python · SQL
**Infrastructure I design with:** Linux · eBPF · Kafka · Postgres · Redis · gRPC · Protobuf
**Tooling philosophy:** Reach for the standard library first. Add a dependency only when the cost of building is truly higher than the cost of owing.
---
## Writing & Thinking
I write infrequently but carefully at [priya.dev/writing](https://priya.dev/writing).
Recent posts:
- [*Why Most Microservices Are Actually Distributed Monoliths*](https://priya.dev/writing/distributed-monoliths) — 34k reads
- [*The Hidden Cost of Eventual Consistency*](https://priya.dev/writing/eventual-consistency) — 21k reads
- [*Rust Isn't Hard — Its Complexity Is Honest*](https://priya.dev/writing/rust-honest-complexity) — 18k reads
---
## Currently Reading
- *A Philosophy of Software Design* — John Ousterhout
- *The Art of Doing Science and Engineering* — Richard Hamming
- *The Unix Programming Environment* — Kernighan & Pike
---
## GitHub Activity

---
*340 pull requests merged across 47 repositories · 12 Linux kernel patches · 4.5k GitHub stars earned*
---
Open to: **Principal / Staff Architecture roles** at companies that take engineering craft seriously.
Not open to: Unpaid work, "equity only" arrangements, or roles that don't involve real systems problems.
---
<sup>Updated June 2024 · Built with intention, not templates.</sup>
Section-by-Section Architecture Breakdown
Engineering managers and technical recruiters review dozens of GitHub profiles every day. They spend an average of 10 to 15 seconds scanning a candidate's profile README. This template is structured to maximize scanning velocity and convey technical capability instantly:
01. Animated Hero & Title
Uses SVG typewriter text to state your core title and stack immediately without forcing the reader to scroll.
02. Tech Stack Shields
Standardized Shields.io badges enable instant visual categorization of languages, frameworks, and cloud tooling.
03. Featured Project Matrix
Replaces plain repo links with a 3-column table showing project purpose, tech stack, and direct live demo links.
Before vs. After Profile Impact
❌ Default / Unoptimized Profile
Blank repository README, generic bio ("I like building stuff"), missing live demo links, no contact info for recruiters.
✅ ReadmeDesign Optimized Profile
Clear role positioning, standardized tech badges, 3x recruiter response rate, live demo links, and active commit streak cards.
Recruiter & Engineering Lead FAQ
Q: How many pinned repositories should I include?
A: We recommend 2 to 4 high-quality repositories. Each repository should have a live demo link, a clean README file, and explicit technical details explaining your architectural choices.
Q: Do GitHub stats cards update automatically?
A: Yes! Dynamic widgets like github-readme-stats fetch real-time data directly from the GitHub API every time someone views your profile.