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.

  • dependencyinjectionOP
    6·
    1 year ago

    You’ve got this bro.

    Getting my first role was the hardest thing I’ve done and a little soul destroying. So much so that after the first bootcamp and many rejections I did another bootcamp and then loads more interviews.

    I suck at interviewing as I have ADHD and I’ll either be too open and honest or I’ll just clam up and seem like an idiot. The more you do it the easier it gets.

    If I can get a role, then anybody can.

      • buzziebee@lemmy.world
        1·
        1 year ago

        Keeping it simple and moving on was a smart move. Your portfolio doesn’t need to be super fancy unless that’s the specific skill you’re selling (fancy designs and UI). Most jobs aren’t doing anything with threejs. Most jobs are crud apps, so focus on demonstrating skills to do with that.

        Svelte is also cool but the majority of jobs aren’t for svelte Devs, and most aren’t for Greenfield projects with bleeding edge tech. Where I am for FE it’s something like 60% react, 30% Angular, 10% Vue/svelte/whatever else. Just focus on building things which show you can do what the jobs you’re looking to apply for need.

        If you’re going full stack then just focus on one stack and focus on building (preferably novel) actual things that all work together. If you have full projects showing you can self direct and implement semi complex systems from start to finish in a stack that’s close enough to what employers are looking for you’ll have a lot more luck landing a job.