Helps bootstrap be projects by temporarily joining teams and working with tech lead and/or manager.Aligned to the engineering organization. My last company had both roles and they shook out like this: Implement and identify methods to scale and automate product maintenance, management of our core platform, and analytics Generate scalable solutions in order to support growth within the organization and the product Leading technological meetings and proof-of-concepts with clients Research and solve problems in our environments, and exploring a new fields on a daily basis On-call rotation to maintain and support the production service Problem analysis and collaborating with product to create plans that continue to help our current users and get new onesĬoding across the full stack by executing those planesĪchieving technical excellence and mentoring and coaching other engineers in the team & group Owning from the commercial success to operational insight of specific features in the product The solutions architect will have some customer facing interactions. I'm not sure what's the career outlook/path for these two positions, cross industry wise nor how these two roles are actually are. I'm having the option to select between these two positions, and I'm not sure what's the actual difference between the two. 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
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |