If you don't fit into every single one of the descriptors mentioned above, it will be very difficult to appreciate working at CoLinx.
Remote developers are encouraged to work 45 hours a week instead of 40 in order to make management trust you. This does not constitute overtime pay, however. In my short time at CoLinx, I saw several employees who had worked there for most of their adult lives resign, one of them openly citing lack of free time to be with his family (despite working from home). Because of these shakeups, there is a lack of leadership, which results in a buildup of pressure on anyone in newer/junior roles as work falls into their laps. No tools are being provided to manage or cope with this disorganization, and because the rest of the team is so tight-knit, any concerns or objections raised are argued with or explained away. Even old, outdated code written by previous employees cannot be questioned by someone who isn't "in" enough with the CoLinx social club until the code actively breaks.
Though the developers are officially remote, monthly meetings are held in Greenville, and inability or refusal to attend those meetings is openly frowned-upon. There has also been a refusal to lean into remote work, despite the claims from management that the company must be fully remote since they downsized to an office with less cubicles than they have employees. There are constant comments like, "back when we were all working in the office, we could have just sat together and done pair programming"... but a lack of curiosity when it comes to examining remote pair-programming tools. This same excuse is raised when discussing many facets of teamwork at CoLinx, not just pair programming. The solution is always for the employee who is struggling to drive to the Greenville office and work from there.
Management will assure you that the programming team operates on a flex schedule, but if you fail to earn enough goodwill (presumably by staying at CoLinx for years, working 45+ hour weeks, and attending in-person extracurriculars in Greenville like bowling and disc golf) your presence on Slack will be scrutinized by management (though not necessarily by the rest of your team). New or junior ("Programmar/Analyst I") developers are told that they should make sure that their flex schedule includes the hours between 9AM and 4PM so that they can best communicate with their team. If ever you step away from your computer for any reason, you are expected to update your Slack status and even notify all of the other developers in the company in a communal channel as to your whereabouts. I even saw home wifi/power outages for juniors met with "can't you go sit in a McDonald's parking lot and use their free wifi to get work done?" by management - on a Friday afternoon.