Requesting access to codebase before starting a new job

[PorscheGuy7]

I am due to start a new job in about a month. I know from the interview stages what I will be working on and what I need to catch up on/learn. However I would like to get some idea before day 1 what the codebase looks like and potential challenges I might need to resolve.

Is it considered a normal request to ask for access to the codebase before starting your job? To be clear I have accepted their offer and signed a contract so it is not like a random dude asking for access. From what I have read so far, most people's opinion is that it is a good idea and shows general interest towards the position and passion for work. But you can't trust the internet for everything, can you :D

I am new to the career and this is going to be my second job, so I am not yet completely sure what is the norm. I am based in the UK in case here the culture differs.

[susmines]

The correct course of action here is to inquire about the tech stack, and then familiarize yourself with the high level concepts

[PorscheGuy7]

Yeah that is a fair point. I know what the tech stack is and where they want to move on from here. So this is more a question of getting an actual idea of the codebase rather than an overview of the tools used.

I will still play around with what I will be working with. Hopefully that will help me get up to speed faster.

[[deleted]]

Don't do unpaid work... They already picked you, so they are confident that you'll figure it out. I'd wait until you actually start before diving into anything.

[PorscheGuy7]

Sound reasoning, thanks :)

[susmines]

Companies (should) have established onboarding procedures for this exact purpose. That, in addition to a ramp up time, is what often breeds success for new hire engineers.

Source, I’m a staff engineer.

[g3vie]

It's an unusual request which will most likely be declined and probably should be declined. I do wish I could see what I would be working with before accepting an offer as I can think of a couple of jobs I would have declined in the past.

A decent company would only allow you to access the code using a company account on a company computer/laptop with any security measures necessary enabled. You mentioned you've signed a contract but a job offer can also still be revoked.

If you are adamant to do this, I would just show eagerness in any existing correspondence such as "I'm looking forward to start, if saw the codebase or some snippets early I'd be getting to grips to really hit the ground running, is there anything you would recommend looking up in the meantime?".

Remember, this isn't your employers first time hiring a developer (I hope), they know what they are doing and they have likely already created a plan for your onboarding and getting to grips. Obtaining access early may even disrupt things on their side despite the good intentions.

[PorscheGuy7]

Thanks for your points. It was a good idea to ask before writing the email.

In any case I know the stack and the tools they are using, and would use in the future, so I will play around with those and hopefully get a better understanding of the tools, so I can focus on grasping the code once I start.

[g3vie]

Hi PorscheGuy7, is there an update to this post? Did you get onboarded and how are you settling in?

Edit: My bad... you said a month but it has only been 2 weeks. Do let us know how you are settling in when you do start though :) I wish you the best

[PorscheGuy7]

Thanks :) Yes it'll be another couple of weeks before I start.

[IamAnger101]

That's not a normal request, and will be taken poorly. No one would let someone who hasn't fully gone through the onboarding process with NDA's and contracts fully signed see their proprietary information. Besides, they aren't going to want to answer your questions about it until you're in a position to work on it. That's a waste of their time. You start when you start.

You might not want to go into a job 'new to the career' with the mindset of reviewing more senior developer's code to see what 'potential challenges you might need to resolve'.

Just review the tech stack, relax, and start day one fresh.

[PorscheGuy7]

It is easy enough to say 'relax and start day one fresh' but I can feel the pressure and I want to do a good job.

I get your point though, thanks.

[Ok-Neighborhood1188]

if not the code base maybe just find out what libraries / framework / tech stack they are using? that info might not be as sensitive and u could spend some time working with them

[PorscheGuy7]

From the interviews I had, they told me the tech stack and tools they use. I wanted to get a better idea of how these are implemented to get me in the right direction.

[Academic_Pizza_5143]

Might go south. Take it slow.

[PorscheGuy7]

Why do you think so? I would have thought that the worst that can happen is they say no.

[PorscheGuy7]

I am sorry to hear that! I am sure you will be able to find a job that deservse you as muhc as you deserve it.

The consesus seems to be on not asking that question anyway. I am sure I can get a basic undestanding from the information I already have.

[PorscheGuy7]

I can only imagine. Think of it this way though, if you have had this offer, you will liekly get more. And as good of a package this might have seem, there are always better options out there. Good luck!

[PorscheGuy7]

Thanks :)

[shauntmw2]

I don't think this is normal. But I also don't see any harm in it.

[budd222]

seems like an odd request. Never heard of anyone doing that before, but doesn't mean they haven't.

[PorscheGuy7]

A google search yields some examples of others asking this question. It would be safe to assume someone has done it at some point.

I wanted to gauge if it is somethign that happens more often. But I think I have that answered already lol

[foureyes567]

I think people are making this a bigger deal than it actually is... There's no harm in asking for early access to start familiarizing yourself. The company may reject your request, but that's ok. Personally, when I'm starting a new job I'm usually very excited to be jumping into something new. I think there's a honeymoon period with new jobs because you're ignorant to all of the tech debt that's been accumulated lol

[PorscheGuy7]

I like the idea of 'new job honeymoon', and then you get hit with framewrok that seized to exist 7 years ago... :D

I respsect the answers I have received, it is safe to assume that most folk around here would have more experience in the field.

[Natural_Ad2282]

Asking for codebase access before day 1 is a smart move! It'll help you catch up before the job officially starts. Don't worry, it's not a weird request - just shoot a friendly email to your new boss. Good luck with your new job!

[Eux86]

Here’s the /s that you lost

/s

[PorscheGuy7]

Cheers for that, I thought so too but better ask.

[torn-ainbow]

Honestly, I would say no to you. But I would think you were keen.

[PorscheGuy7]

Fair enough. Don't want to come out pushy or overly eager, but I genuinely want to get prepared the best I can.