About Praveen Patil
Associate Software Engineer at Brillio. Dedicated to building reliable, well-tested backend services, understanding low-level systems behavior, and writing clean, maintainable software.
Engineering Systems from First Principles
I believe that software engineering is fundamentally about understanding systems deeply, not just gluing together high-level abstractions. Whether it is analyzing how a relational query executes across foreign key constraints, verifying concurrency locks under load, or structuring clean API boundaries, my focus is on predictable, maintainable software.
Currently at Brillio, I work as an Associate Software Engineer, having converted on September 28, 2026, after completing an intensive engineering internship that began on March 5, 2026. In my day-to-day engineering, I contribute to backend service endpoints, participate in code reviews, write automated unit and integration tests, and uphold strict architectural hygiene.
My technical trajectory originated in rigorous computer science education—studying data structures, operating systems, networking protocols, and relational database internals. During university, I built practical software systems like Blogopedia to study session-based authentication lifecycles and normalized schemas from the ground up.
Beyond daily feature delivery, I spend time exploring distributed systems patterns, such as asymmetric credential brokering with PASETO v4 and Redis atomic locks (Vaultless), and decomposed event-driven microservices utilizing RabbitMQ and Spring Cloud (FitTrack).
Associate Software Engineer
Brillio · Sept 28, 2026 – Present
Converted from Software Engineer Intern (March 5, 2026 – Sept 27, 2026). Focused on backend services, clean architecture, automated testing, and team collaboration.
Bachelor of Engineering (B.E.)
Computer Science and Engineering
Foundations in Data Structures, Algorithms, Database Management Systems, Operating Systems, and Distributed Computing.
- • Backend Services & REST APIs
- • Relational & Polyglot Persistence
- • Asynchronous Event Messaging
- • Cryptographic Access Tokens
Core Engineering Philosophy
The principles that guide how I design, implement, and review production software.
I avoid shortcut patterns that suppress compiler warnings, bypass type safety, or postpone edge-case handling. Software should be mathematically verifiable from the initial commit.
Client-side validation is a user experience enhancement, never a security boundary. All service endpoints must enforce strict schema validation, sanitary boundary parsing, and injection defenses.
Features are not considered complete until backed by deterministic tests. Comprehensive unit and integration suites ensure that future refactoring can proceed with zero regression risk.
Every third-party package introduced into a project carries a maintenance, licensing, and vulnerability cost. I prefer standard library primitives and well-vetted, minimal frameworks.
Languages, Frameworks & Infrastructure
- • Python (Core, OOP, Async, Typing)
- • Java 21 (OOP, Streams, Collections)
- • TypeScript / JavaScript (ESNext)
- • SQL (PostgreSQL, MySQL, SQLite)
- • C / C++ (Memory, Data Structures)
- • Spring Boot 3 & Spring Cloud
- • Fastify & Express (Node.js)
- • Flask & Django (Python)
- • Redis (Atomic Locks, Caching)
- • RabbitMQ (AMQP Event Queues)
- • MongoDB Atlas (Document Modeling)
- • Next.js 16 (App Router, Turbopack)
- • Docker & Docker Compose
- • Vitest, Jest & Unit Testing
- • Git, GitHub Actions, CI/CD
- • Keycloak (OAuth2 PKCE Security)
- • Linux CLI & PowerShell Scripting