GTM Engineer Search

Questions to ask an employer in a GTM engineer interview

Reverse questions are the ones the candidate asks and the employer answers, and in most processes they are the last ten minutes of a round. This page has twenty-six of them in four groups: whether the job is the one the posting describes, whether you could win in it, whether you would still want it in two years, and what the working setup around it looks like. Each question comes with what a considered answer sounds like and what should worry a candidate hearing it. Somebody interviewing for the job can read it to work out what to listen for, and somebody hiring for the job can read it to find out what they would be able to answer.

Questions 26
Question groups 4
Bank version 2026.7

What are reverse questions in a GTM engineer interview?

Near the end of most interviews the person on the other side of the table stops and asks whether you have any questions. Those questions are the reverse round, and they are usually the only part of the process where the candidate finds anything out about the job. Ten minutes is the normal allowance. A company that takes the reverse round seriously will give you a whole conversation for it.

The twenty-six questions below sit in four groups, running in the order a candidate decides things. The first eight ask whether the job is the one the posting describes and whether anybody would notice if it went well, which covers what the role is there to do, who set the priorities it would inherit, and where it sits against the number the company is chasing this year. The next seven ask whether you could win in it, and those come down to conditions: whose approval the work needs, what state the data is in, what has already been tried on the problem, and who else here builds anything. Five ask whether you would still want the job in two years, covering the market the company thinks it is selling into and what the level above this one is called. The last six are about the setup you would be handed in the first week. They cover the tooling budget, warehouse access, who owns the sending domains, and who approves a campaign before it sends.

Each question opens to show three follow-ups, what a company that has thought about the question sounds like, and what should worry you when you hear it. Those last two describe the company's answer, since the company is the one being asked. The short line printed with each question runs the other way. It says what a candidate choosing to ask that question has probably already lived through, and that is the part a hiring manager reads.

This page assumes somebody is already in a process. The five rounds covers what each of the other four settles, and interview prep covers what to prepare for each round, this one included.

When in the process to ask what

Who you are talking to decides which of these questions can be answered at all. A recruiter has never waited on warehouse access or watched a campaign sit in somebody's approval queue, so asking them how long either takes returns something polite and empty, and you have spent one of your questions on it.

  1. 01

    The recruiter screen

    A recruiter can tell you how the process runs, what the salary band is, whether the role is new or a backfill, and how long it has been open. They can also name who you would meet at each stage and say what those people do, which is worth having early because it decides where the rest of your questions go.

    What they cannot tell you is anything about the systems. Ask a recruiter what the team last bought and how long the login took, and you get a line read back from the job description, or an offer to find out and come back to you.

  2. 02

    The hiring manager

    Most of the questions below belong here. The hiring manager is the only person who can tell you what the first project is, who asked for it and how long it has been waiting. They also know where the line sits between a change you could make on your own judgment and one that needs a conversation first.

    Ask them as well what a week in the job would look like, and if somebody held the seat before you, what that person spent their time on. Discount what you hear a little. They are describing the role they are trying to fill, and most hiring managers have never done this job themselves. The people you would work alongside are the next stage, and they see the work from closer up.

  3. 03

    The team you would join

    Take an answer the hiring manager gave you and ask the same question again here. Peers will tell you whether anything gets read before it goes live and which systems nobody wants to open. Where their account and the manager's differ, the gap is usually the thing you most needed to know about.

    Nobody at this stage can commit to anything. A peer cannot widen your mandate or change what you would be paid, so a reassurance offered here will not survive into the offer.

  4. 04

    The final conversation

    The last round is usually with whoever signs off on the hire, and it is the only stage where an answer about the mandate binds anyone. Earlier interviewers can guess at budget, headcount, whose approval you would need and what you would be measured on at six months. This person can settle them. The questions about the market and the risks to the plan belong here too, since this is usually the one person in the process who owns both.

    It is also the last chance to go back to something that troubled you two rounds ago. Saying that an answer you got earlier was vague and asking for a better one is not rude at this point. By now they want you to say yes, so this is the stage where you are most likely to get a straight answer.

Is this job what it says it is, and does it matter?

These eight go first, because their answers decide whether the rest of the process is worth your time. What a company says a GTM engineering job is and what the job turns out to be can differ by quite a lot, and the difference is usually settled before you arrive, by whoever wrote the posting and whoever will be handing you work.

A model will hand anyone twenty good employer questions from a single prompt, so asking a sharp one proves very little about the person asking it. The part that carries information is what the candidate does with the answer, and whether they noticed that it came back with no name in it.

You will not get through twenty-six of these in one conversation. Three or four, each pushed a follow-up deep, is what ten minutes holds. Read the strong and weak answers beforehand so you can tell which one you are getting while you are still in the room. The filter on each of the first three groups marks the level a question is pitched at, so you can narrow to the ones that match the job you are actually interviewing for.

  • 01 Is this role here to fix a specific problem you have right now, or to find the leverage points and own the outcome? Whether they have taken a job whose scope was decided after they started

    Follow up with

    Strong answer

    Both answers describe a real job, and what you want is somebody saying which one this is without hedging between them. A scoped role sounds like a named problem with a person attached to it: inbound leads sit for two days before anybody works them, and the head of sales has been complaining about it since spring. An open mandate sounds different, and a company offering one honestly will tell you who decides what you work on, because somebody has to, and it is usually a weekly conversation with whoever you report to. Either way you want the same thing said out loud: what would count as this role working, from the person who would judge it.

    Weak answer

    An answer that moves between the two depending on which half of the question is being addressed means the scope has not been settled, and it would get settled after you arrive by whoever asks you for something first. Watch for the version that promises a blank sheet of paper. Companies offer it because it is attractive, and a role with no stated problem behind it has nobody waiting for its output, which turns the first six months into a search for somebody who wants what you are building.

  • 02 Are the priorities for the first two quarters already decided, and who decided them? Whether they have inherited a roadmap somebody else wrote

    Follow up with

    Strong answer

    Ask who wrote the list, because the answer decides how much of this job is yours to shape. The useful version comes back with a person and a date, and the person is usually whoever you would report to, working from what sales or marketing has been asking for. Priorities set three months ago that have not moved since are a good sign, because somebody has been holding the line against newer requests. Being told the list is yours to write is also a real answer, as long as they can say who signs it off, since a plan nobody has agreed to is one you defend every week.

    Weak answer

    A list of six things with nothing first tells you the ordering has not happened, and the ordering is the hard part. You would be doing it yourself in your second week, without the standing to make it stick. The other answer to be careful about is a set of priorities that came out of an offsite nobody has revisited since, which usually means the written plan and what people spend their days on have quietly separated.

  • 03 If the thing described in the job posting gets fixed in the first six months, what does this role become? Whether they have watched a role end when its founding problem went away

    Follow up with

    Strong answer

    Roles created to fix one thing routinely outlive the thing, and the answer worth having says what comes next: usually a second system somebody has already asked for, or a shift from building toward running what has been built. The other half of a good answer is who owns the first thing once it works. If that is still you, the job is partly maintenance from month seven onward, and you want to know that before you take it. A company that has hired this way before can point at what happened last time, and one that has not can at least say who would decide.

    Weak answer

    An answer that treats the question as hypothetical means nobody has looked past the immediate pain, and the role has been scoped to the length of one problem. That is survivable at a company growing fast enough to generate the next problem on its own. It is harder where the posting describes the only thing anybody wanted, because once it is done your remit is whatever is left over. Notice too if the answer is that you would move into management. Ask how many people, by when, and whether that has happened for anybody here.

  • 04 Whose requests would I be serving, and would I be able to turn one down? Whether they have worked a service desk under a builder's title

    Follow up with

    Strong answer

    The part that matters most is who breaks a tie when two teams ask for something in the same week, and where that has been settled one name comes back, usually whoever you would report to. You want the teams themselves as well, and where their requests land: a channel, a form, a standing meeting with the head of sales. Then ask what has been turned down recently. A refusal somebody can describe means the role has standing, and the reasoning behind it tells you what this company thinks the job is for.

    Weak answer

    Being told that everyone is a customer and nothing gets refused describes a queue, and the queue gets written by whoever is loudest that week. Ask how requests arrive today, before this role exists. If the answer is direct messages to whoever might be able to help, that is what your first year looks like unless somebody changes it, and changing it is a political job before it is a technical one.

  • 05 What would my first week actually look like, next to what the posting describes? Whether they have joined a company where the posting described somebody else's job

    Follow up with

    Strong answer

    Postings for this role are usually assembled from several people's wishes, and a hiring manager who knows that will tell you which parts are real. The first week they describe should be mostly meetings and access requests, because that is what a first week is, and the lines of the posting they skip over are as informative as the ones they dwell on. Ask who wrote it. Written last month by the hiring manager means the document is close to what somebody actually wants. Assembled by a recruiter from a similar posting elsewhere means you are reading a composite, and the real job is whatever the hiring manager says it is.

    Weak answer

    A hiring manager who recites the posting back to you has either not thought about the first week or would rather not say. Press for a day: who you would sit with, what you would be given access to, what would already be waiting. Vagueness here predicts vagueness in month two, because the same person would be deciding what you work on. The answer that should worry you is a first week that includes shipping something, since nobody builds anything useful before they know where the data lives.

  • 06 Who would this role report to, and what made that the right team for it? Whether they have been reorganised into a team that did not want them

    Follow up with

    Strong answer

    Press for the reasoning behind the placement. Where this role reports decides what you spend your time on, and the two common homes pull in different directions. Under revops, the CRM and the reporting model are usually yours and outbound sending belongs to somebody else. Under a sales org, sending and sequences come to you and the reporting model stays elsewhere. A company that considered two homes for the role and can say why it chose one has thought about the job. If the placement was argued about, ask who lost, because that person still has requests and would now be routing them through your manager.

    Weak answer

    When nobody can say why the role sits where it does, it usually landed there because a particular manager had headcount that quarter. That is not fatal, and it does mean your work gets shaped by that team's number whatever the posting says. Watch for a dotted line to a second leader. Two managers measured on different numbers is how a role ends up doing two half jobs, and the person resolving the conflict every week is you.

  • 07 Why is this the right moment for this role? If it is your first one, what changed? Whether they have joined a role that existed because competitors had one

    Follow up with

    Strong answer

    A company that decided this on purpose can tell you what changed, and the change is usually specific: outbound stopped working at the volume two people could sustain by hand, or a migration left the CRM in a state nobody can report off. Whoever argued for the headcount should have a name, and the case they made should be one you can repeat back afterwards. The strongest version includes what the company tried before deciding it needed a person, because a role that follows two failed attempts at the same problem has a real problem behind it, and you would want to know why the attempts failed.

    Weak answer

    Hearing that GTM engineering is where the industry is going, with nothing about this company in the answer, means the role was copied from other companies' postings. Roles like that get cut first when hiring slows, because nobody internally depends on the output. Ask what would happen to the role if the person who pushed for it left. If somebody would have to make the case again, the role belongs to one person's conviction and not to the company.

  • 08 What is the goal the whole company is working towards this year, and where does this role sit against it? Whether they have shipped work that never appeared in anybody's report

    Follow up with

    Strong answer

    Ask somebody to walk you from what you would build to the company's number, and count the steps. The length of that chain decides whether your work gets protected when budgets tighten. A short chain sounds like this: the company needs a stated amount of new pipeline, most of it is meant to come from outbound, and outbound cannot get there at the current reply rate without the systems this role would build. They should get through it without pausing. Ask who reports the number and whether anything you would build shows up in their report, because a contribution nobody reports is one you argue for at review time.

    Weak answer

    When the company goal and this role sit in separate halves of the answer with nothing joining them, the role is a support function whatever the title says, and that shows up later as work nobody notices until it breaks. Also worth catching is a goal stated as growth with no figure attached. Ask what the figure is. A hiring manager who does not know the number their own team is measured on cannot tell you what would count as you doing well.

Can I win in it?

These seven ask what the job would be like to actually do. A mandate can be real and well scoped and still be undoable here, usually because the accounts and contacts are spread across systems nobody has reconciled, or because every change of the kind this role would make needs sign-off from somebody in another org who has never heard of the job. Somebody in the room can tell you both of those things now, and finding them out in your second month is expensive.

Ask these of the hiring manager, then ask the same ones again of the people you would sit with. Where the two accounts differ, that gap is usually the part of the job nobody has settled, and it is the part you would spend your first quarter on.

  • 09 What would have to be true for this role to work here? Whether they have taken a mandate that was impossible from the start

    Follow up with

    Strong answer

    Conditions are the substance of a good answer here, and the real ones are concrete: warehouse access inside the first month, a head of sales willing to let their team's process change, budget for the tools the work needs. What you most want to hear next is which of those hold today. Somebody honest will admit that one does not and name who is working on it, which is worth more to you than a list of conditions that have all conveniently been met, because it tells you they have actually looked.

    Weak answer

    An answer that lists only what you would have to do puts every condition on your side of the table, and no role works on that basis. The conditions that decide this one are the company's: whether the data is in a usable state, and whether the teams whose process you would change have agreed that it should change. Watch for a condition with nobody's name on it. A dependency nobody holds stays undone, and you would find out which ones those were during your first project.

  • 10 How would you define success for this role at twelve months, given how new the role is? Whether they have been reviewed against a standard invented after they joined

    Follow up with

    Strong answer

    Push for something that could be checked by somebody other than your manager. A definition worth having names an outcome and a way of seeing it: outbound producing a stated number of meetings a month without two people running it by hand, or a reporting model the sales leadership uses in its own forecast meeting. Ask who else would have to agree. Where success is defined by your manager alone, a new stakeholder can redefine it in month eight. A company that has written the definition into this role's first review has a bar that exists independently of whoever is in a good mood.

    Weak answer

    Impact and being a force multiplier are things anybody could say about any hire, and they leave the standard to be invented later, usually while you are being measured against it. Press until you get something you could point at. Be careful too with a definition made entirely of activity, like a count of systems shipped. That measures how busy you were, and a year of it can end with a manager who cannot say whether the role paid for itself.

  • 11 Whose approval would this work need, and what has stalled waiting for it? Whether they have had a finished build sit unshipped for a month

    Follow up with

    Strong answer

    Two or three people usually hold a veto over GTM work: whoever owns the CRM, whoever owns security, and whoever owns the mail going out under the company's name. A company that knows its own approvals names them without thinking, and can say what waited recently and for how long. The number matters. A week is a working process, and a quarter means approval is a queue somebody has to be chased through. Ask who unblocked it in the end, because a stall that had to be escalated to a VP tells you the ordinary route did not work.

    Weak answer

    Full autonomy, offered without a single name attached, describes an intention. The approvals still exist, because every GTM system touches customer data and somebody owns the rules about that, and if nobody in the room can say who, you would meet them by tripping over them in your first month. The other thing to catch is a story about something that stalled where nobody says how it ended. Ask directly whether it ever shipped. Sometimes it did not, and the person telling you had stopped following it.

  • 12 Is the data in a state where this work is possible? Whether they have spent a first quarter cleaning up before building anything

    Follow up with

    Strong answer

    Expect an admission, and treat a specific one as good news. Nobody's data is clean, so what you want is where the mess sits: duplicate accounts because the CRM has no matching rule, a lifecycle field three teams write into, contact records that stop being updated after the first sale. A company that has looked will also say whether there is a warehouse and what is in it, since querying the CRM directly and querying a modelled copy of it are different jobs, and which of the two you would be doing decides what you could build in your first quarter. Ask what somebody recently could not build. That answer names the actual constraint.

    Weak answer

    Being told the data is in good shape, by somebody who does not work in it daily, is a description of the CRM's front end. Ask who does work in it, and whether you could speak to that person before you decide. The answer that should slow you down is a company midway through a migration, where the records exist in two systems and neither is authoritative yet. That work has to finish before anything built on top of it can be trusted, and finishing it would become your job.

  • 13 What has been tried on this problem already, and why did it not stick? Whether they have rebuilt something that had already failed twice

    Follow up with

    Strong answer

    A company that has been living with this problem has tried something, usually an agency, a tool bought and abandoned, or a rep who built a version of it in a spreadsheet. Naming the attempt and saying plainly why it stopped working is the answer you want, and the reason is often that nobody owned it once the person who built it moved on. Ask what is left over. Half-built systems still running are a real part of this job, and hearing about them now beats discovering them in week three. The best version includes what they would do differently, which tells you what they have concluded about the problem.

    Weak answer

    Hearing that nothing has been tried usually means the problem is newer than the posting suggests, or that people have been living with it and nobody has been asked to fix it. Ask how long people have been complaining about it. A long-standing complaint with no attempt behind it means something has been stopping people, and whatever that is would still be there for you. The other answer to press on blames the tool. Tools do not fail on their own, and the part left out is usually who was meant to maintain it.

  • 14 Who else here builds things, and would this role be on its own? Whether they have been the only technical person on a GTM team

    Follow up with

    Strong answer

    Ask for names and what each of those people owns. A useful answer puts this role next to the people already here: a data engineer who owns the warehouse models, a marketing ops person who owns the email platform, an engineer you can ask when an API stops behaving. Being the only builder is a real job worth taking with open eyes, and in that case what you want is who you escalate to outside the team. A named person in data or engineering means somebody has already worked out where the edge of this role sits.

    Weak answer

    When the answer is that everybody here is technical, ask what the last thing each of them built was. Companies count people who can use a low-code tool as builders, and those people will not help you when a sync fails at two in the morning. The harder answer is that nobody reviews anything because nobody else understands the systems. That holds while you are careful, and it means the first person to catch your mistake is whoever sits downstream of it, usually a rep already talking to a customer.

  • 15 Which teams would I be building for that I do not report to, and who among them would I not meet in this process? Whether they have been hired into a role three teams had different plans for

    Follow up with

    Strong answer

    This role serves sales, marketing, revops, product marketing and finance without reporting to any of them, so a hiring manager who has thought about it can list those people by name and say what each of them would want from you. The answer that tells you most is which of them did not want the role, since somebody usually preferred the headcount go elsewhere and you would be working with them anyway. A company comfortable with all this will offer to put one of them on a call.

    Weak answer

    A list that stops at the hiring manager and the immediate team means nobody has mapped who this role actually works with, and you would be introducing yourself to those people while asking them to change something. Being told you will meet everyone once you start is the ordinary answer and worth pushing on once. If a request to speak to somebody in marketing or finance gets deflected, take the deflection as information: either the relationship is unsettled internally, or the company would rather you did not ask that person how the work has been going.

Do I want it in two years?

Five questions about the job two years in, when whatever you were hired to build is running and what keeps you there is the company around it. They cover what the company understands about the market it sells into, the biggest risk to its plan, what the level above this one is called and whether anybody holds it, whether anybody else here does this job and what became of the ones who did, and what gets cut if the number is missed two quarters running.

Most of these need somebody who holds the plan, which usually means the final conversation. They are also the questions a company is least used to being asked, so ask them slowly and give the person room to answer at length.

  • 16 What does your team understand about this market that your competitors do not, and how should that change the way you go to market? Whether they have written outbound for a company with no view of its market

    Follow up with

    Strong answer

    The answer you want is about buyers, and a good one is specific enough to be wrong: the people who buy this are operations leads at companies that have just raised, they come looking after a failed internal build, and they will not read a case study from a company larger than theirs. A team holding a view like that can show you where it lands in the targeting and the sequences. Ask what they learned in the last year that they did not know before, since a thesis that has not moved in two years is one nobody has tested. Somebody disagreeing internally is healthy, and worth asking about.

    Weak answer

    Most companies answer this with their product, listing features and the segments they sell into. That describes what they built and leaves you knowing nothing about how they read the market, so ask again in terms of who buys and why. The harder answer to sit with is a thesis stated confidently that nobody can point to in the outbound. Where the sequences going out today do not reflect the view being described, either the view is new or it is decoration, and your work would sit downstream of whichever it turns out to be.

  • 17 What is the biggest opportunity in your go-to-market right now, and what is the biggest risk to it? Whether they have watched a plan fail on a risk everybody already knew about

    Follow up with

    Strong answer

    Most leaders answer the opportunity half comfortably, so the risk half is where the information is. A company being straight with you names something uncomfortable: a single channel producing most of the pipeline, a competitor winning on price in a segment they used to own, a renewal base thinning out. Ask how long they have known and who is working on it. A risk with a named owner and a date has been discussed by the people who could act on it. A risk stated for the first time in your interview is one you would be walking into and then helping to explain.

    Weak answer

    Execution as the only named risk says nothing, because that is the risk at every company in every quarter. Ask what specifically has not been executed, and by whom. Be careful too with an opportunity that turns out to be a market size figure from an analyst report. That number is not a plan, and it usually surfaces where nobody has worked out which customers to go after first, which would make choosing them part of your job before you build anything.

  • 18 What does progression look like for a GTM engineer here? Whether they have hit a ceiling nobody mentioned when they joined

    Follow up with

    Strong answer

    Listen for whether a level above this one exists at all, because at most companies it does not yet. Where one does, expect it named and placed: a senior version of the same job with wider scope, a move into revops or marketing ops leadership, or a path into engineering. Naming the person who holds the next title, where there is one, is the strongest form of the answer. Where nothing exists yet, the honest version is that the ladder would get built around whoever does the job well, and a company saying that should also say who would build it and when it gets written down.

    Weak answer

    Growing with the company means nothing on its own, and it is the most common answer to this question. Ask what the next title is called and whether anybody currently holds it. The version worth noticing is a company where progression for this role means becoming a manager. That is a different job, and if it is the only route up, somebody who wants to keep building has a ceiling here that nobody will mention until their third year.

  • 19 Are there other GTM engineers here, and what happened to the ones who came before? Whether they have taken a role that had already broken two people

    Follow up with

    Strong answer

    Tenure is what to weigh here. Whether there are others already or this would be the first, either answer is fine as long as it comes back direct. Where two or three people already do this work, somebody can tell you how it is split between them and who has been there longest. A company hiring its first can say who has been absorbing the work in the meantime, usually a rep or a marketer doing by hand what should run on its own, and roughly what that costs them each week. If somebody has left, ask where they went and how long they stayed. Eighteen months and then a bigger version of the same job elsewhere is ordinary. Two people leaving inside a year is a pattern, and a company that has noticed will say what it concluded.

    Weak answer

    Vagueness about where a previous person went is worth one gentle follow-up. People leave for ordinary reasons, and a company comfortable with the reason will say it. The answer that should register is a role that has been open or refilled repeatedly, which usually means the job as designed cannot be done: too many stakeholders, no authority, or a manager who wanted an engineer and had budget for an analyst. Ask what they changed about the role after the last person left. If nothing about it changed, the conditions that ended it are still in place.

  • 20 What changes if you miss the number two quarters running? Whether they have been through a hiring freeze from inside a new role

    Follow up with

    Strong answer

    A company that has been through a miss will tell you what it cut and in what order: hiring paused, a channel dropped, a segment abandoned. That order is the part to listen for, because a miss reaches this role through the tooling budget before it reaches anything else. Runway is fair to ask about at any company that has raised, and a finance-literate hiring manager will give you a rough number of months and say what the next raise depends on. Being told plainly that tooling spend goes first is worth having, because it lets you work out now what you would still be able to build without it.

    Weak answer

    An answer built on how confident everybody is about the plan avoids the question, and the question is what happens when the confidence turns out to have been misplaced. Ask it again in the past tense: when did you last miss, and what happened afterwards. A company that has never missed is either young or is not telling you. Watch also for a hiring manager who does not know the runway. That is normal at a large company and unusual at a startup, and at a startup it means they are not in the conversations where this role's budget gets decided.

What the work setup looks like

The last six ask what you would be handed in your first week. Several of the questions above can only be answered in the future tense, because the job itself does not exist yet. These six always have a history at a company that has been selling for a while, so the answers come back with a date and a name in them: how long the last person who needed warehouse access waited for it, what the team last bought and how long they waited for a login, what the approver changed on the last campaign that went out. An answer to one of these that arrives with no name in it is worth a follow-up before you move on.

Four of the six only make sense against a particular kind of system, and the filter narrows to those: one each for the warehouse, the sending domains, the campaign platform and the reporting. The other two, the tooling budget and where a model already runs with nobody reading its output, are worth asking whatever this role turns out to cover.

  • 21 What was the last piece of GTM tooling this team bought, and how long was it between somebody asking and having a login? Whether they treat the tooling budget as part of the mandate

    Follow up with

    Strong answer

    Several weeks between somebody asking for a tool and somebody having a login is ordinary. A few days for anything under a certain figure means the company has a spending threshold, and that figure is worth asking for outright. The name of the tool and the person who pushed for it should both arrive without prompting. Ask what has been turned down, because an answer means somebody is genuinely deciding, and the reasoning tells you how this company weighs a licence fee against your hours. Ask whose budget it came out of as well. A tool paid for on marketing's line means marketing has a say in what you build on.

    Weak answer

    An answer that stays at the level of procurement and vendor review, with no recent purchase in it, usually means nothing has been bought in a while. Ask when the last one was. If it turns out that everything gets built in-house because approvals are slow, you are being told that the first months of your tooling budget would be your own time.

  • 22 How long did the last person who needed warehouse access wait for it? Whether they have spent a first month waiting on credentials

    Follow up with

    Strong answer

    You want a number in days and the name of whoever granted it. Two weeks is ordinary at a company with a real security review, and two days means somebody has made this routine. Ask what the person had to justify, since that tells you whether access here is a form to fill in or an argument to win. Then ask what they can query and what is walled off. Contract values and anything personal are commonly restricted, and a team that can say where the wall sits has settled the question in advance, so you would not be negotiating it during your first project.

    Weak answer

    Hearing that nobody has needed access recently usually means this team works from exports somebody else runs for them, and you would be waiting on that person every time a question changes shape. If the wait is measured in months, ask what people do in the meantime. The usual answer is a spreadsheet from a friendly analyst, which is how a company ends up with several versions of the same number. Be careful with a promise that you will be set up on day one when nobody in the room can point at the last time that happened.

  • 23 Who owns the sending domains, and what happened the last time one was burned? Whether they treat sending infrastructure as theirs to own

    Follow up with

    Strong answer

    Sending and DNS usually sit with different teams, so there should be two names in this answer. Ask how long the last DNS change took. A day means somebody has a working relationship with whoever holds the registrar login, and three weeks means every new sending domain has to be booked in advance against another team's queue. A company doing this properly also knows how many domains are live and what became of the ones it retired, whether they were parked or left to cool off.

    Weak answer

    Nobody being able to say who controls DNS is more common than it sounds, and it means your first sending change waits on a hunt for the registrar login. The specific version worth asking about is a set of domains an agency bought during a contract that has ended, on an account nobody can reach. Also catch a company sending cold mail from the domain its employees use for everything else. That has held up because the volume is low, and raising the volume is probably your first assignment.

  • 24 Who approved the last campaign that went out, and what did they change before it sent? Whether they have had a send held for a week by one calendar

    Follow up with

    Strong answer

    Expect a name, and expect an actual edit to go with it. Copy changes are the common ones. An edit to the audience means somebody looked at who was about to receive the mail before it went. Ask how long the approval took. Two days is a working process, and a week means sends get scheduled around one person's availability. The other half of this is who can send with no approval at all. Lifecycle triggers and transactional mail usually sit outside that review. Ask where a one-off campaign to a small list falls, since that is the case the rule tends not to cover.

    Weak answer

    If the approver has never stopped a send, the step is costing days and catching nothing, and every campaign waits on it anyway. The reverse of that is just as common. Anybody can send to anybody, nothing has gone wrong yet, and the first bad send would be traced to whoever built the audience. Ask what has been stopped at that step. A company that cannot name one thing either has no review, or has a reviewer who approves everything that reaches them.

  • 25 Which reported number did people last disagree about, and how did that get settled? Whether they have built a report that two teams rejected

    Follow up with

    Strong answer

    Pipeline created and anything with attribution in it are where these arguments usually begin, so expect one of those. A company where reporting carries weight will give you the number and both readings of it without much prompting. What matters most is how it ended, which at best is one definition winning, getting written down, and the reports rebuilt to match. Ask whether anybody still keeps a private version in a spreadsheet. The answer is often yes, and a company willing to say so is telling you where the next one will come from.

    Weak answer

    When nobody can remember an argument about a number, either the dashboards are not being used for decisions or the disagreements happen in rooms you have not sat in. Ask who prepares the numbers the board sees and whether those come from the same place as the dashboards. An argument settled by seniority is worth noticing too, since the definition that won has nothing holding it in place and gets reopened the next time it produces an unwelcome figure.

  • 26 Where does a model already run here without anybody reading its output, and when was one of those last wrong? Whether they have owned a model whose mistakes reached a customer

    Follow up with

    Strong answer

    Ask for a system by name, and expect one of two: a column that scores leads, or the first line of an email written per lead. Find out which of them a person reads before it goes anywhere. Keep going until you get something a model got wrong, most often a claim about a company that turned out to be false and a rep who caught it. Then ask what changed afterwards. If there is now a sample somebody reads each week, or a rule that certain output never goes out unread, this team acted on what it found.

    Weak answer

    An answer about using AI across the business, with no system named, means nobody has drawn a boundary and drawing it would fall to you. Be careful with the claim that nothing a model produced has ever been wrong. At any real volume that means nobody has sampled the output, since a wrong answer that reaches no one's desk leaves no trace. Test the opposite claim too, that a person reviews everything. Ask how many items a day that is and whether the reviewer has ever sent one back.

The round you are not running

Four of the five rounds are built to find out about the candidate. In the last ten minutes of each one the direction reverses and the candidate finds out about you. Most companies have prepared nothing for that stretch. There is a scorecard for the case study and a rubric for the technical round, and then somebody asks whether the candidate has any questions, and what comes back is whatever that interviewer happens to know.

The candidate is grading the same thing you are. Nearly every question on this page has an answer with a name in it: who set the priorities, whose approval the work would need, who argued for the headcount in the first place. An answer carrying no name at all is the kind you would mark down yourself in a behavioral round. When a candidate tells you their last team really valued quality, you write down that the answer had nothing in it. When you tell a candidate that engineering and GTM work closely together here, they are writing down the same thing about you.

Preparing for this is short work. Before the round, pick the two or three things a candidate is most likely to ask about, which for this role are usually what the job becomes once the first project ships and who has to approve the work before it goes live. Make sure whoever is in the room can answer each of them with a name attached.

For the candidate reading this, a bad answer is not by itself a bad company. Somewhere good to work can still answer these questions poorly, because the person sitting in front of you may have joined after whatever the question is asking about, or may never have been told how it turned out, and some of the best managers are three months into the job themselves. A vague answer is a reason to ask who would know and then to go and ask them, rather than a reason to leave the process.

That an interviewer may simply not know is also worth something to the company. When nobody in the room knows the answer, say so and offer to find out. It costs nothing, and the paragraph you would otherwise improvise is the exact thing this page is teaching candidates to mark down.

Frequently asked questions

What questions should a GTM engineer ask an employer?

Start with what the job is: whether the role exists to fix a named problem the company already has or to decide for itself where the work goes, who set the priorities for its first two quarters, and what it becomes once the thing in the posting is fixed. Then ask what would make it doable, which means whose approval the work needs, what state the customer data is in, and what has been tried on the problem already. Ask what the culture is like and you get the answer everyone else got.

Does it count against you to have no questions?

It does, though less than candidates fear. An interviewer who has spent an hour asking about your work reads an empty ten minutes as either indifference or exhaustion and cannot tell which. If the conversation genuinely covered everything, say which part of it covered what you came in wanting to ask. That lands better than a question invented on the spot.

How many questions should you ask in an interview?

Three or four in a ten-minute slot, with a follow-up on each. Pushing one question two levels down tells you more than working through a list of eight, because the first answer to anything is the prepared one. Bring more than you plan to use, since some of them get answered during the interview itself.

What do a candidate's questions tell the hiring manager?

What they have already been through, though hold that loosely. Somebody who asks whose approval the work needs has usually watched a finished build sit unshipped for a month, and somebody who asks whether anybody has held this job here before them has usually taken a role that had already worn two people out. These questions are easy enough to copy off a page like this one, so the tell is really in the follow-up they ask once you have answered. None of it says whether they can build anything.

Next step

Hiring a GTM engineer?

Are you a GTM engineer?

Get on the radar