1. SUMMARY This reads like a typical early-stage startup posting that emphasizes flexibility and intensity over clearly defined responsibilities. Based on the wording, you should expect broad ownership across the stack, shifting priorities, and periods of long hours. The posting markets perks like "competitive salary" and "unlimited PTO," but it provides no concrete details about compensation, expected hours, equity, remote work, or benefits. Given your priorities (salary and work-life balance) and the fact that you're currently employed with another interview in progress, you're in a solid position to ask for specifics before making any commitment. 2. RED AND GREEN FLAGS 🚩 Red flags "Fast-paced startup" Usually means priorities change frequently, processes are still evolving, and workloads can fluctuate significantly. "Must be a rockstar" This is marketing language rather than a meaningful job requirement. It often signals expectations of exceptional output without defining success objectively. "Willing to wear many hats" Expect responsibilities beyond traditional full-stack development (DevOps, customer support, infrastructure, product discussions, interviewing, etc.). Ask what percentage of time is actually spent coding. "Competitive salary" This is too vague to evaluate. Competitive compared to what? Without a salary range, it's impossible to know whether it aligns with the market. "Unlimited PTO" This can be a good benefit, but it doesn't guarantee people actually take vacation. In some companies, employees take less time off because there is no defined allowance. Ask how much PTO employees actually used over the past year. "Occasional weekend work during crunch" The key unknown is what "occasional" and "crunch" mean. For one company, that's twice a year. For another, it's every month. This deserves concrete examples. ✅ Green flags The posting explicitly mentions weekend work instead of pretending it never happens. Transparency is better than discovering this after joining. Early-stage startups can offer broad technical ownership, faster learning, and greater influence over architecture and product decisions if that's something you value. 3. READING BETWEEN THE LINES Based on the language, you should assume: Your role boundaries may be intentionally broad. You'll likely be expected to solve problems outside your formal job description. Deadlines may occasionally override normal work hours. Success may be measured more by outcomes than by hours worked—but that can also blur work-life boundaries. The biggest things that should be put in writing are: Exact base salary (or salary range). Equity amount, vesting schedule, and any exercise terms. Expected weekly hours. Remote, hybrid, or in-office expectations. How often "crunch" has occurred over the last 12 months. Whether weekend work is compensated or balanced with time off. How unlimited PTO is actually used in practice (average days taken). Title, reporting structure, and performance review process. 4. YOUR LEVERAGE Given your situation: You're currently employed, so you don't need to accept unfavorable terms quickly. You have another interview underway, which gives you credible—not exaggerated—alternatives. With 6 years of experience, you're likely in the mid-to-senior market where experienced full-stack engineers remain valuable, especially if they can contribute across multiple areas. Since your priorities are salary and work-life balance, negotiate in this order: Base salary (highest priority). Clarify expectations around hours and weekend work. PTO usage expectations and flexibility. Equity, if offered. Title, if appropriate. Because the posting already hints at high expectations ("many hats," weekend crunch), it's reasonable to ask for compensation that reflects that scope rather than accepting vague assurances. Questions you should ask because key details are missing: What is the base salary range? Is there equity? If so, how much and under what vesting terms? What does a typical workweek look like? How many weekends did the engineering team work in the past year? What does "competitive salary" mean for this role? Is the role remote, hybrid, or on-site? How much PTO did engineers actually take last year? What benefits are included (healthcare, retirement, bonuses, learning budget)? 5. WHAT TO SAY Salary negotiation Thank you for the offer and for walking me through the role. I'm excited about the opportunity, especially the chance to have broad technical ownership. Before moving forward, I'd like to discuss compensation. Given my six years of full-stack experience and the wide scope of responsibilities described, I'd be looking for a higher base salary. Is there flexibility in the compensation package? Fallback line If the base salary has limited flexibility, I'd appreciate discussing other ways to make the overall package more competitive, such as additional equity, a performance-based salary review after six months, or clearer expectations around workload and weekend commitments. This is practical career guidance, not legal or financial advice; review any contract terms carefully before signing.