3 ms·

> My instructions when I joined were something like "Yeah so just talk to a bunch of people and look for opportunities to contribute". Do you mind sharing the

> My instructions when I joined were something like "Yeah so just talk to a bunch of people and look for opportunities to contribute". Do you mind sharing the job title for something like this? Sounds like a dream job.

loarabia 3y ago
Currently I’m a GTPM at Meta and this is the expectation we have for onboarding to a new team unless you’re early in career. I’ve seen this be the case for SWE and other roles in the technical domain. Typically you have an expertise area and at least on my team a starter project or 2 with a tangible deliverable to get you going on something while you ramp and meet others and figure things out. Meta is a big place though so could be other expectations in other organizations.
suzzer99 3y ago
I transferred within my company to the much bigger company that bought us out and this is basically what my boss told me. Actually his exact words were "you need to create your own job." I hated it. Give me a freaking task, don't make me network and sell myself (remotely of course, no one I worked with was anywhere near me) just for something to do. I created my own job, just with a startup. For a year I had two ostensibly full time jobs. By the end the startup wasn't doing much either and I considered going for three full time jobs.
- meinheld111 3y ago
  You seem to be doing something right. Imo most ppl are overworked and underpaid
saagarjha 3y ago
It’s less a job title (I’m a “software engineer” like everyone else) but the scope of the problem your role is aiming to solve. Look for places that 1. have an unsolved hard problem with 2. no real direction on where to go with it and 3. buy-in from someone to get it solved.
extr 3y ago
I was a Data Scientist. Personally I found the autonomy immensely frustrating. Combined with the stack ranking performance review system, it was effectively a way of pushing the manager's job on to the employee and forcing them to hold themselves accountable for their own priorities. Makes sense in theory, but once you add huge organization churn + being remote, it was difficult to get a sense of what priorities were exactly, or would be next month. It made me feel insecure at all times that perhaps I was working on the wrong thing and would be punished for it.

loarabia 3y ago

Currently I’m a GTPM at Meta and this is the expectation we have for onboarding to a new team unless you’re early in career. I’ve seen this be the case for SWE and other roles in the technical domain. Typically you have an expertise area and at least on my team a starter project or 2 with a tangible deliverable to get you going on something while you ramp and meet others and figure things out. Meta is a big place though so could be other expectations in other organizations.

suzzer99 3y ago

I transferred within my company to the much bigger company that bought us out and this is basically what my boss told me. Actually his exact words were "you need to create your own job." I hated it. Give me a freaking task, don't make me network and sell myself (remotely of course, no one I worked with was anywhere near me) just for something to do. I created my own job, just with a startup. For a year I had two ostensibly full time jobs. By the end the startup wasn't doing much either and I considered going for three full time jobs.

meinheld111 3y ago
You seem to be doing something right. Imo most ppl are overworked and underpaid

saagarjha 3y ago

It’s less a job title (I’m a “software engineer” like everyone else) but the scope of the problem your role is aiming to solve. Look for places that 1. have an unsolved hard problem with 2. no real direction on where to go with it and 3. buy-in from someone to get it solved.

extr 3y ago

I was a Data Scientist. Personally I found the autonomy immensely frustrating. Combined with the stack ranking performance review system, it was effectively a way of pushing the manager's job on to the employee and forcing them to hold themselves accountable for their own priorities. Makes sense in theory, but once you add huge organization churn + being remote, it was difficult to get a sense of what priorities were exactly, or would be next month. It made me feel insecure at all times that perhaps I was working on the wrong thing and would be punished for it.