Code for Thought Designed to Work: Part 3 - solutions architects
Whereas the last episode focused on architecture at enterprise scale, this episode is looking at architecture for software solutions.
I was fortunate enough to meet with 3 solutions architects from Amazon Web Services in the US: Akash Gheewala, Ro Mullier and John Majarwitz.
As we discuss in this episode, the path to become an architect varies: whether it is moving into the role straight away or gradually after years in software engineering.
Architecture can be an attractive choice for engineers who want to develop their career but don't want to leave the technical field. However, as you move into the role of architect you will need to develop more than technical skills, be that business acumen or stakeholder management.
Research software engineering is a relatively young discipline. But it is rapidly expanding and I think there is an opportunity for us to learn from our colleagues in the private sector: whether it is for developing career paths or software solutions for complex engineering tasks.
Thank you for listening! Merci de votre écoute! Vielen Dank für´s Zuhören!
If you're like to support this show, you can leave a little tip at
https://en.tipeee.com/code-for-thought-podcast/
Contact Details/ Coordonnées / Kontakt:
- Email mailto:peter@code4thought.org
- UK RSE Slack (ukrse.slack.com): @code4thought or @piddie
- US RSE Slack (usrse.slack.com): @Peter Schmidt
- Mastodon: https://fosstodon.org/@code4thought or @code4thought@fosstodon.org
- Bluesky: https://bsky.app/profile/code4thought.bsky.social
- LinkedIn: https://www.linkedin.com/in/pweschmidt/ (personal Profile)
- LinkedIn: https://www.linkedin.com/company/codeforthought/ (Code for Thought Profile)
This podcast is licensed under the Creative Commons Licence: https://creativecommons.org/licenses/by-sa/4.0/