2 ms·
The answer hinges on the expectations that the company has from you. If you and/or your work somehow slipped through the cracks and you know this but you're ke
by jstx1 5y ago
The answer hinges on the expectations that the company has from you.
If you and/or your work somehow slipped through the cracks and you know this but you're keeping quiet and staying low while there's actual work to be done - stop and find the most tactful way to start doing some actual work.
On the other hand, if the company is aware of how little work you're doing and they're happy to keep you on[1], in that case you can look for extra projects at work (they don't need to fill all of your time), spend time learning things you're interested in (related to work or not) and spend time with your kids completely guilt-free.
If you're early in your career, at some point it might make sense to leave and go somewhere where you'll learn more from actual work.
[1] Yes, this really happens. Maybe they expect future projects, or still building the team, or there are some org changes coming up, or they care about appearances and want to be able to say that they have a data scientist on a given team.
- jonahbenton 5y agoWould echo this. It is quite common in general for junior specialists in large orgs to have nothing to do for periods of time- weeks to months to quarters- in the hierarchy/project to which they are assigned. Best to find ways to understand the larger and smaller scale business context in which those specialist roles exist. Whether it is ok, and how to move forward, is dependent on that business context and the expectations it brings of you/your team/area. Gaining an understanding of those expectations in the absence of a direct flow of communication is a valuable skill in its own right, the acquisition of which takes care and discretion but will serve you well, both with advance notice of opportunities and warnings of detrimental changes.