|
|
|
|
|
by toast0
1684 days ago
|
|
When I was at a startup, my job was take care of this one important service, but also be the person for all the server stuff that didn't have a person. Which meant I administered DNS, and email, and Google gSuite (or whatever it was called at the time or now), built out internal tool web login/SSO and migrated it to different identity systems, managed our domains, managed our certificates, advised client teams on security issues, did OS upgrades on servers, managed access to the servers, managed paying several of the vendors and was their single point of contact, patch (server side) OpenSSL so that client system libraries don't crash when OpenSSL and Microsoft disagree on vague specifications, managed a new grad building a TLS 1.3 library for our Android client, pretended to be a data scientist to analyze my service's data because we didn't have any of those (and when we did, most of them were worse at pretending than I was) etc. Someone from our client teams built server stuff occasionally when it was more convenient for one person to do the front and backend or server people didn't have time. The only people not wearing many hats in startup land are either only good at one thing or are very busy on one thing. |
|