Confessions of a Defense Tech Veteran: Four Years Inside the Machine

An anonymous first-person account from a former Army officer turned defense tech startup operator. Names, companies, and identifying details have been changed or omitted.

10 PM on a Tuesday in Arlington

I am sitting in a WeWork in Clarendon at ten o'clock on a Tuesday night, and my Slack has seventeen unread threads, all of them marked urgent. In forty-eight hours, we are demoing our platform for a three-star general and his entourage of colonels, program managers, and at least one person from OSD who will ask a question nobody can answer. The software does not fully work yet. The integration we promised is held together with API calls and optimism. Our lead engineer is in San Francisco and has been awake for twenty hours. I am on my fourth cold brew from the lobby fridge, which I should note costs six dollars because this is Arlington and nothing here is cheap, least of all ambition.

This is defense tech. Not the version you read about in Forbes, where visionary founders stand in front of drones and talk about deterrence and great-power competition. Not the version from the pitch decks, where every slide has a picture of a soldier and a graph going up and to the right. The real version. The one where a former infantry captain with an MBA is debugging a demo script at ten PM because he is the only person on the team who understands both the software architecture and what a three-star general actually cares about when he sits down for a capability brief.

If you had told me four years ago that this would be my life, I would have believed you. I would have believed you because I was warned, repeatedly, by people who had done this before me, and I ignored every single one of them. Not because I thought they were wrong, but because I thought I was different. I was not different. I was just optimistic, which in this industry amounts to the same thing.

I have been doing this for four years. This is the story of how I got here, what I have learned, and what I wish someone had told me before I signed the offer letter.

A quick note before we begin: I am writing this anonymously for reasons that will become obvious. The defense tech world is small. Everybody knows everybody. If I put my name on this, my CEO would have thoughts, my customers would have questions, and my recruiter would stop returning my calls. So I am a former Army officer with an M7 MBA who has spent four years at a venture-backed defense technology startup. That is all you get. It will have to be enough.

The Decision

Let me rewind. Two years before that Tuesday night in Arlington, I was finishing my MBA at my M7 program - one of the top seven business schools in the country, the ones that open every door you have ever heard of and a few you have not. I had done the recruiting dance. I had the consulting offer. A top-three firm, good city, strong practice area. The comp was excellent. The path was clear: two years as an associate, pivot to industry or PE, collect your ticket to the upper-middle-class conveyor belt. My classmates were thrilled for me.

Then I went to a defense tech recruiting event.

I almost did not go. It was a Thursday evening, there was a case competition I could have been prepping for, and frankly I had already signed the consulting offer in my head if not on paper. A buddy from my veteran cohort dragged me along. "Just come listen," he said. "Free beer." The free beer part was true. What I did not expect was that the talk would rearrange my entire career calculus in ninety minutes.

The founder of [Company] was there. He gave a talk that was half TED Talk, half mission brief. He talked about how the Department of Defense was spending billions on systems designed in the 1990s. He talked about how the next major conflict would be won or lost based on software, not hardware. He talked about how every major tech company in Silicon Valley had decided that building tools for the military was beneath them, and how that left a gap the size of the Pacific Ocean.

Then he said something I could not shake. He looked directly at the veteran section of the audience - there were maybe fifteen of us in a room of two hundred - and said: "We need people who have been downrange and can also read a P&L. That person barely exists in the civilian world. If you are that person, we need you more than McKinsey does."

I felt something I had not felt since my last deployment: the specific, physical sensation of being needed for something important. Not wanted. Needed. There is a difference, and if you have served, you know exactly what I mean.

I was that person. Former infantry officer. Ranger tab. A deployment where I had watched million-dollar systems fail because nobody who built them had ever talked to the people using them. And now I had the MBA, the finance training, the strategy frameworks. I was, on paper, exactly what this company needed.

Three weeks later, I turned down the consulting offer and signed with [Company]. Two hundred employees. Pre-IPO. Series C. The base salary was solid, the benefits were startup-standard, and the equity package looked life-changing on a spreadsheet, which is exactly what equity packages are designed to do. My recruiter walked me through the option grant like he was revealing a treasure map. I nodded along, pretending I understood 409A valuations and preferred liquidation preferences, and later that night I spent three hours on Investopedia making sure I had not just made the worst financial decision of my life.

My classmates thought I was insane. One of them, a former Marine who was headed to Goldman, pulled me aside at a bar and said, "Brother, you did not survive Ranger School and two years of case studies to go work at a company nobody has heard of." He was not wrong about the company's name recognition. He was wrong about everything else.

My parents were confused. They had just gotten comfortable telling their friends I was going to be a consultant, which sounded respectable and stable, two things the Army had not been. Now I was explaining venture capital, stock options, and something called "defense tech" that they were pretty sure was just another way of saying "defense contractor," which is what my uncle did in the 1980s and he hated it.

My wife was supportive in the way military spouses are supportive, which is to say she had long ago stopped being surprised by my decisions and had simply learned to plan around them. She asked three questions: Is the health insurance good? Will we have to move? Do you believe in this? The answers were yes, no, and yes. That was enough for her. It would have to be enough for me too.

What Nobody Tells You

Here is what the defense tech recruiting pitch does not include, presented in the order I learned each lesson, mostly the hard way. I write this not to discourage anyone - I am still here, after all - but because I believe veterans deserve the full picture before they make a career decision this significant. We are trained to operate with incomplete information, but that does not mean we should have to.

The sales cycles will break your spirit. In commercial tech, a sales cycle might be a quarter. Maybe two. In defense, you are looking at eighteen to thirty-six months from first contact to contract award, and that is if everything goes well. I have worked deals for two years that died because of a continuing resolution in Congress. I have watched us lose contracts to companies with objectively worse products because they had a retired general on their advisory board and we did not. If you have any experience in the Army with the acquisitions process, multiply that frustration by ten and add the pressure of a startup that needs revenue to survive.

You will become a proposal writer whether you like it or not. I did not get an MBA to spend 40 percent of my time on capture management and proposal writing, but that is what happened. RFPs, RFIs, white papers, quad charts, capability briefs - the sheer volume of paperwork required to sell to the government is staggering. Every proposal is essentially a mini-thesis arguing that your company can do what it says it can do. And the evaluation criteria are sometimes so byzantine that you need a former contracting officer just to interpret the solicitation. I spent my first six months wondering when I would get to do "real strategy work." The answer is that proposal writing is the strategy work. It is how you win.

The startup culture is real, but not for everyone equally. The engineers at [Company] have the classic startup experience. Open floor plan, flexible hours, ship fast and break things. The BD and operations side - my side - is a different animal entirely. You are essentially doing government work at startup speed with startup pay. You are still dealing with contracting officers, security clearances, ITAR regulations, and the Federal Acquisition Regulation. The difference is that instead of a defense prime's army of compliance staff behind you, it is just you and maybe two other people figuring it out as you go.

Classification is a daily headache. Half your team cannot see what the other half is working on. I have sat in meetings where I could not tell my own colleagues what I had learned from a customer visit because the conversation touched on classified material. We have engineers building features for programs they do not fully understand because the requirements live behind a clearance level they do not have. You learn to communicate in careful abstractions. It is like playing telephone, except the stakes are national security and your quarterly revenue target.

The equity might be worth something. Or it might not. When I joined, [Company] had just closed its Series C at a valuation that made my options look very attractive on paper. Four years later, the valuation has gone up - defense tech has been a hot sector - but I still cannot sell a single share. There is no liquidity event on the horizon that I would bet my mortgage on. I have watched M7 classmates at Big Tech companies vest and sell RSUs every quarter while I sit on paper gains that may or may not materialize. The equity is the bet. You need to be at peace with the possibility that it pays off huge or it pays off at zero.

You will question your decision on a regular schedule. It comes in waves. The first wave hits about six months in, when the novelty wears off and you realize the grind is real. The second wave hits when your business school classmates start posting about promotions and bonuses on LinkedIn. The third wave, the dangerous one, hits around year two when you have enough experience to be valuable but not enough vested equity to feel locked in. Every veteran I know in defense tech has had a moment at 2 AM where they opened a job posting at Google or Bain and got as far as uploading their resume. Most of them closed the tab. Some did not. No judgment either way.

The Money

Let me be direct about compensation, because I think veterans considering this path deserve honesty rather than vague hand-waving about "competitive packages." I went to an M7 business school. My classmates are at McKinsey, Goldman Sachs, Google, and Amazon. I know exactly what they make because business school people talk about money the way infantry officers talk about PT scores - constantly, competitively, and with thinly veiled insecurity.

Base salary: When I joined, my base was meaningfully better than what a defense prime would have offered for a similar role, but roughly 25 to 30 percent below what my Big Tech classmates were earning. We are talking about a range that is solid upper-middle-class money but not the kind of number that makes your business school friends nod approvingly.

Equity: This is where the math gets interesting or terrifying, depending on your risk tolerance. I received pre-IPO stock options with a four-year vesting schedule. At the current preferred share price, my vested equity looks very good on a spreadsheet. But spreadsheets are not bank accounts. Until there is a liquidity event - an IPO, a direct listing, an acquisition - those numbers are theoretical. I have friends at other defense tech startups who have had liquidity events and are doing very well. I have other friends whose companies imploded and their equity went to zero. This is venture-backed startup life. The military did not prepare me for this particular flavor of uncertainty.

Year-over-year trajectory: Year one comp was a noticeable step down from what consulting would have paid. I felt it. My wife felt it. When you go from imagining a McKinsey paycheck to depositing a startup paycheck, the gap is visceral, especially in a city like DC or the Bay Area where a one-bedroom apartment costs what your parents paid for their house. Year two, with a raise and more vested equity, it looked roughly comparable. By year three, if you believe the paper valuation - and that is a significant "if" - total comp on paper exceeded what most of my consulting-track classmates were earning. Year four, same story but more so. The catch is that a large portion of that comp is illiquid and speculative. You cannot pay rent with stock options.

The golden handcuffs are real. By year three, you have enough unvested equity that leaving feels financially irresponsible. This is by design. Every startup structures vesting to keep you in the seat during the hard years. The thing nobody tells you is how psychologically effective it is. I have done the math on walking away more times than I care to admit. Every time, the unvested equity - the stuff I lose if I leave - is enough to make me stay for one more quarter, one more vesting cliff, one more year. It is the gentlest prison you will ever occupy.

The comparison that haunts you: My classmate who went to Goldman is pulling total comp that would make your eyes water. My classmate at Google has RSUs that vest every quarter like clockwork and a stock price on a public exchange. My classmate at McKinsey just made engagement manager and is clearing more than I am in guaranteed cash. And then there is me, with a strong base, a pile of options that might be worth a lot someday, and the knowledge that I helped deploy technology that is actually being used by soldiers in the field. You have to decide what you are optimizing for. If it is purely dollars, defense tech is probably not the right answer. If it is some combination of dollars, impact, and the feeling that your work matters - then the math changes.

Your clearance is a financial asset. I want to be very explicit about this. An active TS/SCI clearance is worth fifteen to thirty thousand dollars a year in salary premium. The investigation alone costs the government tens of thousands of dollars and takes months. If you have one, do not let it lapse. Factor it into every career decision. It is one of the few things you walk away from the military with that has immediate, quantifiable market value.

The Work

People ask me what I do all day. The honest answer is that no two weeks look the same, which is either a feature or a bug depending on your tolerance for chaos. But here is a representative week from last month:

A caveat: every defense tech company is different, and your specific week will depend on your role, your company's stage, and whether Congress has decided to do its job that quarter. But this is fairly representative of the rhythm.

Monday: Internal strategy meeting at 0900. We are reviewing our pipeline and trying to figure out which opportunities to pursue and which to let go. Resources are finite - a concept that somehow surprises people who have never worked at a company with fewer than five hundred employees. After that, I spend the afternoon prepping materials for a government customer demo scheduled for later in the week. This means translating engineering speak into language a program manager will understand and care about. I am essentially a bilingual interpreter between Silicon Valley and the Pentagon.

Tuesday: On-site at a military installation running a pilot program. This is the best part of the job and the reason I am still here. I am watching soldiers use software that I helped shape, and they are giving me feedback in real time. Some of it is positive. Some of it is "sir, this interface is terrible and whoever designed it has clearly never worn a ruck." Both kinds are useful. I take notes, shoot video with permission, and start mentally drafting the product feedback I will relay to our engineering team.

Wednesday: Back in the office - or rather, back in whatever WeWork or co-working space we are using this month. I spend the morning writing a proposal response for a contract opportunity. This involves cross-referencing the solicitation requirements, coordinating with our technical team on what we can credibly promise, and arguing with our legal counsel about ITAR restrictions on what we can include in the proposal. In the afternoon, I have a call with a partner company about a potential teaming arrangement. In defense, you team as often as you compete, and figuring out who to team with is a strategic decision that can make or break a pursuit.

Thursday: Flying to a conference. AUSA, SOFIC, Modern Day Marine, SOF Week - the defense world runs on conferences the way Wall Street runs on dinners. I will spend the day shaking hands with generals, colonels, program managers, Hill staffers, and other startup founders. The schmoozing is real and it is necessary. Relationships matter in defense contracting more than in almost any other industry. I will have the same conversation about our capabilities approximately thirty-five times. I will collect a stack of business cards I will never organize properly. I will attend a panel about "innovation in defense acquisition" that says nothing new but features important people, which is the point.

Friday: Theoretically, this is when I do strategic work. Pipeline reviews, competitive analysis, long-term planning. In practice, Friday is when all the fires from Monday through Thursday come home to roost. A customer has a question about our security architecture. A proposal deadline got moved up. The CEO wants to discuss a potential acquisition target. By the time I actually sit down to think strategically, it is 4 PM and I have been context-switching all day. I do my best thinking on Friday evenings and Saturday mornings, which is not a schedule I would recommend but it is the one I have.

If that week sounds exhausting, it is. If it sounds exciting, that is also true. The thing about defense tech that is hard to communicate to people outside of it is that the work is simultaneously mundane and consequential. You are filling out quad charts and arguing about font sizes on a capability brief, but the thing you are selling might actually save lives. That tension - between the bureaucratic tedium and the weight of the mission - is what makes this industry unlike anything else.

The Politics

Nobody warned me about the politics. And I do not mean office politics, though every company has those. I mean actual, capital-P politics - the Congressional appropriations process, the defense authorization cycle, the election-year dynamics that determine whether your program gets funded or gets zeroed out by a staffer who has never heard of your company and does not care.

In the Army, I understood that politics existed somewhere above my pay grade, but it rarely affected my daily life in a tangible way. In defense tech, politics is your daily life. It is the water you swim in. Your revenue forecast is a function of the defense budget, which is a function of the National Defense Authorization Act, which is a function of which party controls the House Armed Services Committee, which is a function of the midterm elections. If that chain of dependencies does not terrify you, you have not thought about it hard enough.

Congressional dynamics affect your revenue more than product quality. I learned this the hard way during my first continuing resolution. Congress could not agree on a budget, so spending was frozen at the previous year's levels, and the new program we were counting on simply did not get funded on schedule. We had the best product. We had a customer who wanted to buy it. The end user - an actual unit in the field - was asking for it by name. But the money was not there because of a political standoff between two senators who could not agree on an unrelated spending provision. We missed our quarterly revenue target by a significant amount. Our CFO aged five years in three months.

You learn very quickly that in this industry, your most important stakeholder is not your customer. It is the appropriations committee. And the appropriations committee does not care about your product roadmap.

Your competitor just hired a retired four-star as their "strategic advisor." This happens constantly. A defense prime or even another startup brings on a retired general officer as an advisor or board member, and suddenly they have access and credibility that you cannot match with product quality alone. The revolving door between the Pentagon and the defense industry is real, it is legal, and it is enormously frustrating when you are on the wrong side of it. We have lost opportunities not because our technology was worse but because the other company had someone who could pick up the phone and call the decision-maker directly.

The Pentagon acquisition system was designed in an era when the Soviet Union was the threat and waterfall development was cutting edge. The Defense Acquisition System, the Joint Capabilities Integration and Development System, the Planning, Programming, Budgeting, and Execution process - these frameworks were built for buying tanks and ships over multi-decade timelines. They are fundamentally mismatched with software that updates weekly. The entire system assumes you know exactly what you want before you buy it, which is the opposite of how modern software development works. People inside the Pentagon know this. They are trying to fix it. But institutional inertia is a force of nature.

DIU, AFWERX, and the other innovation organizations are doing God's work, but they are not enough. The Defense Innovation Unit, AFWERX, NavalX, Army Futures Command - these organizations exist specifically to help startups sell to the military. They are staffed by smart, motivated people who genuinely want to change how the DoD buys technology. And they have had real successes. But they operate within a system that still favors the primes, and the contracts they can award are often too small to sustain a growing startup. They are a door in, not a destination. You still need to navigate the traditional acquisition system eventually, and that is where the primes have fifty years of institutional knowledge and relationships that no startup can replicate overnight.

The media narrative is not the reality. If you read the tech press, you would think defense tech startups are minting money and disrupting the Pentagon daily. The reality is messier. Valuations have inflated, some on the back of genuine revenue growth and others on the back of hype and geopolitical anxiety. Some companies are building real products with real traction. Others are burning venture capital on flashy demos that will never see a production contract. Telling the difference from the outside is almost impossible, which is why due diligence before you join a company matters enormously. Ask to see the pipeline. Ask about contract vehicles. Ask how much revenue is recurring versus one-time. If they will not tell you, that itself is an answer.

The People

The best part of defense tech - the thing that keeps me here when the politics and the bureaucracy make me want to throw my laptop into the Potomac - is the people. Specifically, the bizarre and wonderful collision of people that only happens at a company like this.

The cast of characters at a defense tech startup is unlike anything you will find at a normal company. It is as if someone took a think tank, a special operations unit, a Silicon Valley garage, and a Capitol Hill office and put them in a blender. Here is who you will be working alongside.

The former SOF guys. Every defense tech startup has at least three former Special Operations people. They are brilliant operators who can brief a general, run a training exercise, and troubleshoot a satellite link, but they have never used a CRM and they think "pipeline management" is something that happens on a FOB. They are your secret weapon for customer relationships because they speak the language and they have the credibility. Getting them to log their contacts in Salesforce is a battle you will fight and lose repeatedly.

The Stanford CS grads. They are twenty-six years old, mass-produce elegant code, and have never spoken to an actual service member in their lives. They are genuinely surprised to learn that soldiers do not always have reliable internet access. They will build you something technically brilliant that is completely unusable in the field, and then they will fix it in a week once you explain the problem clearly. The translation layer between what they build and what the customer needs is where veterans add the most value.

The former Hill staffers. They know every acronym, every committee, every staffer who matters. They can read a defense authorization bill like a novel and tell you exactly where the money is going. They know nothing about technology and they do not pretend to. What they know is how Washington works, and in this industry, that knowledge is worth its weight in gold.

The founder. Ours is a former [military branch] officer who went to a top CS program, worked at a major tech company, and then decided that the defense industrial base was broken and he was going to fix it personally. He holds the entire operation together through some combination of charisma, conviction, and an inhuman tolerance for ambiguity. He can pitch a four-star general at breakfast, negotiate a term sheet with a VC at lunch, and debug a deployment pipeline at dinner. I have never met anyone like him, and I suspect the company would not exist without him. This is both inspiring and terrifying, because single points of failure are bad in systems architecture and they are bad in organizations too.

The accidental mentors. These are the people nobody talks about but who make the place work. The retired O-6 who does consulting for us two days a week and who knows every program office in the Army. The former contracting officer who joined from a prime and can decode an RFP like she is reading a children's book. The young analyst fresh out of Georgetown's security studies program who works harder than anyone and knows more about Chinese military modernization than people three levels above her. These are the people you learn from daily, and they are the reason I stay even when the politics make me want to walk out.

There is a particular magic to a room where a former Delta operator, a Stanford PhD, a retired colonel, and a twenty-four-year-old policy wonk are all arguing about the same problem. Nobody else has rooms like that. Defense tech does. If you are the kind of person who thrives in intellectual chaos and diverse perspectives, you will love it here.

The Advice

If you are a veteran reading this and considering the defense tech path, here is what I would tell you over a beer at an AUSA happy hour. Not the polished version I give on career panels when there is a microphone and a moderator. Not the version optimized for LinkedIn engagement. The version I would give you in a corner booth after my second bourbon, when the recruiters have gone home and it is just us.

Do it if you actually care about the mission, not just the equity. This sounds like a platitude, but I mean it operationally. There will be days - weeks, even - when the politics are maddening, the bureaucracy is soul-crushing, and your comp looks embarrassing next to your classmates in finance. The thing that keeps you going is the genuine belief that the work matters. If you are doing this primarily for the equity upside, you will burn out. The equity might pay off, but the timeline is uncertain and the road is long. Mission motivation is the only fuel that does not run out.

Get the MBA first if you can. I know this is self-serving advice from someone who has one, but it is true. The MBA changed how people treated me in boardrooms. Before business school, I was a "former military guy" - respected for my service but not taken seriously as a business operator. VCs would nod politely and then talk over me. After the MBA, I was a "veteran with a top business degree" - someone who could credibly discuss unit economics, go-to-market strategy, and capital allocation in the same language they used. The credential opens doors. More importantly, the education gives you frameworks for thinking about business problems that the military simply does not teach.

Can you succeed in defense tech without an MBA? Absolutely. Plenty of people do. But if you can get into a strong program and your GI Bill and Yellow Ribbon cover most of the cost, the ROI is exceptional. You will emerge with a powerful network, a credible credential, and two years to figure out what you actually want to do - which, despite what your transition assistance brief told you, is not something most people figure out during their last six months in uniform.

Your clearance is worth real money. Do not give it up. I mentioned this earlier, but it bears repeating. An active TS/SCI with a recent polygraph is worth a significant salary premium. The investigation takes months and costs the government a fortune. If you have one, maintain it. Take a reserve or guard billet if you need to. Do whatever you have to do to keep it active while you are in school and during your transition. It is a depreciating asset the moment you stop maintaining it.

Network at the right events. AUSA, SOFIC, SOF Week, DIU Demo Days, the Reagan National Defense Forum if you can swing an invite - these are where the jobs are, the deals are made, and the relationships are built. LinkedIn is fine. Cold emails are fine. But nothing replaces showing up in person, shaking hands, and having a real conversation about what you have done and what you want to do. The defense tech community is surprisingly small. Everyone knows everyone. Your reputation will precede you, for better or worse.

Understand the landscape before you pick a company. Not all defense tech startups are created equal. Some have real government contracts and real revenue. Others are burning venture capital on R&D with no clear path to production. Some have strong relationships with program offices and are well-positioned for follow-on contracts. Others are relying on a single OTA or SBIR to keep the lights on. Before you accept an offer, talk to people in the industry. Ask about the company's contract vehicles, their customer relationships, their burn rate. The difference between a defense tech startup that makes it and one that does not often comes down to whether they figured out the government sales motion, and that is something you can evaluate before you join.

Be ready to explain your choices repeatedly. At every MBA reunion, at every networking event, at every holiday dinner with extended family, someone will ask why you took a 30 percent pay cut to work on military technology when you could be at Google. You need an answer that is honest and that you are comfortable delivering on autopilot, because you will give it hundreds of times.

Mine goes something like this: "I spent years watching people use broken technology in dangerous situations. Now I have the skills and the opportunity to fix that. The money will work itself out." That answer is true, it is concise, and it tends to end the conversation in a way that makes people respect the decision even if they would not have made it themselves. Have your version ready. Practice it. Own it.

The best role for a veteran is at the seam. The most valuable position in a defense tech company is the one that sits between the customer and the product team. You speak both languages. You understand what a battalion commander needs, and you can translate that into a product requirement that an engineer can build against. You know what "good enough" looks like in the field, and you can push back on engineering perfectionism that delays delivery. This is your superpower, and it is the reason defense tech companies hire veterans. Do not let yourself get siloed into pure BD or pure operations. Stay at the intersection. That is where you create the most value and where you are hardest to replace.

Learn to speak both languages fluently. When I say you sit at the seam, I mean it literally. You need to be able to walk into a meeting at the Pentagon, speak in acronyms and military planning constructs, reference the right doctrine, and make a three-star feel like you understand his problem. Then you need to walk back into your office the next day, open Jira, write a user story that your engineering team can build against, and explain why the feature needs to work in a disconnected environment with intermittent satellite connectivity. The veteran who can do both of those things fluently is the most valuable person in any defense tech company. Full stop.

Do not underestimate the culture shock. Even if you think you are ready for the civilian world because you went to business school, defense tech has its own unique culture shock. The engineers work on a different schedule than you are used to. "Moving fast" in a startup means something different than "moving fast" in the Army. Consensus-driven decision-making will drive you insane after years of top-down command authority. And the first time someone tells you they cannot make a meeting because they have a "conflict," and the conflict is a yoga class, you will have feelings about it. Those feelings are valid. Keep them to yourself.

The Verdict

So. Would I do it again?

I have been asked this question by at least two dozen veterans over the past four years - at conferences, in DMs, over beers, on phone calls. Every time, I pause before answering, not because I do not know the answer but because I want to make sure I am giving it honestly rather than reflexively.

Yes. But with caveats, with my eyes wide open, and with a much better understanding of what I was signing up for.

The honest answer is more nuanced than a simple yes or no. There are days when I feel like I am doing the most important work of my life, and there are days when I feel like an overeducated bureaucrat arguing about contract line item numbers. Both of those days can be the same day. Sometimes the same hour.

I would do it again because the work is genuinely meaningful. I have watched technology I helped shape get deployed to units in the field. I have stood in a tactical operations center and seen a lieutenant use a tool that exists because I fought for it in a product meeting six months earlier. I have received messages from NCOs telling me that something we built made their job easier, safer, or faster. That feeling - the feeling that your work matters to people you care about, people who are doing dangerous things in difficult places - is something I did not find in consulting or finance, and I am not confident I would find it in Big Tech.

I would do it again because the people are extraordinary. The combination of military operators, world-class engineers, policy experts, and missionary founders creates an environment unlike anything else in the business world. I learn something new every week. I am never bored. Those are not small things. After the Army, I was terrified of being bored. Of sitting in a cubicle doing work that did not matter for people I did not respect. That fear has not materialized. Not once in four years.

I would do it again because I believe the bet will pay off. Not with certainty - nobody has certainty in venture-backed startups - but with enough conviction to stay in the seat. The defense tech sector is growing. The government is spending more on software. The threat environment demands it. The bipartisan consensus around defense modernization is one of the few things both sides of the aisle agree on, which is about the strongest tailwind you can have in this industry.

If [Company] executes well, the equity will be worth the wait. And if it is not, I will have four years of experience in one of the fastest-growing sectors in tech, a network that spans the Pentagon and Silicon Valley, and a story that will open doors wherever I go next. The skills you build in defense tech - navigating complex stakeholder environments, selling to the government, translating between technical and operational audiences - are transferable in ways that are not immediately obvious but become clear very quickly when you start interviewing elsewhere.

But I would also be more honest with myself about the tradeoffs. I would have negotiated harder on comp - startups will lowball you because they know the mission sells itself, and you should not let it. I would have pushed for more equity earlier, before the valuation went up. I would have set better boundaries around my time, because defense tech will consume every hour you give it and then ask for more. The mission is not an excuse for burnout, even though it feels like one at 11 PM on a Sunday when you are prepping for a Monday morning briefing. And I would have spent less time comparing myself to my MBA classmates and more time defining success on my own terms. The comparison game is poison. It will eat you alive if you let it.

I sacrificed years of higher guaranteed earnings. I sacrificed weekends and evenings to proposal deadlines and customer demos. I sacrificed the clean, predictable career arc that consulting would have provided. I missed dinners, missed weekends, missed the kind of work-life balance that my friends in Big Tech post about on Instagram. My wife has eaten more solo dinners than either of us would like to count.

In exchange, I got a front-row seat to one of the most important transformations in American defense. I got equity in a company I believe in. I got a network that spans the Pentagon, Capitol Hill, and Sand Hill Road. I got the knowledge that my work connects directly to the mission I signed up for when I raised my right hand at eighteen. And I got something harder to quantify but equally important: the feeling, every single day, that I am doing exactly what I am supposed to be doing.

That trade is not for everyone. But for the right veteran - the one who cares about the mission, who can tolerate ambiguity, who has the skills to operate at the intersection of technology and national security - it is one of the best career paths available right now. And it is only going to get more important.

One last thing. If you had told me five years ago that I would be sitting in a WeWork at ten PM on a Tuesday, debugging a demo for a general while eating cold pad thai and arguing with an engineer in San Francisco about API authentication, I would have told you that sounded terrible. And it is, a little bit. But it is also the most alive I have felt since I left the Army. There is a version of that feeling - the feeling of doing hard things with good people for a reason that matters - that I thought I had left behind when I took off the uniform. It turns out you can find it again. You just have to look in unexpected places.

Defense tech is one of those places. It is messy, underpaid relative to alternatives, politically frustrating, and occasionally absurd. You will spend more time on PowerPoint than you ever thought possible after leaving the Army. You will attend conferences where people say "lethality" and "innovation" so many times that the words lose all meaning. You will argue with contracting officers about evaluation criteria while your friends at Google are arguing about which kombucha to stock in the micro-kitchen.

But it is also important. It is growing. It is full of the kind of people who make you better at your job and sharper in your thinking. And for a veteran with the right skills and the right temperament - someone who can tolerate ambiguity, navigate bureaucracy, and keep their eyes on the mission when everything else is noise - there is no better seat in the house.

Come find us. We need the help.

The author is a former Army officer, M7 MBA graduate, and current defense tech operator. Identifying details have been changed to protect anonymity.

Have questions about breaking into defense tech? Head over to our community forums where veterans currently working in the industry are happy to share their experiences and answer questions. Whether you are still on active duty, in business school, or already in the workforce and considering a move, there are people in this community who have walked the path and can help you think through it. You are not in this alone.

Published by Sitreps to Steercos. All views expressed are those of the anonymous author and do not represent the official position of any company, organization, or government agency.