Parakeet Health - Forward Deployed Engineer

• I’ll be straight with you: this role is probably not for you if customer calls feel like an interruption. They’re 15-20% of your week—not a tax on the job, but the job. The engineers who thrive here are the ones who leave a customer call energized, because they just learned something that’s going to make the product better or will delight the customer. • You’ll be a strong fit if you: • Are decisive when there’s no clean answer. You hold context on both sides and make judgment calls constantly. Sometimes that means telling the customer not now, sometimes it means escalating to the roadmap. You don’t wait for someone to tell you which one. • Have instinctual taste for what a good patient experience sounds like. You notice the thing that’s slightly wrong and then you can’t unknow it. You care about how that conversation feels to the person on the other end, not just whether it’s technically completed. • Don’t mind breadth. This role requires you to be effective across a wide surface area: customer context, product judgment, hands-on implementation, prototype building—often within the same hour. If you’d rather go deep on one hard technical problem and be left alone, the SWE role might be a better fit. If switching contexts is where you do your best work, this one’s for you. • Are honest about what you don’t know. “You might have a point; I may be wrong” should be something you’ve said recently and meant. We debate, we disagree, we challenge each other, but we do it with respect and with the assumption of good intent. Someone who can’t say they’re wrong won’t last long here, and frankly won’t enjoy it much either. • Don’t think unglamorous work is beneath you. Everyone rotates through the mundane stuff, no matter their seniority. The people who are great here do it without making it a thing. • You shouldn’t apply if you’ve never owned a project without someone assigning the tickets, or if you need a detailed roadmap to feel grounded. • Our honest assessment: this team skews high EQ. (Maybe too high. We probably need more shoelace staring.) But it’s also what makes working here feel different from most engineering environments: people genuinely like each other, go climbing together, form bands, bake for each other. The culture isn’t declared. It’s just what happens when you hire people you actually want to spend time with. • Cecilia has been here the longest and is, by general consensus, the heartbeat of the culture. She has a cat named Kiwi (she’s allergic to cats, so this is real commitment) and strong opinions about where to eat lunch. • Sumedh is our VP of Engineering who joined because he’d been watching what we were building and couldn’t stay on the sidelines. He’s senior enough to mentor everyone, but humble enough that nobody feels mentored. Also inexplicably West Coast for an East Coast guy. • Mimu joined a month ago and has already built a Claude onboarding agent that turns customer docs and meeting transcripts into a configured agent, shrinking implementation time from 5 days to 2 hours. In his spare time he’s building a 3D printed clock. (The clock was not on anyone’s roadmap.) • Tyrone commutes from Berkeley by bike every day, which is either impressive or unhinged depending on how you feel about the Bay Bridge. He loves climbing and will invite every new hire to go with him. • Tom runs Customer Success and will be your closest partner here. We took him to a client in Orlando once and they said it was the smoothest IT implementation they’d ever experienced (because: Tom). He’s technical enough to dig into a problem before passing it to engineering, funny enough to defuse a tense customer call, and somehow finds time to win Tuesday night softball championships. He also has a dachshund named Wanda who is, by any measurable metric, our most effective marketing asset. • Jung (co-founder, CEO) was patient number one at One Medical: he helped the founder build the first financial model before the practice had a single location. He also built the compliance program there from scratch, which is why we're already SOC 2 and HIPAA compliant. He has a PhD in operations research, which means the person running ops here thinks like an engineer. On the weekends you can find him at the farmers market selling kimchi in honor of his mother. • Eric (co-founder, CPO) was my college classmate, and we played on the same rec league basketball team before we decided to build together. He was working in ML/NLP before ChatGPT existed, which means he knew this business was possible before most people were even asking the question. Eric’s the reason we’re building in healthcare specifically… but I’ll let him tell you that story. • Me (Aaron, co-founder, CTO): Eric and I have been friends since before any of this existed. I think the best thing I can say about what it’s like to work with me is that he’s still here. • 2-5 years of engineering experience. Comfort working across the full stack: you don’t need to be a specialist, but you need to be able to move fast across frontend, backend, and integrations. Experience with Python is a plus. More important than any specific technology: you’ve shipped real things, you’ve talked to the people using them, and you’ve made judgment calls without waiting for someone to define the problem for you.