Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
I keep Sysadmins to 3 until I need more. Developer, lead developers, designers when needed for a new feature or my stock of modules and components are low that it affects the whole production line.
I didn't know I needed more sysadmins to staff ratio.
I have teams of 3 of each class (Teams are 3 designers, 3 developers 3 lead devs, 3 sysadmins, 3 researchers etc...) each team has a manager and each HP Manager has 3 managers under them. (My CEO is in a team with my advertiser at the moment.)
I haven't gone beyond the 3rd HQ building and 1st server building yet. All my staff are intermediate level.
I thought we just needed the teams for production of modules and they seem to be on top of all that at the moment.
Developer: 4
Designer: 4
Lead Developer: 4
Sales: 3
Research: 2
Marketing: 1
SysAdmin: 1
Most of these roles are beginner level for cost purposes.
I'm still in the early game (I guess), but I don't see the Sysadmin as being a super critical role in my company yet. That'll probably change once I get around to trying to add credit card purchases to the shopping website.