Software Developer

Software Developer job interviews focus on assessing coding skills, problem-solving abilities, and understanding of software development principles. Candidates should prepare by practicing coding challenges, explaining their thought process clearly, and demonstrating teamwork experience. Technical knowledge combined with effective communication remains crucial for success in these interviews.

Tell me about yourself.

Focus on your software development skills, highlighting experience with languages like Java, Python, or C++, and your ability to work on financial technology projects. Emphasize your problem-solving abilities, teamwork skills, and any experience with financial systems or regulatory compliance relevant to Raymond James Financial. Conclude by connecting your background to the company's mission of delivering innovative financial solutions and how you can contribute to their technology-driven growth.

Do's

• Concise introduction - Provide a brief summary of your professional background relevant to software development.
• Highlight key skills - Emphasize technical expertise such as programming languages, frameworks, and problem-solving abilities.
• Align with company values - Mention how your experience and goals fit Raymond James Financial's mission and culture.

Don'ts

• Personal details - Avoid sharing unrelated personal information or hobbies unless they directly connect to the role.
• Vague answers - Refrain from giving generic responses without showcasing specific achievements or skills.
• Negative remarks - Do not speak negatively about past employers or experiences during your introduction.

Why do you want to work at Raymond James?

Highlight your alignment with Raymond James' commitment to innovation in financial technology and its strong reputation for client-focused solutions. Emphasize your passion for developing scalable software that enhances user experience and supports the company's financial services platform. Demonstrate knowledge of their technology stack and express enthusiasm for contributing to a collaborative team that drives impactful financial solutions.

Do's

• Research Raymond James - Highlight your knowledge of the company's financial services, culture, and recent projects.
• Align Skills with Role - Emphasize how your software development expertise matches the technical needs of Raymond James.
• Show Passion for Finance Technology - Express genuine interest in developing innovative financial software solutions.

Don'ts

• Generic Answers - Avoid vague responses that do not mention Raymond James specifically.
• Focus Solely on Salary - Do not prioritize compensation as your main motivation for joining.
• Neglect Company Values - Avoid ignoring Raymond James' emphasis on integrity and client service.

What interests you about the Software Developer position?

Highlight your enthusiasm for developing innovative financial technology solutions that enhance client experiences at Raymond James Financial. Emphasize your alignment with the company's commitment to integrity and client-focused service, and your desire to contribute to scalable, secure software that drives business growth. Showcase your passion for continuous learning and collaboration within a dynamic, growth-oriented development team.

Do's

• Company Research - Mention specific projects or values at Raymond James Financial that align with your career goals.
• Skill Relevance - Explain how your software development skills match the job requirements and challenges.
• Career Growth - Highlight your desire to grow within the fintech industry and contribute to innovative financial solutions.

Don'ts

• Generic Answers - Avoid vague or overly broad statements that do not relate to Raymond James or the developer role.
• Salary Focus - Do not emphasize compensation or benefits as the main reason for interest.
• Negative Comments - Avoid speaking negatively about previous employers or jobs when explaining your motivation.

Describe a challenging software project you've worked on.

Focus on a complex software development project involving financial technology, emphasizing your role in designing scalable, secure, and efficient solutions. Highlight challenges such as integrating with legacy systems or ensuring compliance with financial regulations while maintaining performance and data integrity. Describe how you collaborated with cross-functional teams, applied problem-solving skills, and delivered results that improved business processes at Raymond James Financial.

Do's

• Project Complexity - Describe the technical challenges involved, highlighting your problem-solving skills.
• Role and Contribution - Clearly state your responsibilities and the impact of your work on the project's success.
• Technologies Used - Mention relevant programming languages, frameworks, and tools applied during the project.

Don'ts

• Negative Blame - Avoid blaming team members or external factors for project difficulties.
• Vague Responses - Do not give generic answers that lack details about specific challenges or solutions.
• Omitting Results - Avoid neglecting to discuss the outcomes or achievements resulting from the project.

Explain the software development lifecycle.

The software development lifecycle (SDLC) involves a systematic process of planning, designing, developing, testing, and deploying software applications to ensure quality and efficiency. Key phases include requirement analysis, system design, coding, testing, implementation, and maintenance, each crucial for delivering robust software solutions. Demonstrating knowledge of SDLC models like Agile or Waterfall highlights adaptability and understanding of structured development at Raymond James Financial.

Do's

• Requirement Analysis - Clearly describe gathering and understanding client needs to define project goals.
• Design Phase - Explain creating system architecture and design specifications that guide development.
• Testing and Deployment - Emphasize thorough testing strategies and smooth deployment processes for software delivery.

Don'ts

• Overlooking Documentation - Avoid ignoring the importance of maintaining detailed records throughout the lifecycle.
• Skipping Testing - Do not neglect the testing phase as it ensures software quality and minimizes defects.
• Using Technical Jargon Excessively - Refrain from using overly complex terms that might confuse non-technical interviewers.

What programming languages are you most comfortable with?

When answering the question about programming languages you are most comfortable with for a Software Developer position at Raymond James Financial, emphasize languages relevant to financial software development such as Java, Python, C#, and SQL. Highlight your proficiency by mentioning specific projects or applications where you utilized these languages effectively, demonstrating your ability to solve complex problems and optimize financial systems. Focus on your adaptability and continuous learning approach to stay updated with emerging technologies in the financial services industry.

Do's

• Be Honest - Clearly state the programming languages you are proficient in without exaggeration.
• Highlight Relevant Languages - Emphasize languages commonly used in financial software development, such as Java, Python, or C#.
• Provide Examples - Mention specific projects or experiences where you successfully used these languages.

Don'ts

• Don't Overstate Skills - Avoid claiming expertise in languages you are unfamiliar with to prevent future issues.
• Avoid Irrelevant Languages - Do not focus on languages that are not applicable to the job role or financial industry.
• Don't Be Vague - Refrain from giving general answers like "I am comfortable with many languages" without specifics.

How do you ensure the quality of your code?

To ensure the quality of code in a software developer role at Raymond James Financial, implement rigorous unit testing and adhere to coding standards that align with industry best practices. Utilize version control systems like Git for collaborative code review and employ static code analysis tools to identify potential vulnerabilities early. Consistently perform integration testing within agile workflows to maintain high reliability and compliance with financial software regulations.

Do's

• Code Reviews - Participate in regular code reviews to catch bugs and improve code quality collaboratively.
• Unit Testing - Write comprehensive unit tests to validate functionality and prevent regressions.
• Continuous Integration - Integrate code continuously using CI tools to ensure early detection of errors and maintain consistent quality.

Don'ts

• Neglect Documentation - Avoid skipping documentation as it hinders code maintainability and team collaboration.
• Ignore Code Standards - Do not overlook established coding standards and best practices as they ensure readability and consistency.
• Skip Testing - Refrain from deploying code without adequate testing to prevent defects in production environments.

What is your experience with Agile or Scrum methodologies?

Highlight hands-on experience with Agile frameworks such as Scrum by detailing roles in sprint planning, daily stand-ups, and retrospectives that improved project delivery times. Emphasize familiarity with tools like Jira or Trello for managing user stories, backlog grooming, and continuous integration pipelines. Showcase collaboration with cross-functional teams at Raymond James Financial to adapt Agile practices for enhanced software quality and stakeholder satisfaction.

Do's

• Agile Framework - Explain your familiarity with Agile principles including iterative development and continuous feedback.
• Scrum Roles - Describe your experience working as a Scrum Master, Product Owner, or team member within Scrum teams.
• Practical Examples - Provide concrete examples of projects where Agile or Scrum improved delivery efficiency and team collaboration.

Don'ts

• Overgeneralization - Avoid vague statements about Agile without specific examples or outcomes.
• Ignoring Challenges - Do not pretend Agile environments are flawless; acknowledge any obstacles and how you addressed them.
• Technical Jargon - Refrain from excessive use of technical terms that may confuse interviewers unfamiliar with detailed Scrum processes.

Describe your experience with version control systems like Git.

Highlight hands-on experience managing code repositories using Git, including branching, merging, and resolving conflicts, to ensure seamless collaboration in Agile teams. Emphasize familiarity with workflows like GitFlow or feature branching, and tools such as GitHub or GitLab for code reviews and continuous integration. Showcase how version control practices enhanced code quality, traceability, and deployment efficiency in past software development projects relevant to financial services.

Do's

• Highlight Git proficiency - Emphasize your experience using Git for branching, merging, and resolving conflicts in collaborative projects.
• Explain workflow knowledge - Describe familiarity with Git workflows like Git Flow, feature branching, or pull requests to demonstrate best practices.
• Showcase collaboration - Discuss how you used Git to improve team collaboration, code review, and version history tracking.

Don'ts

• Avoid vague statements - Don't say "I used Git" without specifying what you accomplished or how it benefited your projects.
• Don't ignore challenges - Avoid neglecting to mention how you handled merge conflicts or resolved version control issues.
• Skip irrelevant details - Don't dive into unnecessary low-level commands or technical jargon that does not align with the job role.

Have you worked with databases? Which ones? Describe your experience.

Highlight your experience with relational databases such as MySQL, PostgreSQL, or Oracle, emphasizing your role in designing, querying, and optimizing database structures. Mention any familiarity with NoSQL databases like MongoDB or Cassandra if applicable, and explain how you used them for scalable data storage or real-time analytics. Reference specific projects where database integration improved application performance or supported business goals, aligning your skills with Raymond James Financial's needs for secure and efficient data management.

Do's

• Specific Database Technologies - Mention precise databases like MySQL, PostgreSQL, Oracle, or MongoDB to show familiarity.
• Relevant Experience - Describe concrete projects where you designed, queried, or optimized databases.
• Problem-Solving Skills - Highlight instances where you debugged or improved database performance.

Don'ts

• Vague Responses - Avoid generic answers without examples of database usage or specific technologies.
• Irrelevant Details - Do not discuss unrelated technologies that do not apply to the role.
• Overstating Expertise - Avoid claiming proficiency in databases you are not confident in to maintain credibility.

How do you handle tight deadlines or pressure situations?

Demonstrate your ability to prioritize tasks effectively by breaking complex projects into manageable milestones and using tools like Agile or Scrum for iterative progress. Highlight your focus on clear communication with team members and stakeholders to align expectations and quickly address obstacles under tight deadlines. Emphasize maintaining code quality and testing rigor to ensure reliable software delivery despite time constraints, reflecting the high standards expected at Raymond James Financial.

Do's

• Time Management - Prioritize tasks effectively to meet tight deadlines without compromising code quality.
• Clear Communication - Keep team members and stakeholders informed of progress and potential roadblocks.
• Problem-Solving Skills - Demonstrate the ability to analyze issues quickly and implement efficient solutions under pressure.

Don'ts

• Panic - Avoid showing stress or anxiety that could undermine confidence in your ability to deliver results.
• Overpromising - Do not commit to unrealistic deadlines or goals you cannot meet.
• Ignoring Collaboration - Avoid working in isolation; leverage team resources and feedback to improve outcomes.

Describe a time you had to quickly learn a new technology or tool.

Focus on a specific instance where you rapidly mastered a programming language, framework, or financial software critical to a project at Raymond James Financial. Highlight your approach to self-directed learning, such as utilizing documentation, online courses, or peer collaboration to gain proficiency. Emphasize the positive impact this quick adaptation had on project delivery, team efficiency, or client satisfaction within a financial services context.

Do's

• Specific Technology - Mention the exact tool or technology you learned to demonstrate relevance and technical understanding.
• Learning Process - Explain your approach to quickly mastering the new technology, highlighting problem-solving and adaptability.
• Result and Impact - Describe the positive outcome your learning had on the project or team to show your value addition.

Don'ts

• Vague Responses - Avoid general statements without mentioning the technology or the steps taken to learn.
• Negative Focus - Do not emphasize difficulties or failures; keep the narrative positive and solution-oriented.
• Irrelevant Examples - Do not discuss technologies or scenarios unrelated to software development or Raymond James Financial's business domain.

What is your experience with REST APIs?

Highlight your hands-on experience designing, developing, and consuming RESTful APIs using technologies like JSON, HTTP methods, and REST architecture principles. Emphasize your ability to integrate APIs with backend systems, ensure security with OAuth or JWT, and improve performance through efficient endpoint design. Showcase examples of projects or tasks at Raymond James Financial where you successfully implemented REST APIs to enhance system interoperability and functionality.

Do's

• REST API Integration - Describe specific projects where you built or consumed RESTful APIs to enable system interoperability.
• HTTP Methods - Explain your understanding of standard HTTP methods like GET, POST, PUT, DELETE, and their appropriate uses.
• Security Practices - Highlight experience with API authentication methods such as OAuth, API keys, or tokens to ensure secure data exchange.

Don'ts

• Vague Descriptions - Avoid generalities like "I have used APIs" without concrete examples or outcomes.
• Ignoring Error Handling - Do not overlook mentioning strategies for handling API errors and response codes.
• Overemphasis on Theory - Refrain from focusing solely on definitions without discussing practical implementation and problem-solving.

How do you approach debugging and troubleshooting?

When addressing the question about debugging and troubleshooting for a Software Developer position at Raymond James Financial, emphasize a structured and methodical approach. Highlight your use of tools like debuggers, log analysis, and version control systems to identify and isolate issues efficiently. Stress the importance of understanding the financial domain's critical systems, collaborating with colleagues for root cause analysis, and documenting findings to prevent future problems.

Do's

• Systematic Debugging - Explain using structured steps to identify and isolate the root cause of issues.
• Use of Debugging Tools - Mention familiarity with tools like debuggers, log analyzers, and profilers to efficiently trace errors.
• Collaboration - Highlight working with team members and utilizing peer code reviews to resolve complex bugs effectively.

Don'ts

• Guessing Solutions - Avoid stating that you jump to conclusions without proper evidence or analysis of the problem.
• Ignoring Documentation - Do not overlook existing documentation or code comments that may aid in troubleshooting.
• Blaming Others - Refrain from pointing fingers at colleagues or external factors without constructive problem-solving focus.

Explain the difference between object-oriented and functional programming.

Object-oriented programming (OOP) centers on organizing code around objects containing both data and methods, promoting concepts like encapsulation, inheritance, and polymorphism for reusable and modular code. Functional programming (FP) focuses on pure functions, immutability, and avoiding side effects to create predictable and testable code. When answering, highlight your understanding of how OOP suits scenarios requiring state management and FP excels in process-oriented tasks, demonstrating adaptability relevant to Raymond James Financial's software development needs.

Do's

• Object-Oriented Programming (OOP) - Emphasize encapsulation, inheritance, and polymorphism as core principles allowing modular and reusable code design.
• Functional Programming (FP) - Highlight immutability, first-class functions, and pure functions that promote predictability and easier debugging.
• Use practical examples - Illustrate differences with real-world use cases relevant to financial software development, such as transaction processing or risk calculation.

Don'ts

• Don't use overly technical jargon - Avoid confusing terms without simple explanations to keep your answer accessible and clear.
• Don't dismiss either paradigm - Avoid negative comparisons; focus on strengths and appropriate use cases of each programming style.
• Don't forget company context - Avoid generic answers by tailoring examples and benefits to Raymond James Financial's focus on secure and reliable software solutions.

Walk me through a recent application you developed.

Describe the application's purpose, technologies used, and your key contributions, emphasizing how it solved specific user or business problems. Highlight your role in the development lifecycle, such as designing, coding, testing, and deployment, with measurable outcomes like improved efficiency or user satisfaction. Focus on aligning the project's impact with Raymond James Financial's commitment to innovation, security, and client-focused solutions.

Do's

• Project Overview - Provide a clear and concise summary of the application, including its purpose and key functionalities.
• Technology Stack - Highlight the programming languages, frameworks, and tools used in the development process.
• Problem-Solving - Describe challenges faced during development and how you resolved them effectively.

Don'ts

• Vagueness - Avoid giving unclear or generic descriptions about the application or your role.
• Overemphasis on Team - Don't take minimal credit if you contributed significantly; focus on your personal impact.
• Technical Jargon Overload - Steer clear of using excessive industry-specific terms without explanation.

Tell us about a time you disagreed with a team member. How did you resolve it?

Describe a specific situation where you and a team member had differing opinions on a project or technical approach during a software development cycle at Raymond James Financial. Focus on your communication skills by explaining how you actively listened, clarified misunderstandings, and collaborated to find a compromise or innovative solution that aligned with project goals. Highlight the positive outcome that improved code quality, met deadlines, or enhanced team cohesion within the financial software development environment.

Do's

• Conflict resolution - Describe a specific instance emphasizing how you professionally addressed the disagreement.
• Collaboration - Highlight how you worked together to reach a consensus or compromise.
• Communication skills - Focus on active listening and clear, respectful communication during the conflict.

Don'ts

• Blaming others - Avoid pointing fingers or criticizing the team member involved.
• Lack of resolution - Do not describe conflicts that were left unresolved or escalated negatively.
• Ignoring the impact - Don't overlook how the resolution benefited the team or project outcomes.

What automated testing frameworks have you used?

Highlight experience with widely recognized automated testing frameworks such as Selenium, JUnit, TestNG, and Cypress, emphasizing familiarity with both front-end and back-end testing tools. Discuss specific projects where these frameworks improved test coverage, reduced manual effort, and accelerated deployment cycles, aligning with Raymond James Financial's commitment to robust financial software solutions. Mention understanding of integrating these tools into CI/CD pipelines using Jenkins or GitLab to ensure continuous quality assurance.

Do's

• Selenium WebDriver - Highlight experience with Selenium WebDriver for web application automation and cross-browser testing.
• JUnit/TestNG - Mention usage of frameworks like JUnit or TestNG to write structured and maintainable test cases.
• CI/CD Integration - Explain how automated tests were integrated into CI/CD pipelines for continuous testing and deployment.

Don'ts

• Generic Answers - Avoid vague statements like "I have used many frameworks" without specifics.
• Overstating Experience - Do not claim proficiency in frameworks you have not used extensively or practically.
• Ignoring Business Context - Avoid neglecting how automated testing supports financial software reliability and security requirements.

How do you stay updated on new technologies?

Demonstrating continuous learning aligns well with Raymond James Financial's commitment to innovation in software development. Mention specific methods such as following industry-leading tech blogs, participating in online courses on platforms like Coursera or Udemy, and engaging in developer communities like GitHub or Stack Overflow. Highlight attending webinars, tech conferences, or internal company workshops to stay current with emerging technologies relevant to financial software solutions.

Do's

• Industry Blogs - Regularly read reputable technology blogs to stay informed about the latest software development trends and tools.
• Online Courses - Engage in continuous learning through platforms like Coursera, Udemy, or LinkedIn Learning to enhance technical skills.
• Networking - Participate in professional communities, forums, and meetups to exchange knowledge and stay aware of emerging technologies relevant to financial software development.

Don'ts

• Generic Answers - Avoid vague responses like "I just Google it" without providing specific sources or methods of learning.
• Overloading - Do not claim to know every new technology; instead, focus on relevant and recent advancements applicable to the role.
• Neglecting Practical Application - Avoid mentioning only theoretical learning without demonstrating how you apply new knowledge in projects or work scenarios.

What are your salary expectations?

Research average software developer salaries at Raymond James Financial to provide a well-informed, competitive salary range based on your experience and skills. Emphasize flexibility by expressing your willingness to negotiate while highlighting that your expectations align with market standards and the company's compensation framework. Focus on demonstrating how your expertise and contributions justify the expected salary, ensuring a value-driven conversation.

Do's

• Research market salary - Understand the average salary range for software developers at Raymond James Financial and similar companies.
• Provide a salary range - Offer a realistic and flexible salary range based on your research and experience level.
• Focus on value - Emphasize your skills, experience, and how they contribute to the company's success before discussing numbers.

Don'ts

• Give a fixed salary number - Avoid stating a single figure without flexibility to negotiate.
• Disclose current salary first - Don't reveal your current or previous salary unless prompted or necessary.
• Undervalue yourself - Avoid quoting a salary range significantly below industry standards or your worth.

Do you have experience working in the financial industry, or with financial applications?

Highlight any direct experience with financial institutions, trading platforms, or banking software, emphasizing familiarity with industry standards and regulatory requirements. Mention specific financial applications you have developed or maintained, such as risk assessment tools, portfolio management systems, or payment processing software. Demonstrate understanding of financial concepts like compliance, security, and data integrity, underscoring your ability to deliver robust solutions aligned with Raymond James Financial's goals.

Do's

• Highlight Relevant Experience - Emphasize any previous roles or projects involving financial software development or financial industry knowledge.
• Use Industry Terminology - Reference terms like fintech, risk assessment, trading platforms, or financial APIs to demonstrate domain familiarity.
• Show Problem-Solving Skills - Describe how you tackled challenges specific to financial applications, such as security, scalability, or regulatory compliance.

Don'ts

• Exaggerate Experience - Avoid overstating your financial industry background or claiming expertise you do not possess.
• Ignore Compliance Requirements - Do not neglect mentioning awareness of financial regulations or data privacy standards when discussing your experience.
• Use Vague Statements - Avoid general or non-specific answers; be precise about technologies, frameworks, and financial concepts you've worked with.

Are you familiar with cloud computing platforms? Which ones?

When answering the job interview question about familiarity with cloud computing platforms for a Software Developer role at Raymond James Financial, emphasize specific platforms you have hands-on experience with, such as AWS, Microsoft Azure, or Google Cloud Platform. Highlight your knowledge of cloud services like EC2, S3, Azure DevOps, or Kubernetes, and how you have utilized them in previous projects to improve scalability, security, or deployment efficiency. Demonstrate an understanding of cloud architecture best practices and how your skills align with Raymond James Financial's emphasis on secure, reliable, and compliant financial technology solutions.

Do's

• Be Specific - Clearly name cloud platforms you have experience with, such as AWS, Azure, or Google Cloud Platform.
• Highlight Relevant Skills - Emphasize how your cloud computing experience relates to software development and financial services.
• Show Continuous Learning - Mention any certifications, courses, or projects that demonstrate your commitment to cloud technology proficiency.

Don'ts

• Overstate Experience - Avoid claiming expertise in cloud platforms you have only a basic understanding of.
• Ignore Security Concerns - Do not neglect to mention knowledge of cloud security practices, important for financial companies.
• Be Vague - Avoid generic answers that do not specify which platforms or tools you have used professionally.

Describe your experience with front-end frameworks or libraries.

Highlight your proficiency with front-end frameworks like React, Angular, or Vue, emphasizing projects where you implemented these technologies to enhance user interfaces and application performance. Detail your experience integrating APIs, managing state with tools like Redux or Vuex, and ensuring responsive design across devices. Reference specific accomplishments at Raymond James Financial or similar environments that demonstrate your ability to build scalable, maintainable front-end solutions aligned with industry best practices.

Do's

• React.js - Highlight your proficiency with React, focusing on component-based architecture and state management.
• Responsive Design - Emphasize experience creating responsive user interfaces ensuring cross-device compatibility.
• Performance Optimization - Mention techniques used to improve front-end performance such as lazy loading and code splitting.

Don'ts

• Overgeneralizing Experience - Avoid vague statements without concrete examples of frameworks or projects.
• Ignoring Testing Practices - Do not neglect mentioning front-end testing tools like Jest or Enzyme if applicable.
• Neglecting Security - Avoid overlooking secure coding practices related to front-end development.

Have you used CI/CD pipelines? Explain your role.

Demonstrate your experience with Continuous Integration/Continuous Deployment (CI/CD) by detailing specific tools like Jenkins, GitLab CI, or CircleCI you have used. Highlight your role in designing, implementing, or maintaining pipeline stages such as code integration, automated testing, and deployment to ensure rapid and reliable releases. Emphasize collaboration with development and operations teams to streamline workflows and improve software delivery efficiency, which aligns with Raymond James Financial's commitment to robust and secure financial technology solutions.

Do's

• CI/CD pipelines - Clearly describe your experience designing, implementing, or maintaining continuous integration and continuous delivery pipelines.
• Role clarity - Explain your specific responsibilities, such as configuring build tools or automating deployment stages.
• Tools and technologies - Mention tools like Jenkins, GitLab CI, or Azure DevOps to demonstrate hands-on knowledge.

Don'ts

• Vague answers - Avoid generic statements without specifying your contributions to CI/CD processes.
• Technical jargon overload - Do not overwhelm with unexplained technical terms that may confuse the interviewer.
• Ignoring security - Avoid neglecting to mention best practices in secure pipeline implementations.

What questions do you have for us?

When asked "What questions do you have for us?" during a software developer interview at Raymond James Financial, focus on inquiries that demonstrate your interest in the company's technology stack, development processes, and team dynamics. Ask about the primary programming languages and development frameworks used, how the software development lifecycle is managed, and opportunities for professional growth within their technology teams. Inquire about Raymond James' approach to incorporating emerging technologies in financial software solutions and the company's commitment to fostering innovation.

Do's

• Company Culture -Ask about the team dynamics and core values at Raymond James Financial.
• Project Involvement -Inquire about the current or upcoming software development projects you might contribute to.
• Growth Opportunities -Request information on professional development and career advancement options.

Don'ts

• Salary and Benefits -Avoid discussing compensation too early or in a way that seems presumptive.
• Negative Remarks -Do not express doubts or concerns about the company's reputation or past projects.
• Basic Information -Avoid questions that can be answered through simple research on the company website.

More Raymond James Financial Job Interviews