Roles And Responsibilities
- This is primarily a lead role, helping drive technical initiative forward with teams,
given broad guidance and support.
- Need to have solid foundations in API exposure space.
- API life-cycle management (API design best practices, discovery, inventory
management, governance)
- API Provider and Consumer journey
- REST fundamentals.
- API Security (AuthN, AuthZ, OpenID/OAuth 2.0/POP/PKCE etc) & OWASP
- OAS fundamentals too - API documentation, Error code's etc
- GraphQL is a plus.
- Must: Be able to write production quality code in Java / Open-Source
technologies. Python is good to have, exposure to building sdks is strongly
desired.
- Must: have good hands-on experience on Microservices architecture,
Kafka/Message Broker, and Event Driven Architecture.
- Must: have good hands-on experience on Database technologies (SQL & NoSQL)
and design expertise on database modeling etc
- Be able to take direction from tech leads and drive across teams (once teams are
aligned) with minimal guidance. This is key, to not require too much granular
guidance.
- Doesn't need to have telecom background, need to be able to pick up new
concepts quickly
- Hands on Exposure to API Gateways is a strong plus (not a must-to have
requirement) as is prior experience with API exposure to customers.
Skills: api lifecycle management,api gateways,openid,api,nosql,java,microservices architecture,event driven architecture,api security,rest,graphql,owasp,sql,oauth 2.0,core java,kafka,api documentation
