Product engineering
My work spans interfaces, backend systems and delivery, connecting product decisions with the engineering that brings them into production.
Swopnil Acharya · Perth, Australia
Business first.
Built with purpose.
Software Engineer · Product & Architecture
I build products and systems with their business context in mind—from a first build to the next chapter of a legacy platform.
Rooted in Nepal. Building from Perth.Product thinking. Architecture. Delivery.
Experience across VC-funded startups and established business systems.
Pre-seed Series A Series B
The business behind the build
From a blank page to the systems a business depends on.
My work has taken me through startups at pre-seed, Series A and Series B, products built from scratch, and established platforms carrying years of business knowledge. Each setting asks for a different kind of judgment.
At Foody Bag, a double charge meant a customer problem. A peak-time crash meant an order could fail. At Oil Commander, technical decisions sat inside the daily work of laboratories and mining customers. Understanding those consequences is part of the engineering work.
That is the perspective I bring to software engineering. I work with the business context, talk through requirements, and stay hands-on from the product decision through to the system running in production.
Experience & contribution
What I bring to the table.
Solution architecture
I approach technical decisions through the context of the team, the business constraints and the systems already in place.
Legacy modernisation
My experience spans ASP.NET Web Forms, .NET 8 APIs, background services and cloud and on-premise deployments, with an emphasis on understanding existing business workflows.
Teamwork & shared learning
Experience in onshore and offshore roles has shaped how I work with others. I value clear communication, useful feedback and making sure teammates have the context they need.
Working as part of a team
Good engineering is a team effort.
I’ve worked in both onshore and offshore roles, collaborating with people across locations and different parts of a product. That experience has made me appreciate how much clear communication and shared context matter to delivery.
I’ve also seen how different levels of support affect interns and junior engineers. Thoughtful onboarding, useful feedback and room to ask questions make a real difference to how people learn and contribute.
Those are lessons I carry into a team: listen, share what I know, ask when I need context, and help make the work easier to understand for the next person.
Experience in practice
Different businesses. Real delivery.
Customer trust & operational reliability
Apps People · Foody Bag
The sole backend and cloud engineer for a surplus-food marketplace with around 60,000 users. Fixed double-charging and order-flow race conditions with transaction changes and idempotency checks. Added tracing to investigate peak-time crashes and failed orders, and moved AWS infrastructure into a secure VPC layout.
Pre-seed · VC-backed
8Seats
Built real-time messaging features with Elixir Phoenix channels and local data storage. Used state machines to make complex product flows easier to understand, test and maintain, while designing for large conversations without adding unnecessary connection load.
Business continuity & customer requirements
Ozdocs Group · Oil Commander
Took ownership of a laboratory and equipment-monitoring platform processing over 100,000 oil samples daily. Worked directly with customers on requirements, delivered .NET 8 features, and supported deployments across AWS and on-premise environments.
End-to-end product delivery
Leapfrog · Nurix Therapeutics
Owned feature delivery for a proprietary drug-discovery platform: PostgreSQL schemas for scientific workflows, Java/Micronaut APIs and React/TypeScript interfaces for lab operations. Built access controls and monitoring around the needs of the scientists and their data.
Curiosity beyond the code
Understanding what makes a business work.
Learning is part of my daily routine. My interest in economics, markets and incentives sits alongside the technical work. I want to understand the domain, the people using a product, and the reason a feature matters.
Those questions belong in the engineering conversation: What problem are we solving? Who does it help? What is worth building next? What existing knowledge do we need to preserve?
Read what I am learningKeep in touch
Let’s connect.
Find me on LinkedIn, or email me directly.