Technical Functional Analyst (SDK & API) :
Knowledge of the infrastructure: Auth0 Apigee Splunk etc. Sometimes all you need is just expose another API but it usually comes with a bunch of prep work: evaluate the functionality check subscriptions ensure proper access troubleshoot possible issues etc. Having Java background is preferable.
Being proactive and cooperative with the teams mentioned above.
Research core functionality and identify exact improvement points. That would help to come to the core teams with exact proposal vs just asking them to fulfil a certain use case they know nothing about
Be ready to build reasonable design solutions that can be implemented in timely fashion
Try to keep the backlog up to date.
Being ready to learn new services new applications and new patterns quickly including discovery and playing around. Sometimes new solutions can only be verified by manual exploration and communicating with the engineering teams.
Keep track of everything that makes sense not just everything. And track only the request the use case not the solution suggestions or implementation. Yet always keep in mind if the request can be fulfilled given the current functionality and architecture.
Technical Functional Analyst (SDK & API) :Knowledge of the infrastructure: Auth0 Apigee Splunk etc. Sometimes all you need is just expose another API but it usually comes with a bunch of prep work: evaluate the functionality check subscriptions ensure proper access troubleshoot possible issues etc. ...
Technical Functional Analyst (SDK & API) :
Knowledge of the infrastructure: Auth0 Apigee Splunk etc. Sometimes all you need is just expose another API but it usually comes with a bunch of prep work: evaluate the functionality check subscriptions ensure proper access troubleshoot possible issues etc. Having Java background is preferable.
Being proactive and cooperative with the teams mentioned above.
Research core functionality and identify exact improvement points. That would help to come to the core teams with exact proposal vs just asking them to fulfil a certain use case they know nothing about
Be ready to build reasonable design solutions that can be implemented in timely fashion
Try to keep the backlog up to date.
Being ready to learn new services new applications and new patterns quickly including discovery and playing around. Sometimes new solutions can only be verified by manual exploration and communicating with the engineering teams.
Keep track of everything that makes sense not just everything. And track only the request the use case not the solution suggestions or implementation. Yet always keep in mind if the request can be fulfilled given the current functionality and architecture.
View more
View less