#Coding #LearningToCode #SoftwareDevelopment #VueJS đ
If youâve been learning how to code for over a year, you’re already on the right track to becoming a successful software developer. It’s impressive that you’ve built up basic knowledge in HTML, SCSS, and JavaScript while juggling a full-time marketing job. But if you’re worried about not being taken seriously by potential employers due to receiving help at home, don’t fret. Here are some tips to help you approach obtaining a role as a junior software developer:
## Showcase Your Skills and Projects
– Make sure your project is polished and showcases your abilities in HTML, SCSS, and JavaScript.
– Highlight the features you implemented, such as connecting to an API, displaying data, and incorporating sort/filter/search functionality.
– Provide a link to your project on your resume or portfolio website.
## Networking and Building Relationships
– Attend local meetups, workshops, or conferences related to software development.
– Connect with other developers on platforms like GitHub and LinkedIn.
– Ask for feedback on your project from more experienced developers.
## Continuous Learning
– Stay up-to-date on the latest trends and technologies in software development.
– Consider taking online courses or obtaining certifications to further enhance your skills.
– Practice coding challenges on sites like LeetCode or HackerRank to strengthen your problem-solving abilities.
## Prepare for Interviews
– Be ready to discuss your project in-depth, including the challenges you faced and how you overcame them.
– Practice coding exercises commonly asked in interviews.
– Show enthusiasm and passion for software development during the interview process.
## Be Transparent
– If asked about receiving help on your project, be honest about the support you received.
– Emphasize your role in the project and the skills you’ve developed throughout the process.
– Highlight your willingness to learn and grow as a software developer.
Remember, the most important thing is to demonstrate your passion and dedication to software development. Employers are looking for candidates who are eager to learn, collaborate, and contribute to their team. Stay confident in your abilities and continue to hone your skills. Good luck on your journey to becoming a junior software developer! đ
By following these tips and suggestions, you can improve your chances of successfully obtaining a role as a junior software developer in a competitive industry. Remember to stay committed to your learning journey and continue building your skills and experience in software development. With determination and perseverance, you will be well on your way to achieving your career goals in the tech field.
Just start applying. You are making up an issue in your head that doesnât exist yet. Best of luck on your journey.
Early onset imposter syndrome. Don’t over think it you’ll do fine, its just like any other job
Honestly, right now itâs an uphill battle for most but itâs way tougher for junior engineers.
Also, I donât fully understand the problem. Why would someone think that you got help? Do you start the interview by talking about your SO being a lead engineer? Or you mostly focus on yourself?
Why are you going to tell them your wife is a swe?
Define your profile:
[https://roadmap.sh/](https://roadmap.sh/)
Learn the basics:
[https://www.freecodecamp.org/learn/](https://www.freecodecamp.org/learn/)
[https://www.freecodecamp.org/news/what-every-software-engineer-should-know/](https://www.freecodecamp.org/news/what-every-software-engineer-should-know/)
[https://python.plainenglish.io/top-8-algorithms-every-programmer-should-know-93c826267938](https://python.plainenglish.io/top-8-algorithms-every-programmer-should-know-93c826267938)
[https://www.freecodecamp.org/news/introduction-to-algorithms-with-javascript-examples/](https://www.freecodecamp.org/news/introduction-to-algorithms-with-javascript-examples/)
Participate in different projects:
[https://www.codetriage.com/](https://www.codetriage.com/)
[https://gauger.io/contrib/#/language/javascript](https://gauger.io/contrib/#/language/javascript)
[https://firstcontributions.github.io/](https://firstcontributions.github.io/)
Improve your portfolio:
[https://github.com/florinpop17/app-ideas](https://github.com/florinpop17/app-ideas)
Prepare yourselft to interviews:
[https://github.com/jwasham/coding-interview-university](https://github.com/jwasham/coding-interview-university)
[https://github.com/yangshun/tech-interview-handbook](https://github.com/yangshun/tech-interview-handbook)
[https://github.com/DopplerHQ/awesome-interview-questions](https://github.com/DopplerHQ/awesome-interview-questions)
The issue youâre concerned with doesnât even exist dude wtf just apply
Possibly have your partner invoice you for a project that shows your skills and then create it for them as a real world project and receive a good review for it on linked in and have it actually deployed online. Something crud in nature with nice interface. This will give you âwork experienceâ and real world experience in eyes of HR and approval by someone who is already in industry on a product you actually made will look good on your resume. Sadly sometimes even if you have projects on GitHub youâll get ignored unless itâs customer facing and has real presence so the above is a way to try navigate the silly HR systems so your more likely to be seen for your skill and talents
maybe u’ll get hired to fill some quota since the market is filled with super competive male candidates.
comeon guys dont get mad, embrace reality.
u wont get taken seriously cus u dont have a degree
I wouldnât worry about that. The companies I worked at will require you to take a coding test to provide your knowledge. The hardest part these days is getting an interview.
They won’t care if you have help. They won’t likely even look at your resume unless your boyfriend pulls some strings. There are millions of people with your same skillset that cannot find jobs right now. Your resume looks like every other self taught that learned how to make a Vue or React CRUD app. Its an employers market and they have no reason to choose a somebody with no work experience. They can pay a senior 150k+ a year and have them produce value on day 1 or they can take a chance on a noob for 1/3 the price. The noob will take several months to several years to be able to put out value. After 2 years once they train you and you are generating value you will job hop for a pay raise. Go ahead and look at the job boards and you will see they literally have thousands of applications and all of them are people that can make a basic crud app that want to hop jobs into tech. You have to stand out somehow, in this market that would be releasing an open source project that thousands of people find useful and use. Releasing an app that has tens of thousands of downloads, Creating some sort of SAS service that generates revenue. Sorry to be such a downer but I self studied for 2 years and can make small full stack apps, video games, mobile apps a lot of things and I have never gotten an interview because I dont stand out, everyone can do this. I am pursuing other paths and perhaps when the market settles I will look at it again. If you are really serious about this I would get a CS degree as self taught is hard without nepotism or real world projects that generate business value. Here is my portfolio if you’re interested https://seanred.io.
Nobody cares if you got help at home, apply for roles as per usual.
The thing about software development jobs is that there is so much more to them than the coding. You need to be prepared in other ways as well. Picture this – first week at your new job – they give you a Mac and tell you to set up Docker and clone a project from Git and get it running on your machine. Can you handle that?
Or in another situation – you’re given a project to write something in vue.js that pulls data from the backend, but the backend needs to connect to some external system. Now you and the backend engineer need to coordinate to make it clear what you need. Are you comfortable with that?
Finally – you’re given thousands of lines of legacy code in another language and they’d like you to rewrite that in Vue.js. You may have help, but you may also just have to take this on and figure it all out yourself.
It’s very possible that you may encounter none of these situations, but in my experience the people who fail are often the ones who can’t handle things above writing code in isolation all day.
I’m a self-taught lead engineer.
Getting started, I crawled through several free online boot camps and **several** hours of courses to build projects for my GitHub profile. I had about a year’s worth of demos, notes from lessons, small projects, and code challenge solutions.
When I started handing out applications, not one person asked me a single question about *any* of them. All they wanted to know is what technology I was comfortable with, and to back up those claims with a technical interview.
Granted, this was before the COVID industry boom, but even today, as a lead engineer, when I snoop on new juniors all I want to know what their coding style is like. I couldn’t care less what the project is or does; I’m looking at their technical skills to see if they understand what they’re writing, and how clean and maintainable their code is.
Asking if they had help would never even cross my mind, and if they did, it just means that they’re willing to learn and use better methodologies they may have been otherwise unfamiliar with.
You should ask your SO to run you through some practice interviews. Good luck with your job search, I’m sure you’ll be fine.
Why would they think youâve had help at home.
Because your wife is a developer?
How and why would they have that information?
You should work on your critical thinking skills, and probably learn to lie, because if you donât you ACTUALLY wonât make it in tech.
Nothing wrong with getting help.
Most important is how much of that knowledge you retained, and how useful you can be for potential employer.
When I was on entry position I just lied that I was middle and jumped over all the junior mess, try it out
Developer for some 30+ years and more importantly a hiring manager and technical director, these days.
âProperâ teams will look over your code, if you supply them with the repo. Things to make sure of:
1. Make sure the code is clean, succinct and readable.
2. Only comment code where necessary, I.e. a complex piece of logic.
3. Ensure everything runs, as expected. They may well clone the repo and test.
4. Hide (make private) anything unfinished.
5. Make use of runners and tests.
6. Make sure your README (I.e the documentation) is as clear as possible, without going into vast amounts of pointless detail.
Mostly, be confident and inquisitive. For me, itâs less about the answers given to the questions I ask. Anyone can memorise stuff. Iâm more interested in the things you donât know. If I ask a tricky question (designed to trip people up), I want to see their mind working and how they address the problem and even make a guess. For hiring managers, the key thing is to clearly explain where youâre at, that way we know what the onboarding process will look like. No matter the level or the framework / tech stack, any new dev coming in requires onboarding.
Spoilers:
1. If they say anything along the lines of âweâre a family hereâ – run and donât look back. Itâs not a family itâs a team.
2. Everyone says theyâre Agile. Theyâre not. 90% of companies donât know what theyâre doing. Iterative development cycle with a tonne of context switching or distractions, ISNâT Agile. Ask about their processes and ceremonies. Ask how they mitigate sprint failure.
3. Ask about the tech stack and version locks and get them to justify. If they reply with something like âlegacy monolithic architectureâ, be prepared for some archaic code that I promise, most teams wonât even look at âthat part of the codeâ, let alone touch it, after some bearded clever chap who loved crisps wrote it in 1994.
Be prepared for rejection. Itâs harsh, but it happens a lot. Most companies these days donât even reply and it makes me sad. Reply always and feedback so folk can improve. Thatâs my motto!
Good luck in your search and welcome to the world of dev!
You’re not ready yet. You need to learn a lot more. Being a programmer is a lot more
than building a front end that sends requests to an API, and handles the responses. I’d say build at least 3 or 4 more. It wouldn’t hurt to also learn the basics of how backends and databases work. But you do have one good thing going for you. Your partner is a programmer. That is worth more than you realize, because getting hired is about who you know. That’s the big thing.