Sr. Staff Software Engineer - Austin, TX

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. Must include only sections with real specific content. Must not include filler like "commensurate with experience". Must preserve all substantive info, remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines, application instructions. We need to parse the posting. Key content: - Intro paragraph about TrendAI, mission, etc. Could be "About the role" or maybe "About the team". We need to decide sections. We have sections: Position Summary, How We Build, Requirements, Responsibilities, Required Qualifications, Preferred Qualifications, Why Join TrendAI?, What We Offer You, Benefits list. We need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use "About the role" for position summary and intro. "Responsibilities" for responsibilities list. "Requirements" for required qualifications? Actually "Requirements" heading could contain required qualifications. "Qualifications" could contain preferred qualifications? But we have both required and preferred. Could combine under "Requirements" and "Qualifications". Or we could have "Requirements" for required, "Qualifications" for preferred. "Skills" maybe not needed if not explicit. "Benefits" for benefits list. "Pay" and "Schedule" only if present. The posting mentions location hybrid, in-office three days a week (Tuesday, Wednesday, Thursday). That's schedule info. So we can include Schedule section with that detail. Pay: not mentioned specific salary, only "competitive compensation with bonus opportunity". That's vague but maybe we can include Pay section if there is some mention: "We offer competitive compensation with bonus opportunity tied to company performance". That's not a specific number but it's still compensation info. The instruction: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does state competitive compensation with bonus opportunity. That's not a specific number but it's still stating compensation. Is that considered filler? It's vague but it's actual statement. I'd include Pay section with that sentence. Benefits: they list many benefits. So Benefits section. Schedule: they state hybrid role based out of Austin, TX office and requires in-office presence three days a week (Tuesday, Wednesday, Thursday). So schedule. Now we need to strip boilerplate: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At end there is EEO statement, LI-JL1, etc. Remove those. Also remove "At TrendAI™, we’re always seeking exceptional talent; people who want to collaborate with the best and push boundaries together. Here, your work goes beyond building a career. You will help protect what matters and play a vital role in shaping a safer, more trustworthy AI-powered future. AI Fearlessly." That's intro; could be part of About the role. Now produce HTML fragment. Structure:

About the role

... (intro + position summary + how we build maybe)

But we might split into multiple paragraphs. We need to preserve all substantive info. Let's extract substantive paragraphs. Intro: "TrendAI™, the global AI security leader and enterprise business unit of Trend Micro, empowers organizations with full AI visibility and consolidated security that inspires confidence, drives innovation, and eliminates risk. At TrendAI™, we’re always seeking exceptional talent; people who want to collaborate with the best and push boundaries together. Here, your work goes beyond building a career. You will help protect what matters and play a vital role in shaping a safer, more trustworthy AI-powered future. AI Fearlessly." Location: "Location: This is a hybrid role based out of our Austin, TX office and requires in-office presence three days a week (Tuesday, Wednesday, Thursday)." This could go under Schedule. Position Summary: "TrendAI is seeking a Senior Staff Software Engineer to help build Trend Vision One™ Private Access, our Zero Trust Network Access (ZTNA) capability. Private Access lets enterprise customers reach internal applications — RDP, SSH, web — without exposing those apps to the public internet and without a traditional VPN. The Austin team works across three pieces of Private Access: a Connector on-premises next to the customer's application; a Relay in our cloud that brokers the connection between the end user's device and the Connector; and a Controller of cloud microservices that runs the policy, identity, and authorization plane. The product runs across many global cloud regions to meet customer compliance and latency needs. This is a hands-on engineering role with architectural scope." How We Build: paragraph about agents, etc. We could combine Position Summary and How We Build under About the role. Now Responsibilities: list bullet points. Responsibilities list: - Design and implement features across the Connector, the Relay, and the Controller services that drive them. - Own one or more Controller microservices end to end (rule engine, geolocation, event workers, proxy paths, connector management). - Diagnose and resolve performance issues in production: memory pressure, CPU saturation, latency hotspots, autoscaling tuning. - Write architecture proposals and design documents; drive them through review with peers and the team's architect. - Investigate complex production support cases — the ones that require domain expertise about a customer's environment, an interop quirk, or proposing a different approach to their problem. - Contribute to the team's AI-augmented development pipeline: shape what gets autonomous, where humans gate, and what validation is non-negotiable for a security product. Now Requirements: maybe split into Required Qualifications and Preferred Qualifications. Required Qualifications list: - 7+ years of experience building production backend systems. - Equally comfortable with Kubernetes-deployed services and software that ships as a Linux VM — our stack spans both. - Strong proficiency in Go or an adjacent systems-leaning language (Rust, C++, or similar) and willingness to be polyglot in our stack (Go, Python, some C/C++). - Demonstrated experience operating software that runs in customer environments — on-prem services, marketplace images, update mechanisms — and the realities of long-tail version compatibility (customers do not upgrade on your schedule). - Hands-on production debugging with metrics, profiling, and autoscaling (HPA / KEDA). - Linux internals (systemd, namespaces, networking) at a level sufficient to debug a misbehaving Connector running on a customer's host. - Networking fundamentals (TCP/IP, TLS, proxies, NAT, firewalls) — the Connector and Relay carry customer traffic directly. - Demonstrated experience using an agent harness like ours in real engineering work, and the judgment to direct, review, and validate its output. - Excellent written communication; ability to write design documents that survive review. Preferred Qualifications list: - Prior work on a ZTNA, SASE, SSE, VPN, or other network security product. - Distributed systems experience — consistency, retries, idempotency, and reasoning about partial failures across services and regions. - Production depth in Microsoft Azure (where our cloud services run). AWS and Oracle Cloud Infrastructure (OCI) experience is a plus — the Relay also deploys to those clouds for regions where Azure isn't available. - CI/CD and supply-chain hygiene: signed releases, SBOM, reproducible builds. - Experience designing or operating an LLM-powered system in production (RAG, agentic workflows, or otherwise). - Track record of driving architectural decisions across multiple services and lifting peers along the way. Now Why Join TrendAI? Could be part of About the role or maybe a separate section but not in allowed headings. Could incorporate into About the role. What We Offer You: benefits list. Benefits list: - Comprehensive medical, dental and vision insurance - Life insurance - Short & Long Term Disability - Pre-partum, maternity, parental and medical leave - Mental Health Wellness Program - Adoption Assistance - Wellness Incentive - Pet Insurance - 401(k) with company match - Paid Time Off - 14 Annual Holidays - Tuition Assistance - Employee Resource Groups Also mention: "We offer competitive compensation with bonus opportunity tied to company performance, along with room to enhance your skills through ongoing learning and broad technological opportunities." That's Pay. Also mention: "Achieving work-life balance is a priority, complemented by team activities, fostering an environment rooted in equity, inclusion, and collaboration, that is reflected in both our culture and our work." Could be part of Benefits or separate but not needed. Now Schedule: hybrid role based out of Austin, TX office and requires in-office presence three days a week (Tuesday, Wednesday, Thursday). Now we need to output HTML fragment only, no extra markdown. We'll produce:

About the role

TrendAI™, the global AI security leader and enterprise business unit of Trend Micro, empowers organizations with full AI visibility and consolidated security that inspires confidence, drives innovation, and eliminates risk. At TrendAI™, we’re always seeking exceptional talent; people who want to collaborate with the best and push boundaries together. Here, your work goes beyond building a career. You will help protect what matters and play a vital role in shaping a safer, more trustworthy AI-powered future. AI Fearlessly.

TrendAI is seeking a Senior Staff Software Engineer to help build Trend Vision One™ Private Access, our Zero Trust Network Access (ZTNA) capability. Private Access lets enterprise customers reach internal applications — RDP, SSH, web — without exposing those apps to the public internet and without a traditional VPN. The Austin team works across three pieces of Private Access: a Connector on-premises next to the customer's application; a Relay in our cloud that brokers the connection between the end user's device and the Connector; and a Controller of cloud microservices that runs the policy, identity, and authorization plane. The product runs across many global cloud regions to meet customer compliance and latency needs. This is a hands-on engineering role with architectural scope.

We're moving in the same direction as the rest of the industry: engineers no longer just write code; we design the systems that produce it. Concretely, we're building toward a daily loop where: Engineers work through an agent harness (Claude Code, plus its peers) layered on top of GitHub Actions, Jira, CI/CD, docs, and runtime data. Agents handle most of the inner development loop. Humans gate at the edges — architecture, end-to-end validation, the failures the agents can't resolve, and the question of what "good" actually means. Engineers design the pipeline; if the output is bad, we fix the assembly line. We're partway through this transition and the candidate we hire will help define how much further it goes.

Responsibilities

• Design and implement features across the Connector, the Relay, and the Controller services that drive them.
• Own one or more Controller microservices end to end (rule engine, geolocation, event workers, proxy paths, connector management).
• Diagnose and resolve performance issues in production: memory pressure, CPU saturation, latency hotspots, autoscaling tuning.
• Write architecture proposals and design documents; drive them through review with peers and the team's architect.
• Investigate complex production support cases — the ones that require domain expertise about a customer's environment, an interop quirk, or proposing a different approach to their problem.
• Contribute to the team's AI-augmented development pipeline: shape what gets autonomous, where humans gate, and what validation is non-negotiable for a security product.

Requirements

• 7+ years of experience building production backend systems.