Solution Architect
Location: St. Louis, MO
Duration: 12 Months
Job Description:
- Determination of which products impacted
- Just Barely Good Enough design for handoff to responsible teams (incl. technical design document for anything that hits multiple teams)
- Handoff / discussion to socialize the design with the responsible teams
As outputs:
4. Reasonable confidence that downstream capabilities exist and will support the design (technical AND UX);
a. or call outs for those that don't and reasonable confidence that they *could* be built
5. Proposed design (technical AND UX) can be built in a supportable, maintainable, scalable, *able(more of these?)
As engagement:
6. Researches current downstream capabilities, makes suggestions/offers alternatives that may meet the spirit of the "requirements" (the problem statement) that do align to downstream capabilities
7. Engages in the design process, offers potential solutions/influences the UX design in order to assure supportable/maintainable/scalable software
Shared Responsibilities:
• Minimize unicorn solutions, encourage re-use, require justification for inventing new patterns, strategies, duplicating functionality and/or concepts/patterns
• Considers the problem presented and collaborates to propose the best solution balancing technical soundness and usability. Aware of best practices of designing RESTful APIs. Not looking for developers, instead looking for established solution architects. Those that can document flows (like dita mapping, data flows etc.) and have the communication prowess to explain to breadth of audiences (developer to executives).
Technical tools in use:
Postman - to look at API's
Confluence Chalk - documentation
Lucid Suite (similar.to VISIO / Girby)- Charts for process flow
JIRA expertise - Coordinate with Stories/requirements; logging dependencies; Working with Program managers
to move things along.