I have 6 years of experience but mostly as a front end dev. I have got a new job and just finished my third week at the new company. They have placed me on a fullstack role, I have no say and I can't change that. I can't tell them that I only have experience with frontend either otherwise I won't have this job and my family have to stay without a shelter. The programming language they use is completely different from what I know and the product and the engineering practices are so foreign to me also. They are generally much more knowledgeable than me. This week was the third week on the job. I have heard that generally as of fourth week their expectations will start to shape up and that I need to be able to produce code and be able to not sound so irrelevant in the meetings. I have no idea what to do as I'm so stressed and the anxiety is killing me. Any ideas? Have you ever been in that situation? If so what did you do? I acknowledge that I'm not a great engineer so I'm looking for tips helping me to survive the situation and meet expectations. Quiting or changing jobs are not viable options at the moment either. Thank you and have a great weekend.
Take couple of courses from Udemy in areas where you area struggling. Sometimes just 20 hours of learning can make wonders. It is ok to not know everything .
Learn to code lmao stop complaining and start learning.
"Fake it till you make it" and study like it matters to you. You were a front end dev, I assume with strong javascript. Assuming you are now doing java, c#, python or something else. These high level languages all have the same concepts so ask yourself how you would do it then google "how to do THING in LANGUAGE ". For style and concept advice look at how they are coding and borrow as much as you can from their old code. This is how I learn on the job, even if it's in a language or platform I'm familiar with, I always observe the flow and patterns my teammates use and like. And it's a great way to learn some new tricks. They are right though, in 4 weeks you should be able to operate so get in there and start twisting knobs to see how the code works. Edit: I think a great example is a for each loop, all of these languages have it but they all do it slightly different.
Awesome advice
You just have to slog, there is no way out. I would say , create a sandbox and try to get one thing working. Just making one feature work will give you a great insight into their infrastructure and framework, and will give you much more confidence.
lol not just white every girl
Spartan, considering you just complained about racism in a post, I am surprised about your sexism. And no, propagating negative biases is not funny.
Have a drink and calm down it’s only a job. life is short
You clearly don't understand Blind!
Curious if you can’t do this how did you get hired if you’re so off on the requirements. If you don’t suck there’s plenty of jobs out.
Also, expecting you to be productive after a month and knowing your background only had front end work is unjust. Are you sure you are not stressing for no reason? It is easy to do that in earlier weeks / months of joining a new company.
So saying one passes the “standard” data structures and algorithms interview doesn’t necessarily equate to actual performance on the job. I am not demeaning you but probably the employer who thinks the pay you generously should expect you contribute generously as well.
I’m in a somewhat similar situation. 4 years experience. I have adapted to code standards and process over the last six months, but I’m the most junior individual and daily duties range from dev ops to engineering to QA. 1. I don’t think they expect sweeping contributions after 4 weeks. I thinks it’s more so that they expect a basic enough understanding for you to start asking questions and getting the information you need to be successful in completing your tasks. After four weeks, you should no longer be completely silent, you should have questions on infrastructure, code standards and style, industry knowledge. 2. As far as not being comfortable full stack and not knowing the language, it’s likely you understood those shortcomings going into the position. If you’re not putting in your own time to learn these things, then you’re screwing yourself. It’s your duty to make sure you have a great enough command of the tools you work with to be successful. 3. Communicate with more knowledgeable engineers. Ask questions before you’ve spent a ton of time spinning your wheels. Be sure to do some research before reaching out to them, let them know what problem you’re facing, what you’ve tried, and how they can help you. It’s in the teams best interest for you to succeed, and (most) people are typically understanding when you’re new. These are things that have helped me survive the last 6 months. I’ve found that open communication is the most important thing, as suffering in quiet can make it seem like you lack problem solving skills, and don’t care to finish you work in a timely manner. Hope that helps.
How did you get hired?
The interviews were based on general algorithms interviews and the programming that they needed me to do were based on algos and data structures and I was able to do the algorithm questions no problem but the job and the applications that thry are building are so different from what I had to perform on the coding interviews.
Probably irrelevant now, but what did the job description/ posting say about the role?