Research vs Engineering Preference, Technical Likes and Dislikes, and On-Call Experience

A one-hour technical screen for an experienced-hire engineering role on a hedge fund's treasury engineering team opened with about 15 minutes of background conversation before the coding exercise. The interviewer asked three questions: 1. Do you prefer research or engineering? 2. From a technical point of view, what do you like most and least about your current work? 3. Do you take part in production support? Do you have on-call duties? Answer each one as you would in that opening segment. ### Clarifying Questions - Is "research" meant as quantitative or scientific research next to the business, or as exploratory technical work inside engineering? - How much of the role is production support, and is there a formal on-call rotation? - How much detail does the interviewer want in a segment shared by three questions? ### Part 1 — Research or engineering Do you prefer research or engineering? Explain your preference. ```hint Evidence over adjectives Ground the preference in specific work you have done and in what you would actually do in this role, and say what you value in the side you did not pick. ``` #### What This Part Should Cover - A clear preference instead of a hedge, with the reason behind it - Evidence from concrete past work - How the preference fits an engineering role that works next to research and business users - Respect for, and some fluency in, the other side ### Part 2 — What you like most and least, technically From a technical point of view, what do you like most and least about your current work? ```hint A dislike you acted on Pick a dislike that is real and technical, and be ready to say what you did about it, not just what bothers you. ``` #### What This Part Should Cover - Specific technical content: systems, problems, tools or practices, not "the people" or "the culture" - A dislike framed constructively, with an action you took or proposed - No blame aimed at a current employer or colleagues - A link between what you like and what this role offers ### Part 3 — Production support and on-call Do you take part in production support, and do you have on-call duties? ```hint Have one incident ready Prepare one real incident: how you learned about it, what you did first, how it was resolved, and what changed afterwards. ``` #### What This Part Should Cover - An honest description of current support and on-call responsibilities, including if there are none - One concrete incident told with situation, actions, result and follow-up - Prevention habits: monitoring, alerts, runbooks, post-incident reviews - The attitude toward owning production systems that the business depends on ### What a Strong Answer Covers - Concise answers that leave time for the coding exercise - Answers that are consistent with one another and with the résumé - Concrete examples instead of generic claims - Honesty about gaps, paired with evidence of comparable ownership - Signals of fit for an engineering team whose systems support daily business operations ### Follow-up Questions - What is the hardest production issue you have debugged, and how did you find the root cause? - Tell me about a time you had to choose between a quick fix in production and a proper fix. - If you had a month to change the thing you like least about your current work, what would you do? - How do you balance feature work against support duties when both are urgent?