Hello, I'm Priyansh Sharma/ Backend & Distributed Systems Engineer

I make the complicated parts work together.

I'm a software engineer at Thales. I take complex, open-ended problems from requirements through architecture, implementation, and validation. My work spans distributed systems, backend orchestration, stateful workflows, and AI-powered developer tooling.

I care about understanding the whole problem, making deliberate tradeoffs, and building systems that stay reliable, understandable, and adaptable as they evolve.

NOIDA, INDIABACKEND ARCHITECTUREDISTRIBUTED SYSTEMSAPPLIED AI & LLM SYSTEMS

01 / SELECTED WORK

A few problems I've spent time on.

Not a list of everything I've touched. These are the kinds of engineering problems that have shaped how I think and work.

01 / DISTRIBUTED PROCESSINGPROFESSIONAL WORK

Designing the core engine for distributed billing.

Usage-based billing had to apply configured prices and discount tiers per device or across a tenant's usage. Splitting that work across workers meant preserving the pricing rules and knowing when the report was complete.

I independently architected and implemented the core bill-run engine, from mapping through reporting. I used Cassandra-backed coordination to preserve stage progress across worker interruptions and make recovery part of the execution design.

Read the engineering case study
Professional experience with conceptual illustrations; disclosure review remains outstanding.
A SYSTEM, IN STAGES FIG. 01
01MapDistribute work
02ReduceAggregate
03FinalizeBuild output
COORDINATION MATTERS BETWEEN THE BOXES.↗
02 / SYSTEM DESIGNPROFESSIONAL WORK

Redesigning the framework for Fleet interactions.

Fleet decisions and calls were spread across existing Order Scheduler paths. In October 2026, I designed and implemented a centralized Fleet interaction framework, separating side-effect-free planning from execution. I introduced it in stages, with established scheduler and provider-facing behavior as a compatibility constraint.

Read the engineering case study
Professional experience with a conceptual diagram; employer disclosure review remains outstanding.
SEPARATE THE CONCERNS FIG. 02
DECIDEPlannerWhat should happen?
DOExecutorHow does it happen?
ILLUSTRATIVE, NOT AN INTERNAL DESIGN DOCUMENT
03 / SELF-INITIATED ENGINEERINGTEAM-ADOPTED TOOLING

Helping AI keep up with a real codebase.

While working with large backend codebases at Thales, I kept seeing AI tools lose important architecture and context between sessions. I took the initiative to build a persistent engineering knowledge system using AST-aware indexing, structured context, Qdrant/Neo4j retrieval, and MCP integrations. My entire team later adopted it.

Explore this initiative
Self-initiated during professional engineering work; shared conceptually without private implementation details.
CONTEXT OVER TIME FIG. 03
01 Architecture decisions ↗
02 Working conventions ↗
03 Lessons from changes ↗
KEEP WHAT MATTERS. RETRIEVE IT WHEN NEEDED.

A note on these projects: some of my most substantial work has been on private systems. I share the engineering ideas and lessons, not proprietary code, configuration, or customer details.

BEYOND THE HIGHLIGHTS

These aren't all the things I've built. There's independent AI work, earlier algorithm projects, and plenty of curiosity behind the case studies.

Explore all projects

02 / EXPERIENCE

Where I've built and grown.

A concise view of my professional journey. The engineering case studies above explore selected problems in greater depth.

Thales

Noida, India

FEB 2023 — PRESENT

Building backend and distributed systems across processing, orchestration, provisioning, and AI-powered engineering tooling.

  1. Software Engineer IIJan 2024 – Present
  2. Software Engineer IAug 2023 – Jan 2024
  3. Software Engineer InternFeb 2023 – Aug 2023

Vinsol

Delhi, India

JUN 2022 — JUL 2022

Software Development Engineer Intern

Worked on Ruby on Rails backend development and regression test automation using Selenium and Cucumber.

BEFORE THE PROFESSIONAL WORK

Algorithms and competitive programming were an important part of how I got here. I've kept the original results, rankings, and supporting records in one place.

Explore achievements & credentials

03 / A LITTLE ABOUT ME

Engineer by profession. Curious by default.

I started with algorithms and competitive programming while studying Computer Science at JIIT. I enjoyed breaking problems down, understanding the constraints, and finding solutions that were both efficient and correct.

Working on backend systems at Thales gave me a different perspective. A solution isn't just about getting the right output anymore. It's also about what happens across services, how state is managed, what breaks under failure, and whether someone else can understand the design. I enjoy being involved in that entire process — from figuring out the requirement to designing, implementing, and validating the system.

That curiosity extends beyond my day job. I spend time on algorithms, distributed systems, and AI-powered developer tools, particularly ways to make large codebases easier to understand and work with. I like learning how things work, questioning how they could work better, and then building something to find out.

04 / THINGS I'VE LEARNED

The details are the work.

A few lessons I keep coming back to. None of them are glamorous. All of them matter.

01

Failure paths deserve first-class attention.

Retries, duplicates, partial results, and recovery aren't edge decorations. They're part of the design.

02

Simple to explain is a useful design constraint.

If a change needs too many exceptions to make sense, I usually need to revisit the boundaries.

03

Measurements need context.

A benchmark is meaningful when you can explain the workload, environment, and what was actually measured.

05 / SAY HELLO

Have an interesting problem?

I enjoy talking about backend engineering, distributed systems, tooling, and the tradeoffs behind building software. Feel free to reach out.