10 fictional AI personas. Exploratory perspectives, not a survey of real customers. Methodology & limitations

Jeffrey Mann

Jeffrey Mann

Salesforce application developer at a mid-size SaaS company

Full-depth AI personas

Why this persona fits the audience

Works on a 6-person Salesforce team at a B2B SaaS company in Austin. Uses sf CLI in VS Code, keeps a spreadsheet that maps Apex classes and triggers to features, and runs a targeted subset of tests in GitHub Actions before merge and in nightly CI.

  • Age: 32
  • Location: Austin, Texas, US
  • Occupation: Salesforce application developer
  • Income: $145,000/year
  • Education: Bachelor's degree in Computer Science
  • Company size: Mid-size SaaS company (approx. 500 employees)
  • Years in role: 5
“The real win is building something robust that doesn't break when you look at it funny, and making sure we can ship it without holding our breath.”

Jeffrey Mann, 32, is a dedicated Salesforce application developer at a mid-size SaaS company in Austin, Texas. He earned his Bachelor's in Computer Science and has spent the last five years honing his skills in the Salesforce ecosystem. His work revolves around developing and maintaining custom solutions on the Salesforce platform for their B2B clients. Jeffrey is highly conscientious, a trait that manifests in his meticulous approach to code quality and process. He firmly believes in reliable delivery and maintaining clean source control, which drives his interest in pragmatic automation. His current team of six is grappling with the inefficiencies of lengthy test cycles, a problem Jeffrey actively tries to mitigate. He's a proponent of Salesforce DX and leverages VS Code with the sf CLI for his development workflow. Recently, he's been focused on optimizing their GitHub Actions setup to run only the necessary subset of Apex tests before merges, a task that often involves manually updating his elaborate spreadsheet that meticulously maps Apex classes and triggers to specific features. This ongoing effort is a direct response to the team’s increasing frustration with slow deployments and the risk of introducing regressions. While he's generally agreeable, he can be quite firm on technical standards when he believes they are crucial for long-term stability. He's saving diligently, hoping to one day own a condo, a goal that reflects his pragmatic outlook on financial security and his aversion to the uncertainty of renting. He’s not driven by status, but by the satisfaction of building and maintaining reliable systems.

Background & daily life

A day in their life

Jeffrey's weekday starts around 7:30 AM with coffee and a quick scan of tech news. He commutes to the office (or logs in if remote) by 8:30 AM, usually diving into emails and reviewing the overnight CI/CD results from GitHub Actions. His morning is typically dedicated to coding new features, collaborating with teammates on shared tasks, or debugging issues reported by QA. After a brief lunch break, he might spend an hour refining their test execution strategy or updating his meticulously maintained spreadsheet mapping Apex classes to features. The late afternoon often involves code reviews, stand-ups, and planning for the next sprint, aiming to wrap up by 5:30 PM.

Lifestyle

Jeffrey enjoys the vibrant Austin tech scene but his social life is relatively quiet. He typically spends evenings working on personal coding projects or catching up on industry news. Weekends often involve hiking in the nearby greenbelts or trying out new breweries with a small circle of close friends. He's mindful of his finances, aiming to save for a down payment on a condo in the next few years, and prioritizes efficiency in his daily routines to maximize free time. He's not one for grand gestures, preferring steady progress and reliability in all aspects of his life.

Work life

As a Salesforce developer, Jeffrey's days are a blend of coding, debugging, and collaborating. He works closely with his 5-person team, often pair-programming on complex features or reviewing each other's pull requests. The pressure is on for reliable delivery, especially with their SaaS product's rapid release cycles. He spends a significant amount of time managing their Salesforce DX configurations, optimizing Apex test suites, and ensuring the CI/CD pipeline runs smoothly. The constant need to balance new feature development with maintaining existing code and reducing technical debt keeps him engaged but also challenged.

Relationships

Jeffrey has a close-knit group of 3-4 friends from college, mostly in tech, with whom he shares industry insights and occasional weekend adventures. His family lives out of state, and he stays in touch via weekly video calls. He respects the opinions of his direct manager and his more senior teammates, often seeking their guidance on architectural decisions.

How they decide

Jeffrey is a research-heavy decision-maker. He thoroughly investigates options, weighing pros and cons, and often seeks out peer reviews or community consensus before committing. He's cautious with new tools, preferring to understand the underlying mechanics and potential impact on his existing workflows. He values evidence and practical application over hype.

How they sound

Speaks with a clear, measured cadence. Tends to use precise technical language. Avoids overly casual slang but isn't afraid of industry jargon. His tone is generally calm and analytical, rarely raising his voice. He's direct but polite, often prefacing opinions with phrases like 'From my perspective' or 'What I've found is'.

Personality traits

  • Methodical
  • Detail-oriented
  • Pragmatic
  • Dedicated
  • Resourceful
  • Analytical
  • Slightly introverted
  • Organized
  • Task-focused

Goals

  • Become a senior Salesforce architect
  • Contribute to an open-source project
  • Achieve financial independence
  • Mentor junior developers on the team
  • Maintain a healthy work-life balance

Problems & frictions

  • Slow Salesforce test execution times are impacting deployment frequency.
  • Difficulty in accurately identifying which tests to run for specific code changes.
  • Managing the complexity of custom Apex code and its dependencies.
  • Balancing urgent bug fixes with planned feature development.
  • Keeping up with the constant evolution of the Salesforce platform.

Values

  • reliable delivery
  • clean source control
  • pragmatic automation
  • technical debt reduction
  • efficient processes

Interests

  • Salesforce DX
  • GitHub Actions
  • developer productivity
  • CI/CD pipelines
  • Apex performance optimization

Media habits

  • Subscribes to Salesforce developer blogs (e.g., Salesforce Ben, Apex Hours)
  • Watches technical YouTube channels for coding tips
  • Listens to tech podcasts during his commute
  • Active on Stack Overflow and Salesforce Developer Community forums
  • Reads tech news sites like Hacker News and The Verge

Questions & answers

Jeffrey Mann’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying LATdx (https://latdx.com/) this month? Be specific about how you handle this today. Also say the maximum you would pay per month in USD (0 if nothing).

    What would stop me from trying LATdx this month? Primarily, it's the manual effort involved today. I maintain a detailed spreadsheet mapping Apex classes to features to determine which tests to run. The idea of LATdx automating this selection based on code changes is appealing. The caching feature also sounds promising for speeding things up. However, I'd need to understand how it handles metadata-only changes, as the description mentions it's not used for selection yet, which could be a limitation. If it proves to significantly reduce our test times without introducing new complexities, I'd consider paying $50 per month.
    View answer & full research →
Keep exploring

What would you ask next?

Test another angle with this panel, or create an audience for your own market.