PayNearMe
Senior API Engineer - Remote
PayNearMe, Santa Clara, California, United States,
Job Description
You’ll be the primary owner of our APIs, helping us optimize and extend them
For our existing APIs:Build out performance tests for the high-usage calls (we use K6)
Use the results to tune these calls to be as efficient as possible (reader nodes, caching, etc)
Tune the default behavior for new clients to return minimal results
Ensure that our logging and monitoring is sufficient to detect potential problems (we use Datadog)
Our APIs currently use an antiquated signature system, which requires much hand-holdingWe have taken the first step towards OAuth 2.0 for one client (using Kong)
We want to make OAuth 2.0 available to all clients, running incoming requests through Kong
All of our APIs should run through this path so that Kong can do as much auth and validation as possible
We use ReadMe to host our API documentation, with some well written documentationOwn the OpenAPI specification for our APIs
We need to point ReadMe at a separate and firewalled deployment and install an authentication system for clients to use
With the experience gained above, start working on the next generation of APIsHow do we redesign them to be simple, modular and fast?
How do we design for 10x and beyond using horizontal scaling?
You’ll be the primary owner of our APIs, helping us optimize and extend them
For our existing APIs:Build out performance tests for the high-usage calls (we use K6)
Use the results to tune these calls to be as efficient as possible (reader nodes, caching, etc)
Tune the default behavior for new clients to return minimal results
Ensure that our logging and monitoring is sufficient to detect potential problems (we use Datadog)
Our APIs currently use an antiquated signature system, which requires much hand-holdingWe have taken the first step towards OAuth 2.0 for one client (using Kong)
We want to make OAuth 2.0 available to all clients, running incoming requests through Kong
All of our APIs should run through this path so that Kong can do as much auth and validation as possible
We use ReadMe to host our API documentation, with some well written documentationOwn the OpenAPI specification for our APIs
We need to point ReadMe at a separate and firewalled deployment and install an authentication system for clients to use
With the experience gained above, start working on the next generation of APIsHow do we redesign them to be simple, modular and fast?
How do we design for 10x and beyond using horizontal scaling?