Founding Software Engineer

SageReport Founding Engineer Remote (US timezones) $200-250k 2.5% equity

We build AI tools for school-based clinicians - report generation IEP writing case management and more. There are 160000 school-based clinicians in the US all drowning in paperwork and unsupported by technology. Were giving them their time back so they can focus on the kids they serve. Were improving paperwork compliance to potentially save districts millions in legal exposure. There is currently no direct competition.

Traction: One unsolicited Facebook post from a tester 200 beta tester signups within the day. A partner district with 55 psychs fully onboarded and surveys indicating near-ceiling Net Promoter Scores and Product Market Fit. Sixty nationwide beta testers onboarding now. Users emailing us regularly saying this is changing their lives. Launching in 2 months. Were not marketing yetits just coming to us.

Were looking for our first engineering hire. Founding engineer role. Youd be the second technical person US-based ensuring the technical side isnt a single point of failure.

Tasks

• Frontend: React TypeScript Vite Tailwind CSS
• Backend: Firebase (Firestore Auth Functions Storage)
• We use AI tooling heavily in development and applicant should prefer this method

Modern but not exotic. If youre an experienced web developer youll be productive quickly.

Looking for: 10 years experience. Comfortable remote. Autonomous. Sees things through to done. Brings good energy to a small team that genuinely gets along and has mutual respect.

$200-250k depending on experience. 2.5% equity.

Full details on our website /engineering.

This is our first engineering hire. A founding engineer role.

The technical side is currently one person. We need a senior engineer in US timezones to share the load extend coverage and make sure the technical side of the company isnt a single point of failure. This isnt join a team. Youd be helping build the team.

Day-to-day:

Were async-first. Slack Linear PRs. One or two sync calls per week (1-2 hours) unless something urgent comes up likely more with product side following launch. 80-90% of your day should be focused building. The rest is communication code review occasionally handling support issues.

No formal sprints. You take the next important thing you ship it you move on.

For bigger changes we write short design docs: something you can put together in a day then async back-and-forth to sanity-check scope and approach. Were not looking for 22-step task breakdowns. We want to know whats affected what the risks are and that weve thought it through. For smaller things just do it maybe a quick Slack message if there are real tradeoffs to weigh.

Early days vs. later:

In your first weeks youll be reading code getting familiar with the system and finding your footing. We wont have a formal onboarding curriculum youll be able to orient yourself and identify where you can start contributing. Once familiar well have more structure and rhythm. Youll be building features and fixing bugs in focused stretches. Still lightweight on process but with clearer patterns.

Requirements

Experience and disposition:

• 10-15 years of experience. Youve worked on enough projects to have good judgment about tradeoffs.
• Youve been remote for a while and it works for you.
• Youre autonomous. You can take a problem figure out the approach and drive it to completion without a lot of oversight.
• You close loops. When you pick something up you see it throughtested deployed communicated.
• Youre technically broad. You understand how things actually workauth databases networking performance securitynot just how to use the abstractions. Were a small team working with sensitive data in schools; we take security seriously and need someone who does too.
• Youre steady. Startups are unpredictable but you can handle stress and dont add to the chaos. We can get tired but the vibes are good.

On AI tooling:

We use AI heavily in development. Its not a gimmick its core to how we move quickly with a small team. Working with AI tooling requires ongoing attention and adaptation but we believe it significantly accelerates whats possible. We expect any new team member to be comfortable working this way. If youre skeptical or prefer to avoid AI-assisted development thats a legitimate choice but were probably not the right fit.

Nice to have:

• TypeScript/JavaScript experience
• React experience
• Comfort with CSS (though not absolutely necessary)
• Firebase/Firestore (youll pick it up quickly if youre solid generally)

What probably wont work

The following is intentionally direct because it saves everyone time:

If you prefer detailed specs before starting work. We write lightweight design docs for bigger efforts but you wont get comprehensive requirements handed to you. If youre most comfortable in environments with well-defined workflows and clear handoffs our pace will feel youre not sure remote works for you. Fully remote isnt for everyone. Some people thrive some struggle with isolation or self-direction. If you havent done it before this probably isnt the role to find out. We need someone who already knows they do well in this setup.

Benefits

Equity: 2.5% with room to negotiate based on experience and your cash/equity preference. Standard 4-year vest 1-year cliff.

Benefits: Health/Vision/Dental Paid Vacation - Were building out a proper benefits package. Its not fully formalized yet but it will be. Happy to discuss where were : Fully timezones required.

If youve spent years at companies where you had less ownership than you wanted less autonomy than you could handle and less meaning in the work than you hoped for this might be what youre looking for.

Were small. Youd have real impact. The mission is tangible: school teams are overwhelmed and at-risk kids fall through the cracks as a result. Were helping fix that.

Its also demanding. Were a small team. If something breaks we fix it. If something needs building we build it. If you want structure and predictability this isnt it. That said we also have kids and understand that life happens and family comes first.

Message us with:

1. A bit about your background and why this interests you
2. A link to GitHub LinkedIn or whatever best shows your work
3. Any questions you have for us

Were not going to make you do a leetcode test. Well have a conversation look at some work together and figure out if this is a good fit.