Axway API Gateway Module Lead
.png)
Role overview
This position sits in Sopra Steria's Axway API Management practice in Pune. The module lead builds and runs APIs on the Axway Amplify API Gateway and in API Manager: proxies, policies, virtual APIs, security controls and the filters, circuits and policy chains behind them. The scope runs across the whole API lifecycle and includes onboarding internal, external and partner consumers.
The work is delivered in a consulting setup. Expect to pair with architects and developers on backend integration, coordinate with onshore and offshore colleagues and client stakeholders under Agile/Scrum, take L2/L3 production incidents, and guide junior consultants on the team.
What you will do
- Build, set up and roll out virtual APIs, proxies and policies on the Axway Amplify API Gateway and in API Manager.
- Run API lifecycle processes end to end, from design and publishing through versioning, deprecation and eventual retirement.
- Put security controls in place, covering OAuth2, JWT, API key handling, rate limits and protection against threats.
- Set up and debug the policy chains, circuits and filters that run on the gateway.
- Partner with developers and architects to connect APIs to backend systems over REST, SOAP, JMS and MQ.
- Help internal and external API consumers get onboarded, partner integrations included.
- Track how APIs perform, investigate root causes and fix production incidents as part of L2/L3 support.
- Take part in code reviews and release management, and move changes through the DEV, SIT, UAT and PROD environments.
- Write technical documentation, runbooks and API specifications in OpenAPI/Swagger.
- Deliver under Agile/Scrum, staying aligned with onshore and offshore teams as well as client stakeholders.
What the employer is looking for
- Roughly 3 to 5 years in IT overall, at least 3 of them spent on Axway's API Management suite, meaning API Portal, API Manager and API Gateway. The posting separately states an expected total of 4 to 6 years.
- Solid grasp of the standards used to secure APIs, including mTLS, SAML, OpenID Connect and OAuth 2.0.
- Practical work with web service and data formats (REST, SOAP, JSON, XML, XSLT), plus JMS and MQ messaging.
- Comfortable with CI/CD pipelines and automated deployments built on Jenkins, Git and Maven or Gradle.
- Day-to-day familiarity with Linux/Unix environments.
- Awareness of how API governance, versioning approaches and API monetization work.
- Sharp analysis and troubleshooting ability, plus readiness to deal with client teams directly.
- Clear spoken and written communication suited to consulting work in front of clients.
- Able to handle a quick-moving consulting setting with firm deadlines, collaborate well in a team and mentor junior consultants.
- BE or BTech degree.
Good to have
- Scripting in Shell, Groovy or Python.
- Some experience of public cloud (AWS, Azure or GCP).
- Container know-how with Docker or Kubernetes.
- Familiarity with IBM DataPower, MuleSoft or another API gateway product.
About Sopra Steria
Sopra Steria is a European technology group known for its consulting work, digital services and solutions. The Group employs 51,000 people across close to 30 countries and reported revenue of €5.6 billion for 2025. It supports large companies and organizations through digital transformation, pairing sector knowledge and technology with a collaborative way of working, and describes itself as putting people at the center of what it does.
Quick answers
Is the Axway API Gateway Module Lead role at Sopra Steria remote?
No. The posting lists Pune, Maharashtra, India and is flagged as neither remote nor hybrid, so it should be treated as an on-site, full-time position.
How much experience does this role require?
The skills section asks for about 3 to 5 years in IT with at least 3 years on Axway's API Management products (API Portal, API Manager and API Gateway), while the posting also gives an expected total of 4 to 6 years. A BE or BTech degree is listed as the qualification.
Which platforms and tools does the role use?
The core stack is Axway's API Manager and Amplify API Gateway, with API Portal named in the requirements. Around it sit OAuth2, JWT, OpenAPI/Swagger, REST, SOAP, JMS, MQ, Jenkins, Git and Maven or Gradle. IBM DataPower, MuleSoft, cloud platforms, Docker and Kubernetes are listed as good to have.

DigitalAPI's read on this role
Why an Axway gateway lead role still matters in a multi-gateway market
DigitalAPI's leadership team has run API programmes for Fortune 100 companies and now builds the platform behind them. Here is their take on what this opening really asks for.
What this role says about the market
This posting is a reminder that enterprise API estates are rarely built on one product. The core of the job is deep Axway work, yet the same posting asks for awareness of governance, versioning strategy and monetization, and counts familiarity with further gateways such as IBM DataPower and MuleSoft as a plus. In our view that mix reflects how service providers staff API programmes today: clients need someone who can keep an established gateway healthy in production while understanding how it fits alongside other gateways, partner onboarding and commercial API models.
What to emphasise in your application
- Specific Axway work you have delivered: proxies, virtual APIs, and the filters, circuits and policy chains you configured or debugged.
- Security implementations you have owned, such as OAuth2 and JWT flows, API key handling, rate limiting and mTLS.
- Lifecycle discipline: how you handled versioning, deprecation and retirement, and how releases moved from DEV through to PROD via Jenkins and Git.
- Production support stories with a clear root cause and fix, since the role carries L2/L3 responsibility.
- Experience onboarding partner or external consumers and working directly with client teams, including any mentoring of junior colleagues.
For hiring managers
DigitalAPI's leadership team would advise screening for more than product familiarity. Ask candidates to walk through a policy chain they built and an incident they resolved, then probe how they would apply the same security and versioning rules if a second gateway sat next to Axway. Candidates who describe governance as something enforced in the pipeline, and who think about the consumer onboarding experience, tend to grow into the lead part of the title.
Our view is that single-gateway depth is most valuable when paired with a gateway-agnostic mindset: consistent governance, a clear catalogue for consumers, and APIs documented well enough for both developers and AI agents to use.
About DigitalAPI
DigitalAPI is the gateway-agnostic command centre for APIs and AI agents. It connects to the gateways an enterprise already runs, Apigee, Kong, AWS API Gateway and Azure API Management, and turns everything behind them into one governed, self-serve catalogue for developers, partners and AI agents. API Gateway, API Portal, API Catalog, API Marketplace, MCP Gateway and MCP Portal ship as one platform.
The company grew out of an API consultancy founded in Bangalore in 2015 that became an Apigee-Google partner in 2017, then built its own cloud-agnostic, AI-powered platform in 2020 after seeing how fragmented gateways and duplicate APIs blocked its clients. More than 240 API teams now use it, with customers such as Zurich, Canara Bank, HSBC, Fiserv and Mahindra Finance. DigitalAPI has offices in the USA, UK and India, 130+ people, and recognition from Gartner and Deloitte.









.avif)
