|
I had a talk today with a lead developer about a possible next career step. Currently I'm a backend software developer at a company that makes B2B software that runs in the cloud. While we do have a frontend, a large chunk of our development time is spent on API and data related stuff: we receive data from several partners or customers, combine that, crunch that with (sometimes performance-intensive) algorithms, and send it back to the same or other parties. We basically support a large amount of collaboration among our partners and customers. He said the company is looking for someone who can head the design phase for new projects. That actually sounds quite interesting to me - but it's a topic I don't know much about. A quick google search shows that "software design" articles are often focused on frontend UX, which is certainly a part of it, but not the most important. What matters is finding out what makes up an MVP, what data fields are required, and how should they be modeled. What sort of data crunching will be required and is this feasible performance-wise? And perhaps architecture related questions such as which API connects to which, how does the data flow, what data needs to be stored long-term, etc. Of course I won't need to answer all these questions myself - but I'd be expected to organize meetings with customer-oriented people, product roadmap people, developers and make sure to ask the right questions at the right time. I'm not sure yet if this is something for me. So first, I would like to know more. But I'm not sure what this field is even called, as I said "software design" and "product design" google searches aren't really getting me anywhere useful. If anyone has any practical information or could point me to any posts, overviews, books, courses, whatever, I'd be grateful.
|
# ¿ Mar 25, 2022 11:31 |
|
|
# ¿ May 14, 2024 09:46 |