Aller au contenuAller au pied de page
  • Emplois
  • Entreprises
  • Salaires
  • Pour les employeurs

      Boostez votre carrière

      Découvrez votre salaire potentiel, décrochez des emplois de rêve et partagez vos témoignages de manière anonyme.

      employer cover photo
      employer logo
      employer logo

      RTX

      Employeur impliqué

      À propos
      Avis
      Salaires et avantages
      Emplois
      Entretiens
      Entretiens
      Recherches associées: Avis sur RTX | Offres d’emploi chez RTX | Salaires chez RTX | Avantages sociaux chez RTX
      Entretiens chez RTXEntretiens d’embauche pour Software Engineer chez RTXEntretien chez RTX


      Glassdoor

      • À propos
      • Récompenses
      • Blog
      • Nous contacter
      • Guides

      Employeurs

      • Compte employeur gratuit
      • Centre employeur
      • Blog pour les employeurs

      Informations

      • Aide
      • Règles de la communauté
      • Conditions d'utilisation
      • Confidentialité et choix publicitaires
      • Ne pas vendre ni partager mes informations
      • Outil de consentement aux cookies

      Travailler avec nous

      • Annonceurs
      • Carrières
      Télécharger l'application

      • Parcourir par :
      • Entreprises
      • Emplois
      • Lieux

      Copyright © 2008-2026. Glassdoor LLC. « Glassdoor », son logo, « Worklife Pro » et « Bowls » sont des marques déposées de Glassdoor LLC.

      Entreprises suivies

      Tenez-vous au courant des dernières opportunités et profitez de conseils d’initiés en suivant les entreprises de vos rêves.

      Recherche d’emplois

      Obtenez des recommandations et des mises à jour personnalisées en démarrant vos recherches.

      Entretien pour Software Engineer

      1 juin 2015
      Candidat à l'entretien anonyme
      Offre refusée
      Expérience positive
      Entretien moyen

      Candidature

      J'ai postulé via un recruteur. Le processus a pris 2 mois. J'ai passé un entretien chez RTX

      Entretien

      Was contacted by a person doing recruitment, who was interested in some of the work I was doing. We had some email conversations about the research (the person was knowledgeable, so not a standard recruiter, which was nice), and a phone interview with their cybersecurity team lead was arranged, despite knowing that I wasn't a cybersecurity analyst. The phone interview went well, very person person, and of course, it was accepted that I did not know the cybersecurity stuff (my research is useful to cybersecurity people but I am not a cybersecurity person per se). That person decided I wasn't a fit enough, and my contact was frustrated since he was sure my skillset was valuable to them but none of their current reqs fit my set. He set up another phone interview with a different group, and that went well since they were more flexible. They flew me out for a series of interviews with members of the team and the government managers, and apparently I passed, but we couldn't agree on salary. They said they wanted me, so I'm counting that as an offer, but unfortunately, they couldn't pay me an equitable salary. So we parted on good terms. I would recommend this company, these groups doing cybersecurity, to anyone interested. It was a nice group of people, laid back and friendly, and not like the corporate/retail s/w world in my experience, especially since they were more concerned about finding new ways to do things and try new things, not just how to maximize profit or create little mini-empires. :) I wouldn't have hesitated to work for them if we could have agreed on salary, and feel it would have been a great experience.

      Questions d'entretien [1]

      Question 1

      Mainly just a discussion of my research work, but they did ask some of the usual silly coding/architecture questions that one doesn't remember typically unless you just graduated with a C.S degree or are actually doing work in that area. One, how does some function in C that takes any arguments know the type of the passed argument. Two, explain how a browser works.
      1 réponse
      5

      Autres retours d’entretien d’embauche pour un poste comme Software Engineer chez RTX

      Entretien pour Software Engineer

      28 oct. 2025
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience neutre
      Entretien moyen

      Candidature

      J'ai postulé en ligne. Le processus a pris 1 semaine. J'ai passé un entretien chez RTX

      Entretien

      Initial call with hiring manager to talk about my previous experience, fit for the role, job duties, and culture. There was a follow up leetcode style (medium) live coding question.

      Questions d'entretien [1]

      Question 1

      What is your experience with full stack development?
      Répondre à cette question

      Entretien pour Software Engineer I

      19 juin 2025
      Candidat à l'entretien anonyme
      Goleta, CA
      Aucune offre
      Expérience positive
      Entretien facile

      Candidature

      J'ai passé un entretien chez RTX (Goleta, CA)

      Entretien

      Received screening phone call with basic questions. Then, was invited to a Zoom interview with the hiring manager and 2 other software engineers. They asked me mostly behavioral questions and a couple technical questions about C. No leetcode style questions.

      Questions d'entretien [1]

      Question 1

      What's the difference between a heap and a stack?
      Répondre à cette question

      Entretien pour Software Engineer

      8 juin 2025
      Employé (anonyme)
      Offre acceptée
      Expérience positive
      Entretien facile

      Candidature

      J'ai passé un entretien chez RTX

      Entretien

      Fairly easy, just 1 virtual 30 minute interview of some technical questions on tree Data Structure, such as Binary Tree. Other than that, fairly easy questions. Consisted of questions about me and my experience mainly. Then talked about the company itself.

      Questions d'entretien [1]

      Question 1

      Describe on a binary tree which side the child is or something like that.
      Répondre à cette question
      1