New Starter - FullstackCodingGuy/Developer-Fundamentals GitHub Wiki

A new starter should give more focus to the organization's core principles.

Research & explore about

  • Core Values
  • Culture
  • Operational Load
  • Team's Responsibility
  • Individual's Responsibility
  1. Prepare, prepare, prepare
  • Learn everything you can about the company, culture and job challenges beforehand; it shows you care
  1. Use STAR and on every job requirement
  • Situation - Set up the stage for the story by sharing context around the challenge
  • Task - Describe your role in that situation
  • Action - Explain the specific actions or measures you took to complete the task
  • Result - Using numbers explain the ultimate result
  1. Prepare a lot of stories
  • Interviewers love hearing stories; have several ready that show off your skills
  • Keep stories between thirty seconds to a minute to stay engaging without rambling
  • Have a clear, concise story for any sticky spots on your CV and be ready to explain them away
  1. Ace the first 5 minutes
  • Your first impression is key; enter with confidence and speak clearly
  • Break the ice with a compliment to make the interviewer warm to you
  • If you share an interest with the interviewer, great, chat away! If not, don't pretend
  1. Be Honest. No BS.
  • Always tell the truth in interviews; a fib can be spotted a mile away
  • Remember, honesty is not just good for interviews, it’s a solid rule for life
  • Being open about past mistakes makes you more relatable
  1. Don't be negative
  • Never criticise past employers or colleagues, as it may reflect poorly on your character
  • With a positive tone, focus on what you've learned from challenging situations
  1. Emphasise YOU and your potential
  • Don’t worry if you're not a perfect match; show how quick and eager you are to learn
  • Focus on what you've actually done and solid examples, not just what you were part of
  • Focus on YOU over skills. Employers more often value attitude over experience
  • Not everyone has read your resume; help them by repeating all the juicy bits
  1. Not Too Short, Not Too Long
  • Balance is key; give enough detail without going overboard
  • Practice your responses to gauge if you waffle and adjust accordingly
  1. Don’t be afraid to think
  • It’s alright to take a moment to consider your response
  • Pausing shows you're thoughtful and take care in what you say
  1. When it’s going poorly
  • If the interview seems off, don't dwell on it; focus on nailing the next question
  • It's okay to check in with the interviewer to see if they need something more from you
  1. Don't overdo the questions at the end
  • Remember it's quality over quantity; ask thoughtful questions
  • Choose insightful questions that show you're thinking about the VALUE you can add
  1. Your interview isn’t over when you walk out of the room
  • The post-interview thank you email is your final chance to make a memorable impression
Leadership Responsibilities
  • Partner with Product Management, UX Development, Cloud Engineering, Architecture and business stakeholders to create product roadmaps and release schedules.
  • Communicate project status and escalate issues to direct managers, product management, and internal development partners.
  • Build strong relationships with business and technology stakeholders.
  • Advance the development of engineering standards, employee onboarding guides, product documentation, and engineering documentation.
  • Proactively identify opportunities for process improvement and cost reductions.
  • Manage headcount, deliverables, schedules, and costs for multiple ongoing projects, ensuring that resources are appropriately allocated and that goals, objectives, timelines, and budgets are met in accordance with organizational roadmaps.
  • Oversee the development of SaaS and Mobile products.
  • Champion Agile methodologies including the Scrum framework.
  • Leverage Agile practices to create repeatable and predictable software releases.
  • Identify software delivery problems within teams and use your knowledge and experience to help resolve issues.
  • Communicate release issues early, and work with Product Management, Architecture, Platform Engineering, and others to mitigate issues.

  • Lead one or more teams of software developers while helping create a culture of high-performance
  • Deliver best-in-class software by mentoring development team leads, and individual contributors on software development best practices
  • Help engineering teams tackle challenging problems by having a bias for action, including breaking problems into workable chunks, using iterative development, and leveraging software architecture design patterns.
  • Define metrics for all engineering teams, oversee implementation of metrics measurement, and report on KPIs to executive leadership.
  • Lead high-level (epic level) estimation exercises for product releases.
  • Mentor development team leads on estimation techniques for feature and story level estimation.
  • Provide people management for team members, including hiring, setting, and monitoring annual performance plans, coaching, motivating, rewarding, and career development.
  • Scale teams that mix veteran talent eager for new challenges and new team members looking to grow their skill sets.
  • Manage relationships with strategic partners and suppliers, including setting expectations regarding deliverables, product quality, schedules, and costs. Ensure that team members are effectively communicating and collaborating with these third-party resources.
⚠️ **GitHub.com Fallback** ⚠️