Open to new opportunities
Full Stack Developer | Software Engineer
Building scalable web, API and mobile applications with 7+ years of real-world software development experience.
I build and maintain full-stack applications end to end: React and Angular front ends, .NET and PHP back ends, REST APIs, relational and document databases, and Flutter mobile apps. My work spans enterprise clinical systems, CRM and reporting dashboards, learning platforms, internal business tools and a multi-app food delivery ecosystem.
Introduction
I am a software developer based in Hyderabad, India with 7+ years of professional experience building web applications, APIs and mobile apps across several languages and frameworks.
Most of my work has been on applications that were already live and already mattered to someone: enterprise clinical systems, CRM and reporting dashboards, learning platforms, internal business tools and consumer mobile apps. That shapes how I work — I spend time understanding the existing architecture, data model and business rules before changing anything.
I can take a business problem, work inside an existing codebase, design or modify the API, build the UI, shape the database, troubleshoot the production issue, and ship the feature.
Works across the whole stack
Front end, back end, API, database and mobile. I can own a feature from interface through to schema rather than handing it across boundaries.
Productive in existing codebases
Much of my work has been on systems I did not write. Reading code, mapping dependencies and making safe, targeted changes is a core skill.
Comfortable with production
Investigating live issues, reading logs, reproducing defects and shipping fixes without breaking adjacent behaviour.
Breadth across domains
Clinical/healthcare, CRM, education and food delivery. Each domain came with its own rules, constraints and vocabulary to learn.
Expertise
Grouped by where they sit in the stack. Select any technology to see the projects, articles and experience behind it.
Selected work
Case studies covering the problem, the architecture, my contribution and what I took away.
Workflow-driven clinical application with role-based access, dashboards and enterprise integrations.
Record management, multi-criteria filtering, reporting and role-scoped dashboards for internal business teams.
Courses, content structures, learner progress workflows and administrative dashboards.
Experience
Experience spanning enterprise clinical systems, CRM and reporting platforms, learning applications, internal business tools, consumer mobile apps and freelance delivery support.
Clinical / Healthcare · Full-time · Nov 2022 — Present
Worked on enterprise clinical applications involving structured workflows, business rules, role-based access, reporting dashboards and integrations with surrounding enterprise systems.
CRM / Business Applications · Full-time · Sep 2019 — Oct 2022
Developed CRM and internal business applications: record management, multi-criteria search and filtering, reporting dashboards, exports and role-scoped access for different business teams.
Education / EdTech · Full-time · Oct 2019 — Aug 2022
Contributed to a learning platform covering user and cohort management, course and content structures, learner progress workflows, administrative dashboards and supporting APIs.
How I work
The habits that decide whether software keeps working after it ships.
Before changing a system I want to know what it does today: the business requirement behind the ticket, the existing architecture, what depends on what, and which constraints are real. Most bad changes come from solving a problem that was described rather than the one that exists.
Technology choices follow the problem, the team and the timeline — not whatever is currently fashionable. A boring solution that the team can maintain usually beats an elegant one that only its author understands.
A clear contract between front end and back end lets both sides move independently and makes a second client — a mobile app, an integration, an internal tool — a small addition rather than a rewrite. Consistent resources, predictable errors, explicit versioning.
Authentication and authorisation belong on the server and in one place. Validate input at the boundary, apply least privilege, keep secrets out of client code and configuration files, and be deliberate about how sensitive data is stored and logged.
Code is finished when it can be operated: structured logging, meaningful error handling, a deployment that can be repeated, and enough visibility to diagnose an issue without reproducing it locally first.
Working across several stacks and domains means regularly being the least knowledgeable person in the room about something. Learning deliberately — and writing down what is worth keeping — is part of the job.
Writing
Notes on problems worth writing down.
Most professional software work is changing code somebody else wrote. A practical method for getting productive in an unfamiliar codebase quickly — an...
AI tooling is genuinely useful for the mechanical half of development. The engineering judgement it does not replace is the half that decides whether...
Seven years across .NET, PHP, React, Angular and Flutter. The frameworks differ far less than they appear to — and what transfers is more valuable tha...
Capabilities
Alongside long-running product work, much of my experience is being brought into an application that already exists — to fix what is broken, finish what is unfinished, or extend what is working. I deliver in the codebase’s own conventions and hand over notes the team can act on.
Production issue investigation
Reproduce the defect, trace it to its source, ship a verified fix.
Bug fixing in existing codebases
Targeted changes in code I did not write, without disturbing what works.
Feature development
Complete in-flight work under deadline pressure.
API development
New endpoints or extensions against existing contracts and clients.
Database fixes & tuning
Schema corrections, data repair, indexing and slow-query work.
UI development
Front-end features and fixes on established applications.
Performance troubleshooting
Slow endpoints, slow queries, slow pages — measured, then fixed.
Legacy application support
Keeping older applications running and improving them incrementally.
Technical consultation
Approach, trade-offs and sequencing before the work starts.
For businesses
If you are starting or growing a business and are not sure whether you need a website, a mobile app or a CRM — or how to get one built — reach out. Together with a small, trusted team of freelance developers, I work directly with business owners to turn an idea into software that helps more people find, reach and buy from them.
A fast, search-friendly site that explains what you do and turns visitors into enquiries.
Android and iOS apps for customers, delivery partners or your own staff.
One place to track customers, leads, orders and reports instead of scattered spreadsheets.
01
We start with a conversation about what you sell, who your customers are and where time or money is being lost today.
02
You get a clear, plain-language plan: what we will build, in what order, what it costs and how long it takes.
03
Work is delivered in small steps you can see and try, so feedback shapes the product while it is being built.
04
We go live, set up search visibility and analytics, and keep improving so the business reaches more people.
No technical knowledge needed — just tell us about your business and what you want it to do.
Talk about your businessOpen source
Public repositories and languages, pulled from the GitHub API and cached.
GitHub activity is not connected yet
The GitHub API could not be reached. Repositories and languages will appear here once it responds.
Visit my GitHub profileGet in touch
Tell me what you are building, what is in the way, and what a good outcome looks like. I read every message and reply personally.