Software Engineer, ABAP Development

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

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

What Success Looks Like

1. Code Quality - Code you ship is clean, annotated, and passes review without significant rework. Vulnerabilities are caught before they reach QA.
2. Delivery - Features and fixes land on schedule. Estimates are reliable and you surface blockers early rather than late.
3. SDLC Contribution - Tests accompany your code. Transports are clean. You are a constructive voice in code review — both giving and receiving.
4. Support - Customer issues you own are diagnosed clearly and resolved with urgency proportionate to severity.
5. Growth - You are demonstrably more capable at the end of each year than at the beginning, and the team benefits from that.

What You Bring

Required

• Solid, demonstrable proficiency in ABAP — classical and modern language syntax and development principles
• Deep proficiency in ABAP Objects: interfaces, inheritance, class-based exceptions, and design patterns such as factory, builder, dispatcher, and task queue
• Strong ABAP Dictionary skills: transparent tables, views, data elements, domains, table types, lock objects, and search helps
• Hands-on experience with RFC and parallel processing: asynchronous RFC, task queues and dispatching, enqueue locking and synchronization, background jobs, and shared memory objects
• HTTP/REST integration from ABAP and serializing/parsing JSON and XML payloads at high volume
• Performance-minded development for high-volume data extraction: efficient Open SQL, internal table handling at scale, and runtime analysis
• Understanding of core computer engineering principles: data structures, algorithmic complexity, modularity, encapsulation, separation of concerns
• Experience working across the full SDLC: development, testing, transport management, and production support
• Familiarity with SAP security concepts relevant to ABAP development — authorization objects, input validation, injection prevention
• Ability to write code that others can read — not just code that runs
• Curiosity and the discipline to act on it: you find new techniques and actually apply them

Strong Preference

• Experience with modern ABAP practices: RAP, ABAP for Cloud, Clean ABAP guidelines, or ABAP Unit testing frameworks
• Familiarity with SAP observability, monitoring, or security tooling (SAP Solution Manager, SIEM integration, Splunk or Dynatrace connectors)
• Experience in a product company — software you built is running in production at customers you care about
• Exposure to DevOps or CI/CD practices in a SAP context
• Experience with AI-assisted development tooling and a genuine opinion on how to use it well
• Working knowledge of observability protocols and platforms: Splunk (HTTP Event Collector, REST API, metrics), Dynatrace, Elastic or OCI Logging
• Experience querying and monitoring SAP HANA via ADBC / native SQL
• Familiarity with SAP integration and replication technologies: SAP Gateway and OData (V2/V4), SLT/LTRC, IDoc/ALE, AIF

What You're Not Accountable For

To be explicit about boundaries:

• Product direction and roadmap prioritization — the what and why are a product and leadership conversation. Your job is to execute those decisions at a high standard and bring technical insight to the conversation, not make the final call.
• Architecture and security posture decisions that carry company-level risk — those surface to senior engineering leadership with your analysis and a recommendation. You own the implementation once direction is set.
• Commercial outcomes — sales and customer success own the number. You own the quality of the product that makes retention and growth possible.

The Standard

This is a mature product with demanding enterprise customers. The ABAP codebase reflects years of hard-won decisions, and every change to it carries consequence. The standard for this role is not 'functional code that ships.' It is code that improves the system — that is more readable, more secure, better tested, and more maintainable than what it replaced.

AI is a core part of how RHONDOS operates. That applies here: AI-assisted development, code review support, test generation, and documentation are all tools you are expected to reach for instinctively. We lean toward Claude and the Anthropic ecosystem, but the right tool for the right job is the principle. Using AI well is part of the job. Ignoring it is not.

You will be given clear direction, real problems, and the support to do good work. In return, we expect ownership, craftsmanship, and the intellectual honesty to say when something is wrong — in the code, in the plan, or in your own estimate.

Compensation & Benefits

Poland

• Base Salary: PLN 25,000 - 33,000 per month
• Employment contract (umowa o pracę)
• Annual Leave: 26 Days Paid
• Insurance: Private Medical Cover
• Work Location: Remote within Poland
• Bonus: Discretionary annual bonus, subject to plan terms
• Equity: Stock option grant, subject to plan eligibility

Germany (Berlin)

• Base Salary: €72,000 – €95,000 gross per year
• Employment contract: Permanent employment contract
• Annual Leave: 30 Days Paid
• Insurance: Statutory health, pension & care
• Work Location: Berlin or Remote within Germany
• Bonus: Discretionary annual bonus, subject to plan terms
• Equity: Stock option grant, subject to plan eligibility

Culture

We move fast. We go deep. We hold ourselves accountable to outcomes — not activity.

1. Positive Reciprocity - Mutual success with customers, partners, and each other
2. Win - With discipline, clarity, and velocity
3. Customer Obsession - We are relentless about customer success
4. Do the Right Thing - Even when it's harder