Founding Design Engineer
for headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to parse the posting and extract relevant content.
The posting includes:
- About Noto (company description) – maybe not needed as a heading? Could be part of About the role? The instruction: use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content accordingly.
We have sections: About Noto (company description) – could be considered "About the role"? Actually "About the role" is separate from company description. The posting includes "About Noto" then "Team", "Location", "The Role", "Ideal Candidate", "Culture", "Compensation", "Interview Process", "Why Work With Us". We need to extract relevant info for the headings.
We should not include navigation/legal/EEO etc. There's none.
We need to preserve all substantive information.
We need to decide which headings to include:
- About the role: likely includes description of the role from "The Role" section.
- Responsibilities: list of duties from "You will:" bullet points.
- Requirements: maybe from "Ideal Candidate" bullet points (experience, full-stack ability, product judgment, etc.)
- Qualifications: maybe overlapping with Requirements; but we can treat "Ideal Candidate" as Requirements/Qualifications. Could also include "Bonus" as qualifications.
- Skills: maybe list of specific skills: React, Next.js, Node, Postgres, AI usage, etc.
- Benefits: from "Compensation" section: Competitive salary and equity worth caring about, 100% company-paid benefits, Lunch in the office and a stipend for your work setup, Company retreats.
- Pay: maybe not explicitly stated; they say Competitive salary and equity worth caring about. That's compensation, not specific number. Since we should not include sections with placeholder like "commensurate with experience" etc. But "Competitive salary and equity worth caring about" is somewhat vague but still substantive? It's not a specific number. The instruction: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. It says "Competitive salary and equity worth caring about" is stated, so we can include Pay section with that statement. However they also have Benefits section separate. Could combine compensation and benefits? But they ask separate headings for Benefits, Pay, Schedule. We'll include Pay with that statement.
- Schedule: from Location: "Four days in the office at Herald Square and one day remote", "One week per quarter working from anywhere", "Occasional travel for team offsites and customer visits". That's schedule info. So we can include Schedule section.
We also have Culture description maybe could be part of About the role or separate but not required headings. We could incorporate into About the role or maybe as a separate section but not in allowed headings list. Since only allowed headings are those, we should not add extra headings like Culture. We could fold culture into About the role or Responsibilities? Probably About the role can include some culture description. But we need to preserve all substantive information; we can include culture as a paragraph under About the role.
We also have Interview Process and Why Work With Us – could be omitted? The instruction: remove application instructions. Interview Process is application instructions? It's part of hiring process; maybe we should keep? The instruction says remove application instructions. Interview Process is likely application instructions, so we should remove it. Why Work With Us is also maybe promotional but could be kept? It's not a standard heading; we could fold into About the role or maybe omit as it's not required. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep that info somewhere. Could add as a paragraph under About the role or maybe under a generic section? Since we cannot add extra headings, we can incorporate into About the role as a paragraph.
Similarly, Team description could be part of About the role.
Location info we already used for Schedule.
Now we need to format.
We'll produce:
About the role
... (company description, team, location maybe? but location goes to schedule). We'll include company description, team, location? Actually location is schedule. We'll keep location in schedule.
So About the role paragraph: include Noto description, team description, role overview.
Then Responsibilities:
- each bullet from "You will:" list.
Then Requirements: maybe from Ideal Candidate bullet points (four or more years designing and building software products, full-stack ability, product judgment, care for words, comfort with ambiguity, bonus etc). We'll separate Requirements and Qualifications? Could treat Requirements as the must-haves, Qualifications as bonus? But we have both headings allowed. We'll put must-haves in Requirements, bonus in Qualifications.
Skills: list specific technical skills: React, Next.js, Node, Postgres, AI usage, etc.
Benefits: list from Compensation: 100% company-paid benefits, Lunch in the office and a stipend for your work setup, Company retreats.
Pay: Competitive salary and equity worth caring about.
Schedule: Four days in the office at Herald Square and one day remote; One week per quarter working from anywhere; Occasional travel for team offsites and customer visits.
We must ensure we don't repeat content.
Let's extract exact text.
Company description: "About NotoNoto is the AI-native operating system for after-school businesses: tutoring centers, music schools, sports academies, and dance studios. About 180,000 of these businesses operate in the U.S., and millions of kids pass through them every week.They’re run by people who are passionate about teaching but spend their evenings managing schedules, payroll, and parent emails—often in software built in 2011, or in spreadsheets and sticky notes.Noto replaces the entire stack with a modern platform for scheduling, billing, payroll, marketing, CRM, communications, classroom management, and student and parent portals. We bring the whole back office into one place, with AI agents that automate manual work instead of simply tracking it.A school that spends less time on paperwork can teach more kids, hire another teacher, and grow its business. Come help us build the best operating system for these small-business owners! (Fall 2026 team offsite: magic shows, lawn games, trivia, friendly competition, bartender-made drinks, and a cookout 🔥)"
Team: "We’re a team of about 20 in New York City: smart, collaborative, ambitious, and genuinely nice to work with.AJ Ding (CEO) — second-time founder who previously built an AI recruiting company. ML engineer and data scientist at Quora, Lyft, and Meta. Studied statistics at Yale and grew up in a family of small-business owners.Steve Wang (CTO) — former Head of Engineering at Nitra, an a16z-backed vertical SaaS company for doctors. Previously worked in data science and engineering at Lyft. Studied math at Harvard.We’ve raised $4M from Base10 Partners and South Park Commons."
Location: "Four days in the office at Herald Square and one day remoteOne week per quarter working from anywhereOccasional travel for team offsites and customer visits"
The Role: paragraph: "The founding design engineer will own how Noto looks, works, and reads. This is an opportunity to define the design foundation for a product our customers rely on all day—and to make it genuinely intuitive and delightful. You’ll combine design and engineering with strong product judgment, taste, and empathy for users, taking ideas from the first sketch through the shipped experience.Our users spend six hours a day in Noto across a wide range of workflows. The product has grown quickly, and some parts are more complex than they need to be. You’ll have the scope and ownership to bring clarity, cohesion, and craft to the entire experience."
Then bullet list under "You will:":
- Own the design of the entire product—from layouts and workflows to the words on every screen.
- Design and build your own projects end to end, from the UI to the database.
- Set the quality bar for design and shape other engineers’ work from early scoping through final polish.
- Identify the moments that confuse or slow down our customers, then redesign and build better solutions.
- Establish the components, patterns, and copy standards that define how the team builds.
Ideal Candidate bullet list:
- Four or more years designing and building software products
- Full-stack ability. You’re comfortable with our stack (React, Next.js, Node, and Postgres), can use AI to ship features end to end, and can tell when AI-generated code is wrong.
- Product judgment. You can take a messy workflow, such as rescheduling a missed lesson for a family with three kids, and make it simple. You can explain why your version works.
- Care for words and small details. Labels, error messages, empty states, and emails to parents matter to you as much as layout does.
- Comfort with ambiguity. Much of what you’ll work on starts with unstructured customer call notes. You go to the source, talk to the owner or front desk, and uncover the real problem.
- Bonus: you’ve been the first or only designer at a company, or you’ve designed complex operational software such as scheduling, billing, or admin tools.
- Interest in helping education businesses thrive
Culture paragraph: "As our first design engineer, you’ll have a huge impact on how we build our product and shape our design culture. Here’s what’s true today:Serve the customer. Our users run small businesses. We sit in their schools, attend their industry conferences, and take support calls ourselves. We get ideas by listening to our customers’ problems.Low ego. We make decisions collaboratively. Nobody wins an argument through seniority, including the founders. Good ideas come from whoever is closest to the problem.Ownership. You’ll own a large, mission-critical part of the product. It’s intense, but rewarding. Customers will send thank-you gifts and sing your praises when you ship something useful—and call for help on a Saturday if something goes wrong.Work ethic. Team members work 50–60-hour weeks. Some late nights and occasional weekends are expected. The role is about growth and impact. If you want to build something meaningful and grow quickly, let’s talk.Growth mindset. We attend industry conferences to connect with our users, learn, network, and push the boundaries of our craft."
Compensation: "Competitive salary and equity worth caring about100% company-paid benefitsLunch in the office and a stipend for your work setupCompany retreats"
Interview Process and Why Work With Us we may incorporate into About the role or omit? The instruction says remove application instructions. Interview Process is application instructions, so remove. Why Work With Us is promotional but could be considered part of "Why Work With Us" not a standard heading; we could incorporate into About the role as a paragraph about impact.
We'll include a paragraph about impact: "Our product makes a huge positive impact on business owners, educators, and their local communities. Watch our customer testimonial video at the bottom of our home page and see it for yourself.If you’re a designer who builds and want to own how a product people use all day looks, works, and reads, we’d love to meet you."
Now we need to ensure we don't repeat content.
Let's craft HTML.
We'll start with About the role paragraph combining company description, team, location? Actually location goes to schedule. We'll keep location out.
About the role paragraph: include N
for prose. We need to parse the posting and extract relevant content. The posting includes: - About Noto (company description) – maybe not needed as a heading? Could be part of About the role? The instruction: use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content accordingly. We have sections: About Noto (company description) – could be considered "About the role"? Actually "About the role" is separate from company description. The posting includes "About Noto" then "Team", "Location", "The Role", "Ideal Candidate", "Culture", "Compensation", "Interview Process", "Why Work With Us". We need to extract relevant info for the headings. We should not include navigation/legal/EEO etc. There's none. We need to preserve all substantive information. We need to decide which headings to include: - About the role: likely includes description of the role from "The Role" section. - Responsibilities: list of duties from "You will:" bullet points. - Requirements: maybe from "Ideal Candidate" bullet points (experience, full-stack ability, product judgment, etc.) - Qualifications: maybe overlapping with Requirements; but we can treat "Ideal Candidate" as Requirements/Qualifications. Could also include "Bonus" as qualifications. - Skills: maybe list of specific skills: React, Next.js, Node, Postgres, AI usage, etc. - Benefits: from "Compensation" section: Competitive salary and equity worth caring about, 100% company-paid benefits, Lunch in the office and a stipend for your work setup, Company retreats. - Pay: maybe not explicitly stated; they say Competitive salary and equity worth caring about. That's compensation, not specific number. Since we should not include sections with placeholder like "commensurate with experience" etc. But "Competitive salary and equity worth caring about" is somewhat vague but still substantive? It's not a specific number. The instruction: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. It says "Competitive salary and equity worth caring about" is stated, so we can include Pay section with that statement. However they also have Benefits section separate. Could combine compensation and benefits? But they ask separate headings for Benefits, Pay, Schedule. We'll include Pay with that statement. - Schedule: from Location: "Four days in the office at Herald Square and one day remote", "One week per quarter working from anywhere", "Occasional travel for team offsites and customer visits". That's schedule info. So we can include Schedule section. We also have Culture description maybe could be part of About the role or separate but not required headings. We could incorporate into About the role or maybe as a separate section but not in allowed headings list. Since only allowed headings are those, we should not add extra headings like Culture. We could fold culture into About the role or Responsibilities? Probably About the role can include some culture description. But we need to preserve all substantive information; we can include culture as a paragraph under About the role. We also have Interview Process and Why Work With Us – could be omitted? The instruction: remove application instructions. Interview Process is application instructions? It's part of hiring process; maybe we should keep? The instruction says remove application instructions. Interview Process is likely application instructions, so we should remove it. Why Work With Us is also maybe promotional but could be kept? It's not a standard heading; we could fold into About the role or maybe omit as it's not required. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep that info somewhere. Could add as a paragraph under About the role or maybe under a generic section? Since we cannot add extra headings, we can incorporate into About the role as a paragraph. Similarly, Team description could be part of About the role. Location info we already used for Schedule. Now we need to format. We'll produce:
About the role
... (company description, team, location maybe? but location goes to schedule). We'll include company description, team, location? Actually location is schedule. We'll keep location in schedule. So About the role paragraph: include Noto description, team description, role overview. Then Responsibilities:
- each bullet from "You will:" list. Then Requirements: maybe from Ideal Candidate bullet points (four or more years designing and building software products, full-stack ability, product judgment, care for words, comfort with ambiguity, bonus etc). We'll separate Requirements and Qualifications? Could treat Requirements as the must-haves, Qualifications as bonus? But we have both headings allowed. We'll put must-haves in Requirements, bonus in Qualifications. Skills: list specific technical skills: React, Next.js, Node, Postgres, AI usage, etc. Benefits: list from Compensation: 100% company-paid benefits, Lunch in the office and a stipend for your work setup, Company retreats. Pay: Competitive salary and equity worth caring about. Schedule: Four days in the office at Herald Square and one day remote; One week per quarter working from anywhere; Occasional travel for team offsites and customer visits. We must ensure we don't repeat content. Let's extract exact text. Company description: "About NotoNoto is the AI-native operating system for after-school businesses: tutoring centers, music schools, sports academies, and dance studios. About 180,000 of these businesses operate in the U.S., and millions of kids pass through them every week.They’re run by people who are passionate about teaching but spend their evenings managing schedules, payroll, and parent emails—often in software built in 2011, or in spreadsheets and sticky notes.Noto replaces the entire stack with a modern platform for scheduling, billing, payroll, marketing, CRM, communications, classroom management, and student and parent portals. We bring the whole back office into one place, with AI agents that automate manual work instead of simply tracking it.A school that spends less time on paperwork can teach more kids, hire another teacher, and grow its business. Come help us build the best operating system for these small-business owners! (Fall 2026 team offsite: magic shows, lawn games, trivia, friendly competition, bartender-made drinks, and a cookout 🔥)" Team: "We’re a team of about 20 in New York City: smart, collaborative, ambitious, and genuinely nice to work with.AJ Ding (CEO) — second-time founder who previously built an AI recruiting company. ML engineer and data scientist at Quora, Lyft, and Meta. Studied statistics at Yale and grew up in a family of small-business owners.Steve Wang (CTO) — former Head of Engineering at Nitra, an a16z-backed vertical SaaS company for doctors. Previously worked in data science and engineering at Lyft. Studied math at Harvard.We’ve raised $4M from Base10 Partners and South Park Commons." Location: "Four days in the office at Herald Square and one day remoteOne week per quarter working from anywhereOccasional travel for team offsites and customer visits" The Role: paragraph: "The founding design engineer will own how Noto looks, works, and reads. This is an opportunity to define the design foundation for a product our customers rely on all day—and to make it genuinely intuitive and delightful. You’ll combine design and engineering with strong product judgment, taste, and empathy for users, taking ideas from the first sketch through the shipped experience.Our users spend six hours a day in Noto across a wide range of workflows. The product has grown quickly, and some parts are more complex than they need to be. You’ll have the scope and ownership to bring clarity, cohesion, and craft to the entire experience." Then bullet list under "You will:": - Own the design of the entire product—from layouts and workflows to the words on every screen. - Design and build your own projects end to end, from the UI to the database. - Set the quality bar for design and shape other engineers’ work from early scoping through final polish. - Identify the moments that confuse or slow down our customers, then redesign and build better solutions. - Establish the components, patterns, and copy standards that define how the team builds. Ideal Candidate bullet list: - Four or more years designing and building software products - Full-stack ability. You’re comfortable with our stack (React, Next.js, Node, and Postgres), can use AI to ship features end to end, and can tell when AI-generated code is wrong. - Product judgment. You can take a messy workflow, such as rescheduling a missed lesson for a family with three kids, and make it simple. You can explain why your version works. - Care for words and small details. Labels, error messages, empty states, and emails to parents matter to you as much as layout does. - Comfort with ambiguity. Much of what you’ll work on starts with unstructured customer call notes. You go to the source, talk to the owner or front desk, and uncover the real problem. - Bonus: you’ve been the first or only designer at a company, or you’ve designed complex operational software such as scheduling, billing, or admin tools. - Interest in helping education businesses thrive Culture paragraph: "As our first design engineer, you’ll have a huge impact on how we build our product and shape our design culture. Here’s what’s true today:Serve the customer. Our users run small businesses. We sit in their schools, attend their industry conferences, and take support calls ourselves. We get ideas by listening to our customers’ problems.Low ego. We make decisions collaboratively. Nobody wins an argument through seniority, including the founders. Good ideas come from whoever is closest to the problem.Ownership. You’ll own a large, mission-critical part of the product. It’s intense, but rewarding. Customers will send thank-you gifts and sing your praises when you ship something useful—and call for help on a Saturday if something goes wrong.Work ethic. Team members work 50–60-hour weeks. Some late nights and occasional weekends are expected. The role is about growth and impact. If you want to build something meaningful and grow quickly, let’s talk.Growth mindset. We attend industry conferences to connect with our users, learn, network, and push the boundaries of our craft." Compensation: "Competitive salary and equity worth caring about100% company-paid benefitsLunch in the office and a stipend for your work setupCompany retreats" Interview Process and Why Work With Us we may incorporate into About the role or omit? The instruction says remove application instructions. Interview Process is application instructions, so remove. Why Work With Us is promotional but could be considered part of "Why Work With Us" not a standard heading; we could incorporate into About the role as a paragraph about impact. We'll include a paragraph about impact: "Our product makes a huge positive impact on business owners, educators, and their local communities. Watch our customer testimonial video at the bottom of our home page and see it for yourself.If you’re a designer who builds and want to own how a product people use all day looks, works, and reads, we’d love to meet you." Now we need to ensure we don't repeat content. Let's craft HTML. We'll start with About the role paragraph combining company description, team, location? Actually location goes to schedule. We'll keep location out. About the role paragraph: include N