1

Senior Powerbuilder Developer Jobs in Georgia (NOW HIRING)

... PowerBuilder) to identify root cause -- without requiring senior escalation for your primary ... Build relationships with engineering counterparts so escalations that do reach that level move ...

... SQL, .NET, PowerBuilder) to identify root cause - without requiring senior escalation for your ... Build relationships with engineering counterparts so escalations that do reach that level move ...

... SQL, .NET, PowerBuilder) to identify root cause - without requiring senior escalation for your ... Build relationships with engineering counterparts so escalations that do reach that level move ...

Senior Powerbuilder Developer information

What are some common challenges faced by senior Powerbuilder developers when modernizing legacy applications?

Senior Powerbuilder Developers often encounter challenges such as integrating legacy Powerbuilder systems with modern technologies, ensuring code compatibility, and migrating databases without data loss. Adapting to new architectural patterns, such as transitioning from client-server to web-based or cloud solutions, can also be demanding. Effective communication with business stakeholders and other IT teams is crucial to ensure a smooth modernization process and to align technical solutions with business goals.

What are the key skills and qualifications needed to thrive as a senior Powerbuilder developer, and why are they important?

To thrive as a Senior Powerbuilder Developer, you need advanced proficiency in PowerBuilder programming, SQL, and database management, usually supported by a degree in computer science or a related field. Experience with PowerBuilder IDE, version control systems like Git, and familiarity with Oracle or SQL Server databases are typically required, along with any relevant certifications. Strong problem-solving abilities, attention to detail, and effective communication skills set candidates apart in this role. These competencies are crucial for delivering robust, maintainable software solutions and collaborating efficiently within development teams.

What is the difference between Senior Powerbuilder Developer vs Powerbuilder Developer?

AspectSenior Powerbuilder DeveloperPowerbuilder Developer
ExperienceTypically 5+ years, with leadership responsibilitiesUsually 1-3 years, focused on development tasks
CertificationsOften holds advanced certifications or specialized trainingMay have basic certifications or none
ResponsibilitiesDesign, lead projects, mentor juniors, optimize applicationsDevelop and maintain Powerbuilder applications
Work EnvironmentCorporate, financial, or enterprise sectorsVaries from small to large organizations in similar industries

The main difference between a Senior Powerbuilder Developer and a Powerbuilder Developer lies in experience, responsibilities, and leadership roles. Senior developers often lead projects and mentor others, while developers focus on coding and maintenance. Both roles are common in enterprise environments, but senior roles require more expertise and strategic input.

What is a senior Powerbuilder developer?

Senior Powerbuilder Developers are experienced software professionals who specialize in designing, developing, and maintaining applications using PowerBuilder, a rapid application development tool for building client-server and web applications. They typically handle complex projects, lead development teams, and ensure best practices in coding, testing, and deployment. Their expertise often includes database management, troubleshooting legacy systems, and integrating PowerBuilder applications with modern technologies. Senior developers also play a key role in mentoring junior staff and collaborating with stakeholders to deliver robust business solutions.
What are popular job titles related to Senior Powerbuilder Developer jobs in Georgia? For Senior Powerbuilder Developer jobs in Georgia, the most frequently searched job titles are:
What job categories do people searching Senior Powerbuilder Developer jobs in Georgia look for? The top searched job categories for Senior Powerbuilder Developer jobs in Georgia are:
What cities in Georgia are hiring for Senior Powerbuilder Developer jobs? Cities in Georgia with the most Senior Powerbuilder Developer job openings:
Infographic showing various Senior Powerbuilder Developer job openings in Georgia as of August 2026, with employment types broken down into 77% Full Time, 7% Part Time, 1% Temporary, and 15% Contract. Highlights an 80% Physical, 6% Hybrid, and 14% Remote job distribution.

Support Architect

PowerPlan, Inc

Atlanta, GA • On-site

Full-time

Re-posted 19 days ago


Job description

This role offers the chance to serve as a trusted technical expert at the center of PowerPlan's customer experience. As a Support Architect, you will be the escalation point for complex issues across PowerPlan's enterprise tax, accounting, and workflow platform — triaging and resolving problems that require deep application knowledge, code-level analysis, and strong customer communication.

You will work closely with customers, internal engineering teams, and junior support staff to diagnose root causes, drive resolution, and build the technical knowledge base that keeps PowerPlan's customer operations running at a high standard. This is a high-trust, high-accountability role for someone who thrives on difficult problems and takes personal ownership of customer outcomes.

COMPANY

PowerPlan develops enterprise-grade tax, accounting, reporting, and workflow automation solutions tailored specifically for energy industry organizations. We serve customers whose operational, financial, and regulatory processes depend on accuracy, reliability, and scalability. With a culture focused on teamwork, quality, continuous improvement, and modern engineering, we create technology that solves high-value industry problems while providing a supportive, collaborative environment where talented professionals can grow and lead.


KEY PERFORMANCE OBJECTIVES (First 12 Months)

OBJECTIVE 1: Achieve SME-Level Application Mastery (First 90 Days)

Outcome:

Within the first 90 days, develop deep working knowledge of at least two PowerPlan component modules and a high-level understanding of three or more. Be capable of independently triaging, diagnosing, and resolving complex application issues — including reviewing application code (SQL, .NET, PowerBuilder) to identify root cause — without requiring senior escalation for your primary modules.

Impact:

SME-level application mastery is the foundation of this role. Customers trust PowerPlan to resolve their issues quickly and accurately. A Support Architect who owns their domain reduces mean time to resolution, reduces repeat cases, and builds the kind of customer confidence that strengthens long-term relationships.

How:

Immerse in product documentation, architecture diagrams, and historical case data for assigned modules. Shadow senior architects on active cases. Work through real customer scenarios hands-on. Build a personal knowledge repository of common issue patterns, root causes, and resolution playbooks for your primary modules.

OBJECTIVE 2: Deliver Consistently High-Quality Customer Experience (Ongoing)

Outcome:

Manage your personal case queue in accordance with product support standards — accurate documentation, appropriate time management, and consistent communication throughout the life of every issue. Customers should always know where their case stands and feel that PowerPlan is actively working on their behalf. Handle escalations with confidence and minimal assistance from senior staff.

Impact:

Customer satisfaction in enterprise support is built case by case. Clear, proactive communication during a difficult issue often matters as much as the resolution itself. A Support Architect who sets expectations well and follows through consistently becomes a trusted advisor — and trusted advisors retain customers.

How:

Establish a personal cadence for case updates and customer touchpoints. Use structured communication templates for escalation notifications and resolution summaries. Anticipate customer questions before they ask them. Debrief on cases where communication broke down and apply lessons to the next one.

OBJECTIVE 3: Serve as Technical Escalation Point for the Support Team (3–6 Months)

Outcome:

Within the first 6 months, be the reliable escalation resource for junior support staff on complex technical issues within your module expertise. Actively mentor and educate team members — sharing diagnostic approaches, code review techniques, and resolution patterns. Reduce the volume of issues that require escalation to engineering by building team capability.

Impact:

An effective escalation point multiplies the team's capacity to resolve difficult cases. When junior staff have a skilled, accessible resource to learn from, their own resolution rates improve — reducing customer wait times, lowering engineering escalation volume, and strengthening the overall support organization.

How:

Conduct structured knowledge-sharing sessions for your team on your primary modules. Document resolution patterns in shared knowledge bases. Review complex cases with junior staff as a coaching opportunity, not just a handoff. Build relationships with engineering counterparts so escalations that do reach that level move quickly.

OBJECTIVE 4: Develop & Maintain Technical Depth in PowerPlan Tools (Ongoing)

Outcome:

Continuously deepen expertise in PowerPlan's primary development and diagnostic tools — SQL, .NET, PowerBuilder, and PLSQL — and secondary tools as needed (C, ABAP, etc.). Stay current with platform changes as new versions ship and proactively identify how those changes affect support patterns for your modules.

 

Impact:

Technical depth is a direct multiplier on resolution quality and speed. A Support Architect who can read, trace, and debug application code resolves issues that a non-technical analyst cannot — and does it faster, with higher first-contact resolution rates.

How:

Dedicate structured time each quarter to skill development in primary tools. Engage with engineering on code-level issues as a learning opportunity. Participate in product release reviews and internal training to stay ahead of platform changes. Seek out the most technically complex cases as growth opportunities.

OBJECTIVE 5: Lead or Contribute to Operational Improvement Initiatives (6–12 Months)

Outcome:

Identify and lead or contribute to at least one cross-functional initiative that improves team or customer experience within the first year. This could be a process improvement, a new knowledge base contribution, a tool or workflow enhancement, or a training program for the support team. Demonstrate the ability to work across functions and influence outcomes beyond your individual case queue.

Impact:

Support organizations that continuously improve their processes and knowledge assets scale more effectively than those that rely solely on individual heroics. A Support Architect who contributes to systemic improvement creates value that compounds across every case the team handles.

How:

Track recurring issue patterns and identify root causes that could be addressed through documentation, product fixes, or customer education. Bring proposals to the Support Manager with a clear problem statement, proposed solution, and expected impact. Follow through from proposal to implementation.


  • Application Support Expertise — Experience providing SME-level technical support for complex enterprise software applications, including code-level analysis and root cause diagnosis.
  • SQL & Development Tools — Strong hands-on SQL skills (complex query writing, schema analysis, performance diagnostics). Familiarity with .NET, PowerBuilder, or PLSQL is a strong plus.
  • Financial Domain Knowledge — Understanding of financial accounting processes — General Ledger, Accounts Payable, Fixed Assets, Project Accounting, or similar — ideally in an enterprise application context.
  • Customer Communication — Excellent written and verbal communication skills with the ability to explain complex technical issues clearly to non-technical customers and stakeholders.
  • Critical Thinking & Problem Solving — Demonstrated ability to analyze complex processes methodically, isolate root cause in ambiguous situations, and drive resolution with minimal guidance.
  • Enterprise Systems Experience — Familiarity with enterprise applications such as ERP, EAM, or CRM (SAP, Oracle, Maximo, PeopleSoft) and/or experience in utilities, energy, oil and gas, or related regulated industries.
  • Team Leadership & Mentorship — Ability to lead and influence peers, mentor junior team members, and contribute to cross-functional initiatives that improve team performance.
  • Education — Bachelor's degree in Computer Science, Information Technology, Engineering, or a related field (Tax, Accounting). Must be authorized to work in the US.

PREFERRED EXPERIENCE

  • Hands-on experience with capital projects, capital budgets, fixed asset accounting, or business tax software
  • Industry experience within utilities, energy markets, oil and gas, mining, transportation, natural resources, or telecom
  • Experience using PowerPlan products directly
  • Experience with Salesforce or a similar support ticketing system
  • Availability for alternate shift schedules and participation in 24x7 on-call rotation as needed

PowerPlan is an EOE

Applicant Privacy Notice

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.