Been using UNIX since the late 80s; Linux since the mid-90s; virtualization since the early 2000s and spent the past few years working in the cloud space.
Location
Alexandria, VA, USA
Education
B.S. Psychology from Pennsylvania State University
Not to be flippant, but I'd say that there's really no such thing as "typical" roles and/or responsibilities. Roles and responsibilities are as individual as the organizations seeking services and the problems needing to be solved. Worse (ironically?), one of the biggest problems that frequently — possibly even usually — needs to be solved is understanding the actual problem to be solved. If the customer fully doesn't understand the problem (and what constitutes successfully solving it), there's pretty much no way they can engage a consultant/consultancy and reasonably expect success.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Not to be flippant, but I'd say that there's really no such thing as "typical" roles and/or responsibilities. Roles and responsibilities are as individual as the organizations seeking services and the problems needing to be solved. Worse (ironically?), one of the biggest problems that frequently — possibly even usually — needs to be solved is understanding the actual problem to be solved. If the customer fully doesn't understand the problem (and what constitutes successfully solving it), there's pretty much no way they can engage a consultant/consultancy and reasonably expect success.