Software Engineer, SAP ABAP Development at RHONDOS
Berlin, Berlin, Germany -
Full Time


Start Date

Immediate

Expiry Date

04 Jan, 27

Salary

4200000.0

Posted On

06 Oct, 26

Experience

18 year(s) or above

Remote Job

Yes

Telecommute

Yes

Sponsor Visa

No

Skills

Industry

Information Technology & Services

Description

About the job

The Opportunity


RHONDOS PowerConnect is the recognized leader in SAP security and observability — trusted by Fortune 500 enterprises to secure and monitor their most mission-critical systems. PowerConnect is a mature, widely deployed product with a substantial global customer base, and the ABAP at its core has to be world-class: clean, secure, maintainable, and continuously improving.


This role is for a capable, self-directed software engineer who takes ownership of the quality and evolution of production ABAP code. You are not a junior developer learning the basics, and you are not a senior architect setting direction. You are a skilled practitioner — someone who understands what makes software good, applies computer engineering fundamentals with discipline, and raises the standard of the codebase through every commit.


PowerConnect sits at the intersection of SAP, security, and observability. The work is technically deep, the customers are large and exacting, and the stakes are real. This role is for someone who finds that motivating.


Before You Apply


Review our public presence before reaching out. We want to hear from engineers who understand what we are building and can speak to why they are the right person to make it better.


LinkedIn


  • YouTube
  • rhondos.com

Requirements


What You'll Own


ABAP Development & Feature Delivery


You write ABAP code that works — correctly, efficiently, and at a standard the codebase can be proud of. Specifically, you are accountable for:


  • Delivering new features and enhancements as directed by the product organization, with clean, well-annotated, vulnerability-free code
  • Applying both functional and object-oriented programming principles with fluency — choosing the right approach for the problem, not the one you happen to be most comfortable with
  • Writing code that others can read, review, and build on — variable names that mean something, logic that is traceable, and comments that explain intent where the code alone cannot
  • Ensuring every piece of code you ship is free from security vulnerabilities — this is a non-negotiable on a product trusted by the world's largest organizations to protect their SAP environments

Software Development Lifecycle Ownership


Development does not end when the code compiles. You are expected to own your work through the full SDLC, including:


  • Writing and maintaining unit tests and contributing to integration testing coverage — quality is your responsibility, not QA's alone
  • Participating actively in code review — both receiving feedback and providing it for your peers
  • Contributing to transport management and release packaging, ensuring changes move through development, quality, and production environments cleanly and traceably
  • Supporting root cause analysis and resolution when defects surface in production — and contributing to the process improvements that prevent them from recurring

Product Support


PowerConnect has a large, active customer base. Support is not a distraction from engineering — it is part of the job:


  • Providing technical escalation support for complex customer issues that require ABAP-level diagnosis
  • Translating customer-reported problems into clear, reproducible defects and driving them to resolution with appropriate urgency
  • Building documentation and tooling that reduces the frequency and cost of escalations over time

Continuous Learning & Technical Growth


The SAP development landscape is evolving — ABAP for Cloud, RESTful Application Programming Model (RAP), ABAP Unit, clean core principles, and AI-assisted development are all changing what good ABAP looks like. You are expected to:


  • Actively stay current with modern ABAP practices and bring relevant improvements back to the team and the codebase
  • Contribute to internal knowledge sharing — write-ups, documentation, brief tech talks, or simply being the person on the team who knows the answer
  • Engage with the broader RHONDOS mission beyond your immediate codebase — understand the product, the customers, and the business context well enough to make better engineering decisions


Responsibilities
Loading...