AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
If you have very specific skills, but not a lot of breadth, you better be able to prove you're an expert in that focus. At 20+ years of experience, I would hope you have enough trust / access to be able quantify a business benefit of at least some of the things on your resume. For example, "Improved system infrastructure to better match current usage capacity, resulting in a 60% decrease in monthly team expenses" or "Modified team build process to run unit tests in parallel, resulting in a 50% decrease in development build times" are things I'll look at and say "Cool!" I know some people say the numbers are meaningless, but I notice them. ![]() If you can quantify the impact of your work. ![]() Possibly even having worked on multiple verticals (Health Care /Entertainment / Real Estate / Finance / Government / etc. So, if your tech list says Java or Angular or React or TypeScript I'd like to see in your work history that you worked on a project using Java or Angular or React or TypeScript.Īt the experienced level, I would expect the candidate to have a breadth of knowledge having touched on multiple languages / tools throughout their career. If you're listing a language or tool as something you know I want to see it mentioned in the details of your jobs. I haven’t heard of many people getting LeetCode hard questions in interviews (even at FAANG), so I just tell people to ignore those. It can take some hours to get into the flow of LeetCode Mediums and study common algorithmic tricks. ![]() If someone has been programming for 20 years then the kinds of problems you see in LeetCode easy shouldn’t need prep, really. My real-world skills have grown past what can be tested in a short interview, so I have to practice the exercises that do fit into interviews. It helps that I’ve led projects that are known by many people in the tech industry.īut if I step outside of my network and talk to people who don’t know anyone in my network and don’t recognize my past work, then I fully accept that I’ll have to do some interview prep. Once you get to a certain level with enough of a reputation and a network, you can lean on your past results and accomplishments as known by peers and as listed on your LinkedIn page. Related Subsįor what it’s worth, I haven’t submitted a resume for a job in probably 8 years now. It might be OK to talk about the merits of an interview process, or compare what has been successful at your company, but if it ends up just turning into complaints your post might still be removed. There is no interesting/new content coming out. This has been re-hashed over and over again. No questions like “Should I learn C#” or “Should I switch jobs into a language I don’t know?”ĭiscussion about industry direction or upcoming technologies is fine, just frame your question as part of a larger discussion (“What have you had more success with, RDBMS or NoSQL?”) and you’ll be fine.Ħ. This includes almost any discussion about a “hot market”, comparing compensation between companies, etc. General rule of thumb: If the advice you are giving (or seeking) could apply to a “Senior Chemical Engineer”, it’s not appropriate for this sub.Īsking if you should ask for a raise, switch companies (“should I work for company A or company B”), “should I take offer A or offer B”, or related questions, is not appropriate for this sub. ![]() Career advice threads may be removed at the moderators discretion based on response to the thread." This sub is for discussing issues specific to experienced developers.Īny career advice thread must contain questions and/or discussions that notably benefit from the participation of experienced developers. Violations = Warning, 7-Day Ban, Permanent Ban. This includes posts that could be interpreted as trolling, such as complaining about DEI (Diversity) initiatives or people of a specific sex or background at your company.ĭo not submit posts or comments that break, or promote breaking the Reddit Terms and Conditions or Content Policy or any other Reddit policy. No racism, unnecessarily foul language, ad hominem charges, sexism - none of these are tolerated here. If you have less than 3 years of experience as a developer, do not make a post, nor participate in comments threads except for the weekly “Ask Experienced Devs” auto-thread. Do not participate unless experienced (3+ years) This community leans towards being a specialized subreddit facilitating discussion amongst individuals who have gained some ground in the IT world.įor an idea of what is encouraged in this subreddit and what is not (please report anything that does not follow the rules): Rulesġ. Welcome to the /r/ExperiencedDevs subreddit! We hope you will find this as a valuable resource in your journeys down the fruitful CS/IT career paths.
0 Comments
Read More
Leave a Reply. |