BUSINESS SYSTEMS DEVELOPER — PYTHON & SQL
Job Description & Role Charter
Position Title: Business Systems Developer — Python & SQL
Department / Function: Business Systems & Process Automation
Reports To: Business Owner
Direct Reports: None
Location: Noida
Job Description
About the Organisation
We are a distribution business in hoses and allied industrial products, and a manufacturer of hose assemblies. Supply Chain is our largest function, spanning warehouse, production and procurement operations, supported by HR and Accounts. We operate from Delhi and Noida with a clear vision to expand across India.
SAP Business One is our core ERP. Alongside it we have built a modern internal application platform — a dedicated SQL Server operational database, a secure REST API layer, and Python applications hosted on cloud infrastructure. This platform is how we intend to run the business: structured, measurable processes replacing spreadsheets and informal coordination.
Because we are growing and because operations are continuously refined, process creation and improvisation is a permanent function here, not a one-time project.
Role Purpose
To build, own and continuously improve the internal applications through which the organisation runs its operations. The Business Systems Developer converts business process requirements into working applications — designing the supporting data structures, building the Python application, testing it against real operational data, and then owning it through its life in production use.
The role is deliberately both build and maintenance. Every application built by this role remains that person's responsibility: defects, refinements and improvements arising from day-to-day use are handled by whoever built it. Ownership does not end at go-live.
The role is also expected to be present at the operational level. Understanding how a process actually behaves at the user's desk — where it slows down, where people work around it, where it produces bad data — is part of the job, not an optional extra. Over time this role is the natural feeder into a Business Systems Architect position.
Key Responsibilities
Own assigned business processes end to end — from data structure design through to a tested, documented, working application ready for rollout across the organisation.
Design and create tables in the development database to support each process, applying sound structure, keys and indexing.
Build Python web applications that read and write through the internal REST API, following the established application framework and build patterns.
Build interfaces that non-technical staff across warehouse, production, procurement, sales, HR and accounts can operate without training.
Build both ERP-linked and standalone processes. Some processes originate from SAP transactions — a complaint raised against a sales invoice, a delivery requiring warehouse confirmation. Others are entirely independent of SAP — vehicle in and out logging, courier inward and outward tracking, and similar operational records — which draw on employee master data from SQL but carry no SAP transactional dependency.
Test every application thoroughly against real operational data before it is put forward for rollout. Applications that pass on clean test data and fail on real business data are the single most common cause of rework, and testing is the builder's responsibility, not the user's.
Maintain and improve every application owned — resolving defects, absorbing change requests, and proposing refinements as operational understanding deepens.
Engage directly with end users and department heads. Understand the day-to-day intricacies of how a process runs, identify bottlenecks, and propose solutions rather than waiting for specifications.
Document every process built to the agreed standard — data structures, logic, dependencies and design decisions. Documentation is a delivery requirement, not an afterthought; a process is not complete until it is documented.
Raise data requirements to management through development meetings — any SAP data needed for visibility in the development environment, and any data required to be inserted into or updated within custom tables from the SAP database.
Decision Authority
Decides independently: Table structure and data model within the development database for assigned processes; application architecture within the established framework; UI design and user flow; technical approach to implementation; timing and method of testing.
Proposes, with management deciding: Process design changes and improvements identified through user interaction; changes to the shared application framework or standard patterns; new processes worth building.
Raises to management in development meetings: Any SAP data required for visibility in the development environment; any data insertion or update required into custom tables from the SAP database; requirements that cannot be met within existing access.
Escalates to management: Conflicting requirements between departments; process logic questions where the correct business answer is unclear; anything requiring changes to the live SAP environment.
Decision scope widens with demonstrated judgment. Developers who consistently propose sound process improvements will progressively be given process design ownership.
Required Experience
• 1 to 3 years building applications in Python, with production applications actually used by people.
• Hands-on experience with a Python web framework — FastAPI, Flask or Django.
• Working SQL — designing tables, writing SELECT and JOIN queries, understanding keys, relationships and basic indexing. Microsoft SQL Server experience is an advantage.
• Experience consuming REST APIs in application code.
• Ability to build functional web interfaces — HTML, CSS and sufficient JavaScript to make a page work well.
• Comfort with Git and standard version control practice.
• Graduate in Computer Science, IT or equivalent practical capability.
Sign in
To continue your applicationor continue with email
By continuing you agree to our Terms & Privacy Policy.
