As a Lead Software Developer, you will own the technical direction and hands-on implementation of a mission-critical enterprise application used by customers in complex, asset-intensive industries. You will lead the modernization of legacy components into cloud-native, scalable services while continuing to deliver new features that customers rely on every day.
This role combines architecture influence, hands-on coding, and mentoring, giving you the opportunity to shape patterns, standards, and practices that the broader engineering team will follow. You’ll collaborate closely with Product, Architecture, and Operations to deliver secure, high-performing solutions that can scale with customer growth and evolving business needs.
COMPANY
PowerPlan builds enterprise software for asset-intensive industries, including regulated utilities and similar complex domains, helping customers manage critical assets, financial processes, and operational decisions with confidence. We operate in a space where reliability, accuracy, and compliance matter deeply, and where strong engineering practices directly impact our customers’ ability to serve their end users.
Our culture values pragmatic engineering, modern tooling, continuous improvement, and the thoughtful use of AI-assisted development to accelerate delivery without compromising quality or security. Joining our team means working with experienced engineers and product leaders who care about building robust systems that stand the test of time.
Responsibilities:KEY PERFORMANCE OBJECTIVES (First 12 Months)
OBJECTIVE 1: Deliver a Modernized, Cloud-Ready Application Foundation (First 6–12 Months)
Outcome: Within the first year, lead the transformation of targeted application components to Azure-based services with measurable improvements in reliability, performance, and maintainability (e.g., reduced latency, lower error rates, and adherence to defined SLAs/SLOs). Demonstrate consistent delivery of modernization increments each sprint, such that meaningful portions of legacy functionality are safely transitioned without disrupting existing customers.
Impact: Improves product stability and resilience, supports customer growth, and positions the platform for faster feature delivery by reducing technical debt and simplifying the architecture. This foundation enables the organization to respond more quickly to business opportunities and regulatory changes.
How: Implement secure, scalable cloud-native services using modern .NET, APIs, and event-driven or microservice patterns where appropriate; apply incremental modernization strategies (e.g., strangler patterns and backward-compatible changes) to reduce risk; and reinforce architectural standards through design reviews, hands-on coding, and close collaboration with Architecture and Product. Work with the team to prioritize modernization work in each sprint so that cloud adoption and feature delivery advance together.
OBJECTIVE 2: Establish High-Quality Engineering & Responsible AI-Assisted Development Standards (First 6–12 Months)
Outcome: Within the first 6–12 months, define, implement, and drive adoption of consistent engineering standards covering code quality, automated testing, documentation, secure coding, observability, and maintainability—while integrating responsible AI-assisted development workflows (e.g., GitHub Copilot). Ensure all Scrum teams apply these standards in code reviews and daily development, with measurable improvements in code quality, test coverage, PR review depth, and time-to-delivery.
Impact: Reduces defects and rework, accelerates team productivity, and ensures AI-generated code meets required levels of security, maintainability, and correctness. Establishes a consistent engineering culture that supports predictable delivery and the safe, scalable evolution of the platform.
How: Lead the creation and rollout of engineering standards and AI-assisted development guardrails; introduce templates, checklists, and pipeline automation to enforce quality gates; coach teams on effective prompting and critical review of AI-generated code; and monitor adoption through metrics such as test coverage, build health, defect trends, and PR review quality. Partner with Architecture, Security, and Product to embed these standards into the SDLC, from design through deployment.
OBJECTIVE 3: Lead Hands-On Delivery While Strengthening Cross-Team Technical Alignment (Ongoing, First 12 Months)
Outcome: Deliver high-quality production code each sprint across both legacy modernization and new cloud-native features while ensuring architecture decisions, design patterns, and scope boundaries are clearly understood and consistently followed across Product, Architecture, and engineering teams. Improve predictability and reduce rework by aligning on technical decisions and patterns early, and by modeling best practices through your own contributions.
Impact: Accelerates roadmap execution, reduces delivery friction and misalignment, and prevents architectural drift by ensuring teams converge on well-defined patterns and approaches. Engineers gain clear examples to follow, which improves consistency and maintainability across the codebase.
How: Contribute hands-on to feature delivery in a Scrum team; participate in and lead design and architecture reviews; pair with developers to model clean, testable designs; and facilitate trade-off discussions (performance, cost, time-to-market, and maintainability) with Product and Architecture. Document and communicate key technical decisions and patterns so that teams can apply them independently and consistently.
OBJECTIVE 4: Raise Team Technical Capability While Enforcing High-Quality, Predictable Delivery (First 6–12 Months)
Outcome: Within 6–12 months, mentor and coach engineers to elevate skills in cloud development, modernization strategies, testing excellence, secure coding, and AI-assisted development, while simultaneously enforcing quality gates such as code review standards, automated test thresholds, security scanning, and incremental delivery practices. Demonstrate measurable improvements in code quality, team autonomy, onboarding speed, and reduction of escaped defects and production incidents tied to preventable issues.
Impact: Builds a stronger engineering team capable of delivering high-quality features with consistency and confidence, reducing support burden and increasing development velocity across the organization. Over time, this reduces dependence on a few senior engineers and creates a deeper bench of capable contributors.
How: Provide structured mentoring and pairing opportunities; run technical deep dives and design walkthroughs focused on real work in progress; strengthen automated checks and CI/CD gates; collaborate with Product and QA to define practical, testable acceptance criteria; and model engineering best practices through your own code, reviews, and decision-making. Use feedback loops (retrospectives, metrics, and 1:1s) to continuously refine coaching and standards.
OBJECTIVE 5: Strengthen Product & Architecture Collaboration While Championing Secure, Compliant Solutions (First 12 Months)
Outcome: Within the first 12 months, improve alignment between Product, Architecture, and engineering so that features are scoped with clear technical assumptions, reusable patterns, and security requirements defined up front—resulting in fewer late-cycle redesigns and smoother releases. At the same time, ensure all new and modernized services consistently meet baseline security standards (e.g., static and dependency scans, secrets management, and basic threat-modeling), with a measurable reduction in security-related defects and vulnerabilities over the year.
Impact: Increases roadmap predictability and delivery throughput while reducing security and compliance risk, ensuring the platform remains enterprise-grade and trusted by customers operating in complex, regulated environments. This protects the business from costly incidents and strengthens customer confidence in the product.
How: Lead cross-functional design sessions and architecture reviews that explicitly cover scope, technical feasibility, and security considerations; define and socialize secure coding guidelines and patterns for APIs, data access, and cloud services; integrate automated security checks into CI/CD pipelines; and partner with Security or Governance stakeholders where applicable. Coach engineers to incorporate security and compliance thinking into design, code review, and story refinement, and ensure key decisions are documented and repeatable.
Qualifications:WHAT YOU BRING
PowerPlan is an EOE
Please note that this is a hybrid role that involves a combination of onsite work from our corporate office as well as work from home. While we strive to accommodate flexible working arrangements when sensible, there will be times when onsite work is required. This could include scheduled office days, team meetings, client meetings, or special events.
Raytheon Missiles & Defense
RTX
GSMA
Dentsu World Services Brazil
Raytheon Technologies
PowerPlan, Inc.
PowerPlan, Inc.
PowerPlan, Inc.