Distributed systems
Designing service boundaries, asynchronous workflows, and failure-aware interactions that stay understandable as systems grow.
Senior Backend & Platform Engineer
10+ years across Sweden and India, focused on system design, backend APIs, platform ownership, and maintainable engineering. Core strengths include distributed systems, enterprise integrations, AWS infrastructure, and pragmatic product delivery.
Current focus
Go services • distributed APIs • platform reliability
Platform expertise
AWS • Kubernetes • data integration • cloud systems
Proof of impact
Enterprise analytics, telecom, and workflow-heavy products
Writing topics
Architecture notes • scaling lessons • offline-first design
Highlights include architecture thinking, technical ownership, and delivery depth across enterprise backend and cloud environments.
Highlights
Engineering focus
The work is strongest where systems need clear ownership, dependable integrations, scalable backend behavior, and practical engineering trade-offs.
Designing service boundaries, asynchronous workflows, and failure-aware interactions that stay understandable as systems grow.
Building backend services on AWS with practical attention to deployment flow, operability, and long-term platform ownership.
Shaping explicit contracts, data movement paths, and integration logic so products can evolve without fragile coupling.
Improving throughput, caching behavior, and hot-path simplicity where responsiveness and reliability directly affect user trust.
Favoring maintainable architecture choices that support team clarity, observability, backward compatibility, and safe change.
Exploring AI features as engineered systems with attention to reliability, guardrails, explainability, and useful delivery workflows.
About
I'm Mahesh Chandra, a software engineer with over a decade of industry experience across analytics, telecom, healthcare, and finance platforms. I focus on building scalable backend systems, integration-heavy services, and maintainable architecture that teams can operate confidently over time.
I hold a Double Degree Masters in Software Engineering from Blekinge Institute of Technology (M.Sc), Sweden, and Andhra University (M.Tech), India. During my studies I wrote research articles on mobile networks and software quality — a habit of thoughtful communication that still influences how I work today. My current interests span Go services, cloud platforms, software quality, and AI-assisted engineering workflows.
Built and maintained enterprise-scale integrations for analytics and data movement workflows.
Worked across telecom, healthcare, finance, and data platforms with cross-functional product teams.
Writing and research habits continue to shape how architecture decisions, trade-offs, and ownership are communicated.
Current chapter
Here you'll find more than a résumé: technical ownership, system thinking, and reasoning behind design choices — not just a list of technologies.
Expanding backend depth through practical Go service design, clean APIs, and reliability-oriented engineering patterns.
Deepening platform knowledge around deployment behavior, observability, and scalable service operations.
Ownership
Backend delivery, API design, integration quality
Writing
Architecture notes · cloud lessons · maintainability
Focus
Go, AWS, distributed systems, AI-assisted workflows
Skills
The stack reflects hands-on delivery in enterprise settings: Java and Go services, cloud platforms, CI/CD automation, and modern frontend work where product teams need end-to-end ownership.
7 technologies
4 technologies
4 technologies
5 technologies
5 technologies
Career
Experience spans enterprise software, telecom platforms, and data systems — with work shaped around platform scale, backend complexity, cross-functional execution, and long-lived engineering ownership.
Professional experience
Software Engineer
Qlik
Gothenburg, Sweden
Contributing to enterprise-scale data integration platforms supporting analytics and workflow automation, with ownership across backend services, reliability improvements, and cross-team delivery.
Software Engineer (Consultant)
Sigma Technology · Ericsson
Sweden
Consulted for Ericsson on telecom software platforms, contributing to distributed backend systems, platform modernization, and large-scale engineering coordination where reliability and maintainability were critical.
Software Engineer
Innominds Software
India
Delivered production systems for Deloitte and Broadridge across healthcare, finance, and telecom domains, owning delivery from implementation through release and being recognized as Performer of the Month.
Software Engineer
MSQAA BDL
India
Started in software quality assurance, strengthening release confidence, defect visibility, and engineering rigor on production-focused projects.
Academic background
M.Sc. in Software Engineering
Blekinge Institute of Technology (BTH)
Karlskrona, Sweden
Double Degree Masters programme. Wrote research articles on mobile networks and software quality. Completed a thesis on software engineering topics.
M.Tech in Software Engineering
Andhra University College of Engineering
Visakhapatnam, India
Double Degree partner programme alongside the M.Sc. at BTH, deepening theoretical and applied software engineering foundations.
B.Tech in Information Technology
J.N.T.U
Hyderabad, India
Undergraduate foundation in computing, algorithms, and information systems.
J2EE Certified
NIIT Technologies
Certified in "Developing Enterprise Applications and Web Services using J2EE Technologies".
Architecture notes
The goal is to make system thinking visible: why certain decisions matter, where the trade-offs are, and how architecture choices support reliable delivery over time.
Cloud patterns
Notes on designing secure download flows, handling throughput trade-offs, and keeping operational ownership clear when large-file delivery grows.
Read noteEngineering philosophy
A practical view on choosing service boundaries, abstractions, and team-friendly architecture decisions that age well.
Read noteProduct architecture
Patterns from building calmer mobile UX with local caching, resilient sync behavior, and responsive search in variable connectivity conditions.
Read noteBackend systems
Current focus areas include service design in Go, explicit API contracts, and operational clarity across backend and platform work.
Read noteArchitecture visuals
These are intentionally lightweight, but they show how the work is framed: boundaries, flows, degraded behavior, and operational clarity.
System snapshot
Make reading and search feel local-first, then synchronize or refresh when connectivity allows.
System snapshot
Keep security boundaries explicit while minimizing hot-path complexity and preserving observability.
System snapshot
Separate source systems, workflow orchestration, and downstream consumers so scaling does not create hidden coupling.
Projects
This section includes only publicly visible GitHub repositories.
Recruiter-focused portfolio that presents backend and cloud engineering work through concise case studies and MDX writing.
• App Router architecture with reusable section components
• MDX-powered blog and metadata routes for SEO
• Production-ready deployment flow for Vercel
Mobile reading app exploring reliable, offline-friendly user flows with search and local caching behavior.
• Cache-aware architecture for unstable network conditions
• Mobile-first search and browsing interaction design
• API integration with practical local data persistence
Product concept focused on media-led storytelling and timeline navigation in a mobile-first experience.
• Narrative-first UX exploration
• Mobile interaction design experimentation
• Structured app flow around timeline-driven usage
Earlier public Java project that reflects long-running backend and engineering fundamentals.
• Core Java backend implementation
• Practical software structure and module boundaries
• Foundational engineering learning archive
GitHub activity
Contribution activity sits alongside selected repositories so visitors can quickly inspect current build habits, technical interests, and public project depth.
TypeScript · Next.js
my-portfolio-vercel
Current portfolio implementation with stronger engineering storytelling, MDX-driven writing, and senior backend/platform positioning.
Live demo availableView repositoryDart · Flutter
quietly
Flutter mobile app exploring offline-first reading UX, API-backed book discovery, and calmer product design.
View repositoryDart · Flutter
life-replay
Mobile app concept centered on storytelling, timeline navigation, and media-centric interaction patterns.
View repositoryJava
fxtalks
Older Java project that still helps surface long-running backend interests alongside newer portfolio and mobile work.
View repositoryWriting
Writing is used to document architecture decisions, cloud lessons, Go/backend interests, and the practical engineering trade-offs behind maintainable systems.
A short architecture note on secure file delivery, throughput, and operational trade-offs when downloads grow on AWS.
A senior-engineering view on why maintainability, team clarity, and operational ownership often matter more than fashionable architecture choices.
Lessons from building mobile experiences that stay calm, responsive, and useful when connectivity is inconsistent.
Contact
Email is still the fastest route, and the form below can prepare a ready-to-send message in your mail client.
Direct email
hello@ymchandra.in
Download resume
Mahesh Chandra Resume