Senior Software Developer
I’m Pranav Arora, a Senior Software Developer focused on building scalable, data-driven, and technically meaningful software systems.
Senior Software Developer | Energy Software | Cloud & AWS | GIS
I build software that turns engineering and energy data into practical decision tools: full-stack products, AWS and geospatial systems, and simulation workflows. At Angler Solutions I contribute to MESO (Model for Energy Systems Optimization) across hybrid energy modelling, GIS analysis, and cloud infrastructure.
Senior software developer building data-driven products for energy systems, AWS and GIS, and simulation workflows.
I’m Pranav Arora, a Senior Software Developer focused on building scalable, data-driven, and technically meaningful software systems.
I am a software engineer with a strong foundation in full-stack development, cloud systems, and applied problem solving. My work has evolved from general web and application development into platforms that combine software engineering with energy systems, geospatial workflows, and decision-support tools.
I work as a Senior Software Developer at Angler Solutions on MESO (Model for Energy Systems Optimization), a platform for planning and optimizing hybrid energy systems. Scope spans backend services, frontend capabilities, GIS integrations, AWS deployments with Terraform, serverless systems, simulation workflows, and technical planning across software, modelling, and leadership teams.
What excites me is solving technical problems that connect software with real-world impact: systems that are scalable, well-structured, and clear enough for decision-makers and technical users.
Senior Software Developer with experience in cloud-based platforms, full-stack applications, and technically complex products. Currently focused on simulation workflows, GIS-enabled analysis, and AWS architecture on MESO. Strong background in backend systems, frontend development, cloud modernization, and technical problem solving.
I build energy systems software from design through release: product engineering, cloud architecture, GIS, and delivery discipline.
Four areas I keep in balance:
I stay with the full arc from intent through architecture, implementation, and stakeholder communication, so engineers, modellers, and leadership hear one coherent story instead of reconciling handoffs.
Senior Software Developer, Angler Solutions · St. John’s, NL. These are the product and platform priorities I am driving on MESO today.
MESO (Model for Energy Systems Optimization) is Angler’s platform for techno-economic analysis and optimization of hybrid energy systems. I contribute across engineering and architecture: how services and workflows are shaped, how simulation is exposed in the product, and how the platform should evolve.
What I’m driving on MESO lately:
I bring together capabilities that often sit in separate people. Fewer handoffs, faster alignment from idea to implementation, and one person who can follow a thread from architecture through delivery and stakeholder communication.
I am especially effective where a product needs someone who can hold the technical detail, shape a coherent solution, and help the platform grow into something more mature and easier to evolve.
Highlights from recent product and platform work on MESO: cloud modernization, GIS, simulation, reporting, platform economics, and delivery discipline.
Designed a structured cost modeling approach for MESO to estimate, track, and scale the economics of individual simulation workloads in the cloud.
This involved:
This work bridges the gap between engineering and business by enabling transparent, scalable, and monetizable platform usage.
Helped steer MESO from a heavier container-centric posture toward a more serverless, AWS-native shape. The platform scales and changes without environment drift; IaC and peer review are now part of how we ship.
Shipped product depth around maps, land suitability, and spatial constraints so planning conversations reference the same geography the models use, not a disconnected spreadsheet.
Tightened how complex simulations surface in the app with clearer steps, fewer sharp edges for users, and a structure the team could extend without rewriting the same glue each time.
Pushed reporting and scenario comparison toward outputs people can brief from: less raw dump, more interpretable comparison when models disagree.
Turned novel technical approaches into architecture and workflow narratives counsel could work with, so filings reflected how the system actually behaves rather than a slide-deck sketch.
Aligned roadmaps and technical storylines with grants and partner programs (AWS, partners, regional collaborators) so funding asks matched what engineering could commit to.
Raised the bar on how we branch, test, release, and document. Fewer surprises in production and easier onboarding for anyone picking up a feature cold.
Built and deployed MERLIN (MESO Ensemble Reservoir Level Intelligence Network) end to end—a 14-day probabilistic lake-level forecasting system for a hydroelectric utility in Newfoundland. It replaced a static spreadsheet heuristic with a weather-driven, dispatch-conditioned deep-learning forecast that answers the real operational question: given a planned generation schedule over the next two weeks, what's the P10/P50/P90 trajectory of the reservoir level?
This involved:
Hybrid energy modelling, simulation surfaces, and platform evolution. Most of my public GitHub activity aligns with production work.
Maps, constraints, and site intelligence. Geospatial UI and analysis threads reflected in repositories and notes.
Serverless and infrastructure-as-code work: AWS, Terraform, and deployment patterns documented in code and notes.
Outputs, comparisons, and communication of model results. Themes tied to reporting UX and analytics.
Secure backend workflows using token-based authentication to support anonymous and cross-platform research interactions.
Where I go deepest: full-stack engineering, cloud delivery, geospatial products, platform economics, and product leadership.
Technologies and tools I use regularly in production work.
Recent coding activity (WakaTime).
Beyond implementation: connecting engineering with product strategy and decision-ready technical design, including cost modeling and platform economics where product meets business model.
In addition to software development, I work on areas that connect engineering with product and business impact:
Employment history, education, and related background.
Senior Software Developer with experience building cloud-based software platforms, full-stack applications, and technically complex products. Currently focused on simulation workflows, GIS-enabled analysis, and AWS architecture through work on MESO at Angler Solutions.
Memorial University of Newfoundland, Canada
Courses included:
Cisco Systems, Bangalore
Contributed to the Cisco Contact Center Operations Suite (CCOps) project, aiding Cisco Engineers in troubleshooting Contact Centre issues through automated log collection and problem resolution using the Known Error Database Engine.
Bharat Sanchar Nigam Limited, Jhansi, U.P., India
Understood about how mobile and landline communication works and how a call is setup.
The Electronics Club, SRMIST, Chennai
SRM Institute of Science and Technology, Chennai
Holy Cross Higher Secondary School, Datia, M.P., India
Cathedral College, Jhansi, U.P., India
Angler Solutions, St. John’s, NL, Canada
Memorial University of Newfoundland, St. John’s, NL
Canadian Blood Services, St. John’s, NL
Memorial University of Newfoundland, St. John’s, NL
Earlier roles included web development, software engineering, training, and technical mentoring, which built the broad foundation that now supports platform engineering, cloud systems, and specialized technical software.
Writing on software engineering, architecture, cloud and GIS, and practical workflows—tools, patterns, and lessons from building technical products.
Dev.toSchedule a short introductory call to discuss career guidance, cloud and platform topics, delivery architecture, or related technical questions. Use the calendar below, or email first if you prefer to align before booking.
This is an introductory meeting — 15 minutes, subject to availability. It’s a chance to align on goals and see if there’s a fit; deeper work or a formal engagement can be discussed as a follow-up.
Request by email Open scheduler in new tabOpen to discussions on cloud architecture, energy and geospatial products, and technical collaboration—including IP-aware system design, funding, and partner ecosystems where relevant.
Prefer email or a social profile? Use the cards below. For a longer note or inquiry, use the form — I read every message.
This form is powered by Google Forms (via Formfacade).