As the title say I am looking for some advice.

I’m almost 6 months into my first role and it really isn’t what I expected.

I’m late thirties and always had an interest in tech, but personal circumstances and a late start in life left me unsure if I was good enough.

I did too many boot camps and in all them they discussed how in your first role you would get lots of support to help develop your skills.

I work for a small company < 10. I don’t feel I get the support I expected.

A lot of time the spec is kept in the lead engineers (owners) head and when given a task I get no timeframe, the task is given verbally with 100 words when I need 1000 words. It’s confusing to understand their vision so I’ll do something and either be told great or no that’s completely wrong.

If wrong I’m not called out and they will spend a little more time going over what they want.

The boss is always so busy that sometimes you feel like a burden asking for pointers.

The tech stack is great but as a mature company they have refined the process over numerous projects and the newest will start as a copy of the last one, keeping all the shared hooks and stuff, so naturally it’s second nature to them and I feel stupid.

I guess my question is is this normal and how do I write an email expressing these concerns and to gauge how I am doing?

As an aside, there is no remote work and no headphones in the office, even though nobody really talks about work that often. So when is a good time to start looking for your second role.

I feel like I flip between I am a god and can code anything and omg I know nothing show me the nearest bridge.

Thanks.

  • rufus@discuss.tchncs.de
    4·
    8 months ago

    I don’t know who gives that advice. But from personal experience I’d say it’s like this in most companies. Everyone has a job to do and tasks to finish. Nobody has extended down-time to train ‘the new guy’. Especially the experienced people you’d like to learn from have important stuff to do.

    Some employers like their workers to actively solve their problems. So you could try to be more proactive and vocal about it. Say you’re not familiar with that project or tech and you need a more detailed explanation. Tell them what you didn’t understand and ask where you can look it up.