/**
 * FAQ for the fractional CTO for early-stage SaaS service page.
 * Single source of truth for both the page content and FAQPage JSON-LD.
 */

export interface FaqItem {
    question: string;
    answer: string;
}

export const faqItems: FaqItem[] = [
    {
        question: 'What does "fractional CTO" actually mean?',
        answer: 'A fractional CTO is a part-time technical leader who provides CTO-level guidance without the cost of a full-time executive. You get senior architectural direction, decision review, and technical oversight on a retainer basis—typically 10–40 hours per month depending on your stage.',
    },
    {
        question: 'How involved are you in day-to-day engineering?',
        answer: 'I stay close enough to the code to keep decisions grounded. That means architecture reviews, participation in product and roadmap discussions, and hands-on refactoring when it matters. I’m not a slide-deck CTO—I operate as a technical partner who can both advise and implement.',
    },
    {
        question: 'Can you still contribute code?',
        answer: 'Yes. I contribute code when it’s the right leverage: critical refactors, foundation work, or examples that set standards for the team. The goal is to improve the system and transfer knowledge, not to become a permanent implementer.',
    },
    {
        question: 'How long do engagements usually last?',
        answer: 'Engagements are typically ongoing month-to-month. Some teams need fractional leadership for 6–12 months until they hire a full-time CTO; others stay on a retainer longer. We align on goals and revisit as your team grows.',
    },
    {
        question: 'Can you help with hiring engineers?',
        answer: 'Yes. I help define technical standards, review candidates, and advise on team structure. Hiring decisions are technical decisions—having a clear bar and someone who can assess it makes a big difference.',
    },
    {
        question: 'What tech stacks do you work with?',
        answer: 'I work with modern web and SaaS stacks—frontend, backend, and infrastructure. The principles of good architecture (separation of concerns, maintainability, stage-appropriate choices) transfer across stacks. We can discuss fit for your stack.',
    },
];
