Why this persona fits the audience
Leads application security for a 9-person Bengaluru SaaS startup with public signup, login, and partner API endpoints. He already uses DataDome alongside Cloudflare, reviews blocked-request reasons with one backend engineer, and maintains partner allowlists for automated traffic.
- Age: 31
- Location: Bengaluru, India
- Occupation: Application security lead
- Income: INR 42L
- Education: BTech in computer science
- Company size: 9 employees (3 engineers, 2 product, 1 design, 1 ops, 1 sales, 1 CEO)
- Years in role: 2
“The goal isn't to build walls, it's to understand the landscape so well that the walls build themselves where they're needed most.”
Ujjawal Adiga's journey into application security began not with a grand plan, but with a deep-seated fascination for how systems work and, more importantly, how they can be broken. Growing up in Mysore, his parents, both educators, instilled in him a strong sense of discipline and a love for learning. This translated into a BTech in Computer Science from a reputable Bengaluru university, where he excelled, particularly in areas requiring logical problem-solving. Post-graduation, he spent three years at a large IT services firm, gaining broad exposure to enterprise systems but feeling constrained by the bureaucracy and lack of direct impact. He craved a more dynamic environment where his contributions could be immediately felt. This led him to his current role at a burgeoning SaaS startup, a move that aligned perfectly with his desire for technical autonomy and hands-on problem-solving. He thrives in the lean, agile atmosphere, even with the inherent pressures of being the sole security lead for a rapidly scaling product. His income of INR 42L reflects his specialized skills and the high demand for application security expertise in the Indian tech scene. Ujjawal is meticulous about his work, viewing security not as a set of rules to enforce, but as an intricate system to be understood and optimized. He meticulously documents everything, from firewall configurations to incident response procedures, believing that clear documentation is the bedrock of robust security. His current focus is on achieving SOC 2 compliance, a significant undertaking for a company of their size, which involves rigorous process definition and implementation. He sees this not just as a compliance checkbox, but as a fundamental step in maturing the company's security posture and building trust with enterprise clients. He views his role as a guardian, constantly scanning the horizon for threats, and building resilient defenses through systematic control and incident prevention. His personal life is equally structured, with a disciplined routine that supports his demanding professional life. He views time and money as resources to be managed efficiently, with a long-term goal of financial security and the ability to invest in further learning and perhaps, eventually, his own venture.
Background & daily life
A day in their life
Ujjawal's day begins at 5:30 AM with a run. After a quick breakfast, he cycles to the office, arriving by 8:30 AM. The first hour is spent reviewing overnight alerts and checking the status of automated security scans. He then dedicates time to refining Cloudflare WAF rules based on recent traffic patterns, often cross-referencing with DataDome's blocked request logs. Mid-morning involves a sync with Rohan to discuss any suspicious activity or recent incident findings. The afternoon might include updating documentation, researching potential vulnerabilities in new libraries, or working on the SOC 2 compliance checklist. He leaves by 6:30 PM, often spending an hour in the evening reading security blogs or contributing to an open-source project.
Lifestyle
Rents a 2BHK in Koramangala with a treadmill desk setup. Wakes at 5:30 AM for 45-minute runs, then cycles to work on rainy days. Meals are prepped Sunday evenings (turmeric rice, dal, seasonal veg). Spends weekends at a local badminton court or tweaking his Raspberry Pi home server. He's saving for a down payment on a small apartment, aiming for financial independence within ten years. Social life is limited to a few close college friends and occasional tech meetups.
Work life
Ujjawal is the sole application security lead at a fast-growing SaaS startup. His days are a constant juggle between proactive hardening and reactive incident response. He spends significant time configuring and tuning Cloudflare WAF rules, analyzing DataDome's bot traffic reports, and collaborating with the single backend engineer, Rohan, on parsing blocked request logs. Maintaining the partner API allowlist is a critical, time-consuming task. The pressure is high, as any significant breach could cripple their small operation.
Relationships
He maintains a close, professional relationship with Rohan, the backend engineer, who is his primary technical collaborator. His CEO, Priya, trusts his judgment implicitly but is budget-conscious. His parents, retired teachers in Mysore, are proud of his career but don't fully grasp the technical details. He has a small circle of college friends he meets for occasional badminton.
How they decide
Ujjawal is highly research-driven and analytical. He meticulously evaluates technical documentation, compares features against his specific needs, and seeks out peer reviews or community discussions before committing to a solution. He prioritizes tools that integrate seamlessly with his existing stack and offer clear, actionable insights, preferring to avoid complex setups or extensive training.
How they sound
Speaks with a measured, precise cadence. Uses technical jargon naturally but can explain complex concepts clearly when needed. Avoids hyperbole or overly casual slang. His tone is generally calm and analytical, even when discussing critical issues. He tends to use phrases like 'From a security perspective...' or 'The primary concern here is...'.
Personality traits
- Detail-obsessed but pragmatic
- Prefers written documentation over meetings
- Quietly competitive with peers
- Skeptical of solutions that require ops overhead
- Stores passwords in a YubiKey 5C
- Always reads changelogs
- Uses Chromium with aggressive cookie controls
- Distrusts email attachments
- Keeps a private wiki of security playbooks
Goals
- Achieve SOC 2 compliance within 18 months
- Automate 80% of security monitoring tasks
- Build a robust incident response playbook
- Mentor a junior engineer in security best practices
- Contribute a security tool to an open-source project
Problems & frictions
- Limited engineering resources for security initiatives
- Balancing rapid feature development with security requirements
- Lack of centralized logging and visibility across all services
- Managing the security posture of third-party integrations
- Constant threat of sophisticated bot attacks targeting user data
Values
- systematic control
- incident prevention
- documentation
- technical autonomy
- lean efficiency
Interests
- Cloudflare
- AppSec
- Linux
- OpenTelemetry
- Kubernetes security
- infosec community
Media habits
- Twitter (security circles)
- Hackernoon
- Linux Foundation blogs
- YouTube (technical talks)
- XKCD