Application choices
The decisions before an application
- The same software company can look attractive to equity and unattractive to credit, or vice versa. Know which security and downside you are underwriting.
- Add-on acquisitions require integration logic. “Buy and build” is not a thesis unless product fit, cross-sell, churn, systems, and purchase price are addressed.
- Preparation should include transaction mechanics and software KPIs rather than one or the other.
Work, teams and company background
Jump to a section
Compare the offer by team and work
Prestige is not a work description. Before accepting an offer, verify manager quality, actual analyst responsibilities, team placement, hours and travel expectations, location, return-offer mechanics, and whether the role builds evidence for the next step.
Record the compensation unit and paid term separately from any relocation, travel or housing support. Ask about the return-offer criteria and decision date rather than assuming the internship converts to full-time work. An attractive platform can still be the wrong assignment when the actual work does not build the evidence you need.
Match the work to the investment platform
Platform or lens: Software buyouts · What it changes for candidate research: Control investments where product position, retention, pricing, margins, and acquisition opportunities shape the return case.
Platform or lens: Explore and growth strategies · What it changes for candidate research: Company size and maturity can differ; confirm which team owns the role rather than assuming one recruiting process.
Platform or lens: Credit · What it changes for candidate research: Debt underwriting requires a different lens from equity despite shared software-sector knowledge.
Platform or lens: Portfolio operations · What it changes for candidate research: Execution can involve sales, pricing, product, finance, talent, procurement, and add-on integration.
Investing is only one possible function
- Investment roles. Screening, market work, diligence, valuation, transaction execution, portfolio monitoring, and investment-committee materials. Exact undergraduate access varies sharply by strategy and year.
- Capital formation and investor relations. Fundraising support, client materials, consultant databases, product strategy, reporting, and relationship management. Communication quality and market knowledge matter alongside analytics.
Trace the software thesis into cash flow
Build a fictional software-company case that separates recurring revenue quality, customer retention, operating costs and investment needs. Explain one proposed operational change and what it might damage if executed badly. Show the cash consequences before adding acquisition financing. A useful downside case changes the business assumptions as well as the exit value. Label the data as synthetic and distinguish an analysis of a strategy from knowledge of the firm's confidential underwriting.
Prepare the output the team would use
- Model a take-private with a base case, pricing-led upside case, and recessionary retention downside.
- Evaluate an add-on acquisition and quantify standalone value, synergies, integration cost, and leverage impact separately.
- Compare a high-growth low-margin software company with a slower-growth high-retention company at the same valuation.
The work sample should be adapted to the target role. A credit team will care more about repayment, documentation, and recoveries; a growth team will care more about retention, market structure, and growth duration; an operating team will expect a diagnosis with implementable actions.
A source-backed recommendation should make the reader able to reproduce the result. Keep an assumptions page, show the sensitivity that changes the recommendation, and identify the information you could not obtain. Submit only work that is yours to share. An anonymized name does not make confidential deal data safe to publish.
Use the interview to test the assignment
Ask which strategy, product or operating problem the intern actually supports. Find out who reads the deliverable, who checks the analysis and whether you will own a defined workstream. For a client-facing function, ask what quality control applies before material reaches investors. For an operating role, ask whether you will diagnose a problem, implement a change or merely monitor a report.
These are diligence questions, not reports of the firm's interview stages. The supplied guide does not establish a role-specific, dated sequence of assessments that should be treated as universal.
Research context
Thoma Bravo is a software and technology investor associated with control-oriented transactions, active portfolio work, and detailed underwriting of recurring-revenue businesses.