![](/static/66c60d9f/assets/icons/icon-96x96.png)
![](https://lemmy.ml/pictrs/image/d3d059e3-fa3d-45af-ac93-ac894beba378.png)
Yeah, that sounds pretty normal, I guess. The time-frame part is probably based on how new you are as well as the nature of the task. I did quite a bit of that type of thing when I started, basically fixing tech debt, and small stuff.
If it’s something you want to bring up, I think you expressed yourself pretty clearly. You could schedule some time with your boss to talk about it.
What would frustrate me would be the rework I was doing. If you could maybe even set up a short weekly meeting? Show your boss what you’re doing and they could tell you if it’s the right track or not.
My interview for an internship that became my first developer job, for sure. It wasn’t a traditionally “technical” interview, meaning it wasn’t the latest trivia ever. They looked over my resume, and asked me technical questions about what I had done, decisions I made for projects, etc. The team just didn’t believe in staring at people trying to code on a whiteboard.
Got the offer within about an hour and didn’t have to interview to sign on permanently. I have subsequently always refused interviews where salary range wasn’t disclosed up front, and if I talk to a recruiter, I have always asked for contact information for a dev on the team.
But, that’s the advantage of having a job I don’t need to leave, and having experience. I’ve heard much worse from others.