candidate_questions / art_zsa4BdyZOtw
Interviewer
Dana Rafferty is a Technical Recruiter II at Box, based in Austin, Texas, with over 5 years of tenure at the company. She started as a Recruiting Coordinator in July 2021, progressed through a Sales Recruiter temporary assignment, Recruiting Coordinator III, and Technical Recruiter I before reaching her current Technical Recruiter II role as of April 2026. Her background blends digital marketing, graphic design, and recruiting coordination, and she is also a co-founder of Friend of a Friend, LLC. As a recruiter, Dana's interview focus will likely center on cultural fit, Box's values, candidate experience, working style, and career motivations rather than deep technical or product strategy topics. There is limited direct overlap between Dana's background and Felix's technical profile, though both have entrepreneurial streaks — Felix as a multi-time founder and Dana as a co-founder of her own LLC.
Questions to ask them (19)
| category | question | why |
|---|---|---|
| interviewer_experience | You've been at Box for over five years and have grown through several different roles — from Recruiting Coordinator to Technical Recruiter. What's kept you energized and growing here, and what does that trajectory tell you about how Box invests in its people? | Anchors the question in Dana's visible career arc at Box, signals genuine curiosity about retention and development culture, and invites her to share what she values about the company — useful intel for evaluating the role. |
| interviewer_experience | You made the jump from a more coordination-focused role into technical recruiting, which is a meaningful shift. What did Box do to support that transition, and what did you have to go figure out on your own? | Draws directly from her profile progression and surfaces honest insight into how Box handles internal growth — relevant for a candidate evaluating whether the company invests in people who want to stretch. |
| interviewer_experience | You've recruited across sales and technical roles at Box. From your vantage point across many hiring cycles, what do you consistently see in the candidates who thrive here versus those who struggle to find their footing? | Leverages Dana's unique cross-functional recruiting lens to surface unwritten cultural and performance signals that won't appear in the job description. |
| role_team_dynamics | This role sits at the intersection of partnerships, product thinking, and technical solutioning — which is a pretty wide mandate. How is the AI Partnerships function currently structured, and who would this role work most closely with day to day? | Clarifies reporting lines, team size, and cross-functional dependencies — critical for understanding whether this is a solo builder role or part of a larger partnerships org. |
| role_team_dynamics | What does success look like at 30, 60, and 90 days for this role? Are there specific partner relationships or ecosystem milestones the team is already tracking toward? | Signals strategic preparation and helps the candidate understand whether there's a defined ramp plan or whether they'd be building the playbook from scratch. |
| role_team_dynamics | The job description mentions this person will act as 'one of the more technical members of the business development team.' How technical is the current BD team, and where does the expectation for technical depth actually come from in practice — product, engineering, or partners themselves? | Surfaces the real technical bar and helps calibrate whether Felix's depth would be an asset or potentially misaligned with the team's current operating mode. |
| role_team_dynamics | Is this a backfill, or is Box expanding the AI Partnerships function? Understanding the origin of the role helps me think about what's already been built versus what's greenfield. | Directly informs whether there's an existing playbook, inherited relationships, or a true 0-to-1 build — a meaningful difference in how to position and evaluate the opportunity. |
| technical_environment | From a platform perspective, how mature is Box's developer and partner ecosystem today — are there established APIs, SDKs, and integration patterns that partners are already building on, or is part of this role helping define what 'building on Box' even means for AI-native companies? | Felix has deep SDK and developer platform experience from Intuit; this question signals that fluency and probes whether the role is evangelizing an existing platform or helping architect the partner experience. |
| technical_environment | When you're recruiting for technical roles at Box, what tools and workflows does the engineering and product org seem most invested in right now — especially on the AI side? I'm curious what the internal stack signals about where Box is placing its biggest technical bets. | Dana has unique visibility into what engineering and product teams are hiring for, which is a proxy for technical direction — a creative way to gather signal from a recruiter that a hiring manager might not share directly. |
| technical_environment | How does Box think about the boundary between what partners build on top of Box versus what Box builds natively? Is there a clear platform philosophy, or is that something this role would help shape? | Gets at a fundamental product strategy question that directly affects how the AI Partnerships role would operate and what 'winning' looks like. |
| culture_working_style | Box requires three days a week in office, and this role is based in Redwood City. From what you've seen recruiting for the team, how does the in-person culture actually manifest — is it collaborative and energizing, or more of a compliance checkbox? | Dana has firsthand visibility into how Boxers describe their in-office experience across many hiring conversations — this gets at real culture rather than the polished version. |
| culture_working_style | Partnerships roles often require pushing internally to get product or engineering prioritization for a partner's needs. How does Box's culture handle internal advocacy and constructive tension between teams — is that kind of friction welcomed or does it create friction? | Surfaces how Box handles internal conflict and advocacy, which is critical for someone who will need to champion partner needs against competing internal priorities. |
| culture_working_style | Box describes itself as an 'AI-first company' in the job description. From your recruiting conversations with candidates and hiring managers, what does that actually mean in practice for how people work day to day — not just the marketing version? | Dana hears the unfiltered version of this from both sides of the hiring table; this question invites her honest read on whether 'AI-first' is cultural reality or aspirational branding. |
| growth_development | Your own path at Box shows real upward mobility — you've grown through five distinct roles in five years. Is that kind of internal growth trajectory common across the company, or is it more the exception? | Anchors the question in Dana's own story, making it personal and genuine, while gathering honest signal about whether Box is a place where ambitious people actually advance. |
| growth_development | For someone coming into this AI Partnerships role with a strong technical and product background, what would the natural next chapter look like at Box — is there a defined growth path, or does it depend heavily on what the person carves out? | Signals long-term ambition and helps evaluate whether Box has a structured career ladder for this function or whether growth is self-directed. |
| strategy_vision | Box is positioning itself as the platform for AI-native companies to build on. From what you're seeing in the types of roles Box is hiring for right now, where does the company seem to be doubling down most aggressively in the AI ecosystem? | Dana's hiring pipeline is a leading indicator of strategic investment — this question extracts forward-looking signal from a recruiter's unique vantage point. |
| strategy_vision | The role mentions identifying 'high-growth AI partners' and building Box's presence in the AI ecosystem. Is Box's current partnership motion more focused on large established AI platforms, or is there a deliberate bet on emerging startups and developer communities? | Clarifies the strategic focus of the role and helps Felix assess whether his startup founder network and AI ecosystem fluency are directly relevant to the near-term mandate. |
| strategy_vision | How does Box think about the competitive landscape for content management in an AI-first world — especially as AI companies increasingly build their own document and data handling? Is the partnership strategy partly a response to that competitive pressure? | Demonstrates strategic awareness of Box's market position and probes whether the AI Partnerships role is offense, defense, or both — important context for how to frame the candidate's own value proposition. |
| shared_context | I noticed you co-founded Friend of a Friend LLC alongside your work at Box. I've been building my own companies in parallel with other work, so I'm curious — how does Box's culture respond to employees who have entrepreneurial projects on the side? Is that something people are open about? | Builds genuine peer-level rapport by connecting Felix's founder background to Dana's own entrepreneurial venture, while surfacing a practical and important cultural question about side projects. |
Conversation starters
- I saw you co-founded Friend of a Friend LLC — I've been deep in the founder world myself with a couple of AI products, so I'm always curious what pulls someone into starting something. What's the story behind it?
- Five-plus years at Box across five different roles is genuinely impressive — especially in a market where people jump constantly. I'd love to hear what's made it worth staying and growing there.
- I noticed you studied abroad at Universidad Nebrija in Madrid — I've always been curious about the experience of doing business coursework in a second language. How did that shape how you think about communication and building relationships?
⚠ Handle carefully
- Dana is a recruiter, not a product or business leader — avoid asking deep technical product strategy questions that she won't be positioned to answer well, as it could create awkwardness rather than rapport.
- Dana's LinkedIn shows overlapping date ranges for her Technical Recruiter I role (listed as 'July 2024 - Present') and her Technical Recruiter II role (listed as 'April 2026 - Present') — this appears to be a profile update artifact; don't probe or reference the date discrepancy as it could come across as scrutinizing or adversarial.
- Friend of a Friend LLC is listed with minimal detail — don't press for specifics about what the company does, as Dana may not want to discuss it in a professional recruiting context, especially if it's early-stage or tangential to her Box role.