Job search
SAP Basis Jobs: Distinguish Platform Operations from ABAP Application Development
Compare SAP platform operations, HANA administration and ABAP development through two US employer descriptions and two completed evidence and ownership maps.
Identify an SAP Basis job by its responsibility for the SAP platform's operation: system health, maintenance, changes, recovery and the technical landscape. ABAP application development concerns application behavior and code. Functional work concerns the business process and configuration. The roles collaborate; your evidence should identify which responsibility you actually held.
LandOffer publishes this guide. Use recent roles on LandOffer.ai to choose a target, then check the employer's complete description. The complete public descriptions from two US employers and the official SAP learning pages were checked on October 23, 2026. The jobs are responsibility snapshots, not a continuously verified vacancy list. Both completed worked assets below are fictional documents; no SAP system, HANA database, account, license or environment was accessed or changed.

Start with the system the engineer operates
SAP's System Administration overview describes ongoing reliability, performance, management and support of SAP application environments. It includes system management, problem response and capacity planning. For each posting, ask what environment you would keep operating and which decisions you would own.
A Basis description may name installations, upgrades, system refreshes, monitoring, transports, backup and recovery, or coordination with infrastructure and security teams. Read the verbs and the system context together. Supporting a maintenance task differs from planning the change, executing it, reviewing the result or authorizing service restoration.
Also identify the landscape: development, test and production environments; operating systems; databases; SAP products and releases; and any managed-service arrangement. A title does not establish who administers every layer. An organization may divide platform, database, infrastructure and application duties among several teams, or combine some of them.
Two current Basis descriptions show different scope
SAP NS2's SAP Basis Automation AI Engineer in Herndon emphasizes automating Basis operations with Linux shell scripting, Ansible and Python. Its required qualifications include a relevant bachelor's degree and eight or more years of SAP Basis administration and operations. HANA administration and installation, upgrade, migration and maintenance experience appear among preferred qualifications. The page requires US citizenship because of customer-data access. The AI wording does not turn this senior platform-automation job into an ABAP application-development position.
Apiphani's SAP Basis Engineer — Second Shift combines client production support with migrations, refreshes, database backup and recovery, high availability and maintenance. It asks for three or more years in Basis work in a 24/7 setting, HANA administration and a relevant degree or equivalent experience. Its remote role explicitly requires US citizenship, US residence and availability from 2:00pm to 11:00pm Pacific Time, with a West Coast preference. Remote therefore does not establish flexible hours or worldwide eligibility.
Compare level as well as technology so you can distinguish following a procedure from owning its design and operation. The examples range from defined support activities to substantial automation ownership. A candidate who has followed a runbook should explain that contribution accurately, while checking whether a target expects independent architecture or framework development. Neither a scripting language nor a system-administrator title supplies that answer alone.
Separate platform automation from application code
A Basis engineer can write substantial software. A script that gathers approved system-health information or coordinates a maintenance workflow is still engineering work, with correctness, error handling and review requirements. Its users and operating consequences differ from those of an application feature.
SAP's ABAP Cloud lesson describes developing applications, services and extensions, including transactional and analytical scenarios and integration. That is application-development context, not a universal description of every SAP landscape. Ask which ABAP model, system edition and development practices a particular team uses.
Functional configuration is another responsibility. A business-process owner or consultant may define expected purchasing, finance or other module behavior. An application developer may implement an approved extension. A Basis team may support the environment and controlled movement of changes. One project can require all three without giving any one person authority to approve every aspect.
When a posting says “configuration,” identify the object. Operating-system settings, database settings, application-runtime configuration and business customizing are different work. Do not attach a platform-administration claim to a business-rule change simply because both happened inside an SAP project.
HANA experience needs a specific boundary
SAP's HANA Installation and Administration course covers database installation, updates, configuration, administration, monitoring, backup and recovery. It lists Linux administration as basic knowledge. That supports the database-and-operating-system context behind some Basis requirements; completing or reading a course does not establish production ownership.
Using SQL against a database is different from administering it. Supporting an application that depends on HANA is different from executing a database migration. Preparing an operating-system change is different from confirming application behavior afterward. For each experience claim, identify the layer, environment, personal task and evidence available.
A posting mentioning an OS or HANA migration also leaves practical questions. Who owns compatibility assessment, data protection, the maintenance window and the decision to proceed? Which team checks application interfaces and business behavior? Record each owner and unresolved handoff before deciding whether your migration experience matches the advertised responsibility.
Completed asset: two delivery records from one project
Consider a fictional manufacturer, Cedar Works, preparing an upgrade rehearsal in an approved nonproduction environment. Two invented staff members contribute. Ava is an ABAP developer; Ben supports Basis operations. The records below are completed document exercises, not logs from a real rehearsal. No code, transport, upgrade or recovery was executed for this article.
| Record field | Ava's application-development record | Ben's platform-operations record |
|---|---|---|
| Intended contribution | Review an existing custom report against the agreed application behavior | Prepare the rehearsal's environment and operational evidence requirements |
| Evidence prepared | Technical change note and three expected report outcomes | Environment inventory, maintenance checklist and recovery-evidence request |
| Review boundary | Functional owner confirms the expected business behavior | Platform and database owners review the proposed operating steps |
| Current result | Expected outcomes documented; no application test executed | Rehearsal readiness questions documented; no upgrade or restore performed |
| Remaining decision | Authorized team must implement and test any approved change | Designated change authority must approve the rehearsal and its conditions |
Ava's completed expected outcomes are specific: an authorized test user can request the fictional report; a missing required date produces an understandable validation response; and an empty result is distinguishable from a failed request. These are invented acceptance requirements, not claims about a standard SAP report or observed system behavior.
Ben's completed readiness note identifies three unresolved items: the approved starting state, the owner of recovery evidence and the team that will confirm application availability after the rehearsal. His handoff requests those records before scheduling is finalized. It does not claim that a backup exists, that recovery succeeded or that a maintenance window is approved.
The resulting portfolio statements stay separate. Ava records, “Prepared a fictional custom-report review brief and expected application outcomes.” Ben records, “Prepared a fictional upgrade-rehearsal readiness packet with environment, recovery-evidence and approval questions.” Neither uses “delivered a successful production upgrade.” The project label is shared; the contribution and limits differ.
Completed asset: a HANA migration responsibility map
A second fictional project proposes moving an SAP application landscape to a new HANA/OS environment. Its purpose here is to identify evidence owners, not prescribe a migration method. The target versions, tools, licenses, capacity, permissions and compatibility have not been established. No real migration plan should be inferred from the table.
Project analyst Lena completes this ownership map before the invented planning review:
| Decision or evidence | Owner assigned in this fictional project | Completed status and next handoff |
|---|---|---|
| Supported target landscape and compatibility | Technical architect with platform, database and infrastructure owners | Evidence not supplied; request the documented target assessment |
| Database protection and recovery readiness | Database owner | Recovery-evidence requirement recorded; no successful restore claimed |
| OS resources and technical dependencies | Infrastructure owner with Basis input | Dependency list requested; no host or account changes authorized |
| SAP platform readiness and monitoring | Basis owner | Required health and operational records identified; execution pending approval |
| Custom code and interfaces | Application-development owner | Regression scope requested; no code compatibility result established |
| Business process acceptance | Functional and business owners | Acceptance examples must be agreed before executed results are interpreted |
| Proceed, stop or restore decision | Designated change authority informed by the owners above | Hold the planning gate until the missing evidence and responsibilities are resolved |
Lena's finished meeting note states: “The map is complete as a responsibility document. Technical readiness is not established. Each owner must return the requested evidence, and the designated authority retains the proceed decision.” That resolves who needs to answer the questions without inventing the answers.
The distinction helps a candidate explain collaboration. A Basis engineer might coordinate several records while another person owns database recovery or business acceptance. Conversely, a broad role might own more than one layer. Use the actual project record rather than assuming that every Basis administrator performed every migration task.

Audit the experience you would put on the resume
For each proposed bullet, mark whether you authored a plan, performed a task, supported another owner, checked a result or approved a decision. Then name whether the work concerned development, test or production and identify the SAP product context. A nonproduction rehearsal can supply useful evidence when described accurately. It does not become production experience because the procedure resembles one used later.
For an operational example, explain the original symptom or maintenance objective, the authorized scope, your contribution and the evidence of the outcome. If you only prepared documentation, say so. If you executed a task under supervision, explain the supervision and escalation boundary. Avoid adding an availability percentage, recovery time or incident-prevention claim without a supporting record.
For a development example, explain the requirement, application change and test evidence. Debugging an ABAP program may help diagnose a platform issue, but it does not by itself establish landscape administration. Likewise, transporting a change does not establish authorship of the application code inside it.
Check coverage hours and automation responsibility
Read support coverage separately from remote location. Apiphani gives explicit shift hours; another posting may need clarification about on-call work, maintenance periods or handovers. Ask who receives escalations and how responsibilities move between coverage teams. Do not infer a schedule from “24/7 environment” alone.
For an automation-heavy role, ask who reviews scripts, approves privileged actions and handles failed or incomplete execution. Distinguish a tool-generated suggestion from reviewed automation and an executed result. SAP NS2's description combines AI-assisted work with deep Basis and scripting experience; familiarity with an AI assistant does not replace those requirements.
Keep private infrastructure details, credentials, customer diagrams and license information out of public samples. A sanitized or explicitly fictional document can demonstrate planning and ownership reasoning. It should not imply permission to operate a system or claim that the author performed an unexecuted task.
Choose by the responsibility you can substantiate
Before applying, select one example and record its platform or application scope, environment, personal contribution, evidence and remaining limitation. Compare it with the target's actual level and duties. Identify a missing capability precisely: HANA administration, supervised transport work, Bash automation or application testing are different gaps.
Browse recent roles on LandOffer.ai, then return to the employer's full description and decide whether to apply, clarify a material requirement or target a closer match. The useful distinction is the work you can explain and the responsibility you are ready to hold.
Sources and Further Reading
- SAP NS2: SAP Basis Automation AI Engineer: senior Basis automation, qualifications and access condition.
- Apiphani: SAP Basis Engineer — Second Shift: production support, HANA and explicit shift/residency conditions.
- SAP Learning: System Administration: platform operations overview.
- SAP Learning: HANA Installation and Administration: database administration learning scope.
- SAP Learning: Exploring ABAP Cloud: application and extension development context.


