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 | IP & System Design | Partnerships
I build software that turns engineering and energy data into practical decision tools — software, cloud, geospatial intelligence, and product delivery. I also work on software and system design in support of patent strategy, collaborate on funding and grant-aligned technical narratives, and engage with AWS, AWS partners, and local partners to align architecture and delivery with ecosystem programs. At Angler Solutions, I contribute to MESO (Model for Energy Systems Optimization): hybrid energy modelling, simulation, GIS analysis, and cloud-native infrastructure.
Senior software developer building cloud-native, data-driven products for energy and adjacent technical domains: energy systems, AWS and GIS, simulation, IP-aware design, and collaboration with partners and funding programs.
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. Over the years, my work has evolved from general web and application development into building more advanced technical platforms that combine software engineering with energy systems, geospatial workflows, cloud infrastructure, and decision-support tools.
Currently, I work as a Senior Software Developer at Angler Solutions, where I contribute to MESO (Model for Energy Systems Optimization) — a platform designed to support energy stakeholders in planning, evaluating, and optimizing hybrid energy systems. My work involves both product engineering and architecture, including backend services, frontend platform capabilities, GIS integrations, AWS deployments (including Terraform-based infrastructure and deployment strategy), serverless systems, simulation workflows, technical planning, and collaboration across software, modelling, and leadership teams. Beyond implementation, I contribute to software and system design work that supports patenting and technical disclosure, help shape narratives and artifacts for funding and programs, and collaborate with AWS, the AWS partner network, and local partners so platform decisions stay aligned with cloud programs and regional opportunities.
What excites me most is solving meaningful technical problems that connect software with real-world impact. I enjoy working on systems that are not only functional, but also scalable, well-structured, and clear enough to support decision-makers, technical users, and future product growth.
Senior Software Developer with experience building cloud-based software platforms, full-stack applications, and technically complex products. Currently focused on energy software, simulation workflows, GIS-enabled analysis, and AWS architecture through work on MESO at Angler Solutions. Strong background in software engineering, backend systems, frontend development, cloud modernization, and technical problem solving, with involvement in IP-oriented system design, funding collaboration, and AWS and local partner engagement. I am interested in building scalable products that connect engineering depth with real-world usability.
I build energy systems software end to end—product engineering, cloud architecture, GIS, and technical governance—from design through release. My current focus is MESO at Angler Solutions.
Four areas I keep in balance:
I stay with the full arc—intent, 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. That scope also includes IP-aware design, funding alignment, and cloud partner engagement alongside core product delivery.
What I’m driving on MESO lately:
I bring together capabilities that often sit in separate people—so there are 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, observable, and easier to evolve.
Highlights from recent product and platform work—cloud modernization, GIS, simulation, reporting, cost and platform economics, IP, partner programs, and delivery discipline—grounded in real engineering on energy systems software.
Designed a structured cost modeling approach for MESO to better understand, track, and scale the economics of simulation workloads in a cloud-native environment.
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—so the platform could scale and change without environment drift; IaC and peer review became part of how we ship.
Shipped product depth around maps, land suitability, and spatial constraints—so planning conversations could reference the same geography the models use, not a disconnected spreadsheet.
Tightened how complex simulations surface in the app—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, not a slide-deck sketch.
Aligned roadmaps and technical storylines with grants and partner programs—AWS, AWS partners, and 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.
Hybrid energy modelling, simulation surfaces, and platform evolution—where 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.
Designed a cost modeling framework to estimate and track the cost of individual simulations in a cloud-based architecture. Introduced a credit-based pricing concept and structured cost attribution using AWS metrics, enabling future commercialization and scalable pricing strategies.
Design artifacts and collaboration alongside code—patent-adjacent architecture, funding narratives, and partner-facing roadmaps (often confidential).
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, product leadership, and IP/partner alignment.
Technologies and tools I use regularly in production work.
Recent coding activity (WakaTime).
Beyond implementation: connecting engineering with product strategy, commercialization, and decision-ready technical design—including cost modeling and platform economics where the product meets the 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 energy software, simulation workflows, GIS-enabled analysis, and AWS architecture through work on MESO at Angler Solutions — plus software and system design for IP, funding collaboration, and AWS and local partner ecosystems.
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 software engineering roles, 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).