SaaS Developer
for section headings. Sections: About the role? Actually we have "Who are we?" and "Who are you?" etc. We need to decide headings: maybe "About the company", "About the role", "Responsibilities", "Requirements", "Benefits", "Pay", "Schedule". We must include only sections with real specific content. The posting includes: description of company (Who are we?), description of ideal candidate (Who are you?), Bonus level unlock (nice-to-have), Responsibilities, Requirements, Other Details (title, Hours, Benefits...), location info, flexible hours, remote options. No explicit pay or benefits details. So we should not create Pay or Benefits sections unless stated. There's mention "Other Details...title, Hours, Benefits..." but no specifics. So we should not create Benefits or Pay sections. Hours: they say "Hours are flexible." That's specific enough for Schedule? It says schedule: flexible hours. So we can include a Schedule section with that detail. Benefits: not specified, so omit. Pay: not specified, omit.
We need to use for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate, duplicated lines, application instructions, cookie/navigation/legal/EEO etc. Also remove the repeated sections (the posting appears duplicated). We need to combine unique content.
Let's extract substantive content:
- Company intro: "We are an “old startup”. We recently spun-off from muvee, one of the pioneering global software startups from Singapore. muvee invented automatic video editing in 2002, garnering 26 patents in the process…and now we at photobook.ai are bringing all that smart storytelling goodness to automate the creation of photobooks. Our SDK currently powers photobook companies in the US, UK, Belgium, Japan, Mexico, Brazil, Kenya and South Africa. Next stop, China, Germany and Korea! So yeah, we are kind of global. We are just missing JB, Bintan, and Batam. #sarcasm The code we write typically gets pre-installed on gazillions of mobile phones (500m and counting). Not bad for a bunch of geeks coding from the little red dot."
- Ideal candidate description: "You are an SaaS (whatever buzzword floats your boat) aficionado. Each morning as you brew your coffee, you subconsciously map out solutions of all the unique flavors in your JSBeans which you quantize into diagrams, then pave solutions along your way, still sleepy-eyed to the washroom, then mentally code for the feature to your dreary office. When you arrive, you avoid passing your boss by calling your mental architectures and calculation algorithms whilst you are in your own world, with noise-canceling headphones, shutting your mind from the world’s chaos as you find escape in Node tech talks, Noisecore, Neumann, or whichever samples of n. Like the ever-evolving realm of an unkempt git repo, you are constantly curious and always learning new stuff, finding patterns, repeats, short-cuts, and even new languages and techniques."
- Bonus level unlock: "You will definitely score deep respect if you can work with Alicloud, ReactJS, play 3 musical instruments, are a photography enthusiast, are a soccer-mom with 2 kids, with pink-hair, tats+piercings and don’t need to sleep…ok, it’s highly unlikely we will find all the above in a single freak, but hey, prove us wrong!"
- Responsibilities: "You will be a part of a growing SaaS team that centers around developing solutions for print management, image rendering, and photobook-making, amongst other services. You will be fully immersed in product discussions and help build regional/global solutions for communications between frontend platforms, other backend services, AI technologies, printers, and their clients. Our customers rely on our solutions to radically speed up their workflow in various verticals, including school-yearbooks, sports photography, wedding studios, safaris, theme parks and plain old regular iPhone photography on a trip to wherever… We always hire smart people we can mold, so various levels are being considered for this position."
- Requirements: "Familiarity and expertise in the following areas or domains: Primarily NodeJS, RESTful APIAWS services (Lambda, API Gateway, DynamoDB, EC2, S3)Serverless architectureSaaS solutions and architectures Super-curious Bachelor’s Degree level candidates in Computer Science, Engineering and Mathematics with interest and experience in image processing can also apply. You will be working closely with a team of very experienced software engineers who are willing to share and mentor you."
- Other Details: "We believe in finding the right person; everything else is negotiable. You can have any title you want, we don’t care for “ranks” so you can call yourself the Chief SaaS Monkee, or simply “The Caffeine Filter Dude/Dudette”. In Singapore, we work out of a large private WeWork office at City House (opposite Lau Pa Sat). But we are looking for someone in Bandung to work at BLOCK71 (Jl. Ir. H. Djuanda) with the rest of the SaaS team. Hours are flexible. We are even open to hiring mothers who need to work from home a few days a week, but want to keep current and practice their craft!"
We should not include application instructions (the form etc). Also remove duplicated lines.
Now decide sections:
- About the company (maybe "About the role"? Actually "Who are we?" is about company. Could use heading "About the company" or "About the role"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They gave examples but we can use any of those. Since we have company description, maybe "About the role" is not appropriate. Could use "About the company" but not in list. However they said use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It seems they expect those headings; but we can also use other headings? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, not exclusive. But to be safe, we can stick to those headings where applicable. We have Responsibilities, Requirements. We have Schedule (flexible hours). We have maybe Skills? Could list technical skills. But we already have Requirements includes skills. Could create a Skills section from the bonus unlock? Might be thin. Better to keep only sections with substantive content: Responsibilities, Requirements, Schedule. Also maybe "About the company" as a heading but not in examples; risk. Could use "About the role" to encompass company description and role description? The role description includes responsibilities etc. But we already have separate sections. Could put company intro under "About the role". Might be acceptable.
Let's decide: Use headings: About the role, Responsibilities, Requirements, Schedule.
- About the role: combine company description and ideal candidate description and bonus unlock? Might be too much but okay.
But we need to avoid filler. All content is substantive.
We'll output:
About the role
We are an “old startup”. We recently spun-off from muvee, one of the pioneering global software startups from Singapore. muvee invented automatic video editing in 2002, garnering 26 patents in the process…and now we at photobook.ai are bringing all that smart storytelling goodness to automate the creation of photobooks. Our SDK currently powers photobook companies in the US, UK, Belgium, Japan, Mexico, Brazil, Kenya and South Africa. Next stop, China, Germany and Korea! So yeah, we are kind of global. We are just missing JB, Bintan, and Batam. #sarcasm The code we write typically gets pre-installed on gazillions of mobile phones (500m and counting). Not bad for a bunch of geeks coding from the little red dot.
You are an SaaS (whatever buzzword floats your boat) aficionado. Each morning as you brew your coffee, you subconsciously map out solutions of all the unique flavors in your JSBeans which you quantize into diagrams, then pave solutions along your way, still sleepy-eyed to the washroom, then mentally code for the feature to your dreary office. When you arrive, you avoid passing your boss by calling your mental architectures and calculation algorithms whilst you are in your own world, with noise-canceling headphones, shutting your mind from the world’s chaos as you find escape in Node tech talks, Noisecore, Neumann, or whichever samples of n. Like the ever-evolving realm of an unkempt git repo, you are constantly curious and always learning new stuff, finding patterns, repeats, short-cuts, and even new languages and techniques.
Bonus level unlock: You will definitely score deep respect if you can work with Alicloud, ReactJS, play 3 musical instruments, are a photography enthusiast, are a soccer-mom with 2 kids, with pink-hair, tats+piercings and don’t need to sleep…ok, it’s highly unlikely we will find all the above in a single freak, but hey, prove us wrong!
Then Responsibilities as - items.
Responsibilities list:
- Part of a growing SaaS team that centers around developing solutions for print management, image rendering, and photobook-making, amongst other services.
- Fully immersed in product discussions and help build regional/global solutions for communications between frontend platforms, other backend services, AI technologies, printers, and their clients.
- Customers rely on our solutions to radically speed up their workflow in various verticals, including school-yearbooks, sports photography, wedding studios, safaris, theme parks and plain old regular iPhone photography on a trip to wherever…
- We always hire smart people we can mold, so various levels are being considered for this position.
We'll put each as
- .
Requirements: list:
- Familiarity and expertise in the following areas or domains:
- Primarily NodeJS
- RESTful API
- AWS services (Lambda, API Gateway, DynamoDB, EC2, S3)
- Serverless architecture
- SaaS solutions and architectures
- Super-curious Bachelor’s Degree level candidates in Computer Science, Engineering and Mathematics with interest and experience in image processing can also apply.
- You will be working closely with a team of very experienced software engineers who are willing to share and mentor you.
We could format as nested lists but simpler: each bullet as
- . For the sub-items we can include them in same
- with commas.
Schedule:
Hours are flexible. We are even open to hiring mothers who need to work from home a few days a week, but want to keep current and practice their craft!
We should not include location details? That's substantive but not under any heading. Could include under About the role or maybe a separate section "Location". But not in examples. Could add a under About the role about location. However we already have location info: "In Singapore, we work out of a large private WeWork office at City House (opposite Lau Pa Sat). But we are looking for someone in Bandung to work at BLOCK71 (Jl. Ir. H. Djuanda) with the rest of the SaaS team." That's substantive. We should include it somewhere. Perhaps add a
after About the role or as part of About the role.
Let's add a paragraph under About the role after the bonus unlock: location info.
Now ensure no duplicated content.
Now produce HTML fragment.
Check for any
- for any list of duties/requirements/benefits. Use
for prose. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate, duplicated lines, application instructions, cookie/navigation/legal/EEO etc. Also remove the repeated sections (the posting appears duplicated). We need to combine unique content. Let's extract substantive content: - Company intro: "We are an “old startup”. We recently spun-off from muvee, one of the pioneering global software startups from Singapore. muvee invented automatic video editing in 2002, garnering 26 patents in the process…and now we at photobook.ai are bringing all that smart storytelling goodness to automate the creation of photobooks. Our SDK currently powers photobook companies in the US, UK, Belgium, Japan, Mexico, Brazil, Kenya and South Africa. Next stop, China, Germany and Korea! So yeah, we are kind of global. We are just missing JB, Bintan, and Batam. #sarcasm The code we write typically gets pre-installed on gazillions of mobile phones (500m and counting). Not bad for a bunch of geeks coding from the little red dot." - Ideal candidate description: "You are an SaaS (whatever buzzword floats your boat) aficionado. Each morning as you brew your coffee, you subconsciously map out solutions of all the unique flavors in your JSBeans which you quantize into diagrams, then pave solutions along your way, still sleepy-eyed to the washroom, then mentally code for the feature to your dreary office. When you arrive, you avoid passing your boss by calling your mental architectures and calculation algorithms whilst you are in your own world, with noise-canceling headphones, shutting your mind from the world’s chaos as you find escape in Node tech talks, Noisecore, Neumann, or whichever samples of n. Like the ever-evolving realm of an unkempt git repo, you are constantly curious and always learning new stuff, finding patterns, repeats, short-cuts, and even new languages and techniques." - Bonus level unlock: "You will definitely score deep respect if you can work with Alicloud, ReactJS, play 3 musical instruments, are a photography enthusiast, are a soccer-mom with 2 kids, with pink-hair, tats+piercings and don’t need to sleep…ok, it’s highly unlikely we will find all the above in a single freak, but hey, prove us wrong!" - Responsibilities: "You will be a part of a growing SaaS team that centers around developing solutions for print management, image rendering, and photobook-making, amongst other services. You will be fully immersed in product discussions and help build regional/global solutions for communications between frontend platforms, other backend services, AI technologies, printers, and their clients. Our customers rely on our solutions to radically speed up their workflow in various verticals, including school-yearbooks, sports photography, wedding studios, safaris, theme parks and plain old regular iPhone photography on a trip to wherever… We always hire smart people we can mold, so various levels are being considered for this position." - Requirements: "Familiarity and expertise in the following areas or domains: Primarily NodeJS, RESTful APIAWS services (Lambda, API Gateway, DynamoDB, EC2, S3)Serverless architectureSaaS solutions and architectures Super-curious Bachelor’s Degree level candidates in Computer Science, Engineering and Mathematics with interest and experience in image processing can also apply. You will be working closely with a team of very experienced software engineers who are willing to share and mentor you." - Other Details: "We believe in finding the right person; everything else is negotiable. You can have any title you want, we don’t care for “ranks” so you can call yourself the Chief SaaS Monkee, or simply “The Caffeine Filter Dude/Dudette”. In Singapore, we work out of a large private WeWork office at City House (opposite Lau Pa Sat). But we are looking for someone in Bandung to work at BLOCK71 (Jl. Ir. H. Djuanda) with the rest of the SaaS team. Hours are flexible. We are even open to hiring mothers who need to work from home a few days a week, but want to keep current and practice their craft!" We should not include application instructions (the form etc). Also remove duplicated lines. Now decide sections: - About the company (maybe "About the role"? Actually "Who are we?" is about company. Could use heading "About the company" or "About the role"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They gave examples but we can use any of those. Since we have company description, maybe "About the role" is not appropriate. Could use "About the company" but not in list. However they said use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It seems they expect those headings; but we can also use other headings? The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, not exclusive. But to be safe, we can stick to those headings where applicable. We have Responsibilities, Requirements. We have Schedule (flexible hours). We have maybe Skills? Could list technical skills. But we already have Requirements includes skills. Could create a Skills section from the bonus unlock? Might be thin. Better to keep only sections with substantive content: Responsibilities, Requirements, Schedule. Also maybe "About the company" as a heading but not in examples; risk. Could use "About the role" to encompass company description and role description? The role description includes responsibilities etc. But we already have separate sections. Could put company intro under "About the role". Might be acceptable. Let's decide: Use headings: About the role, Responsibilities, Requirements, Schedule. - About the role: combine company description and ideal candidate description and bonus unlock? Might be too much but okay. But we need to avoid filler. All content is substantive. We'll output:
About the role
We are an “old startup”. We recently spun-off from muvee, one of the pioneering global software startups from Singapore. muvee invented automatic video editing in 2002, garnering 26 patents in the process…and now we at photobook.ai are bringing all that smart storytelling goodness to automate the creation of photobooks. Our SDK currently powers photobook companies in the US, UK, Belgium, Japan, Mexico, Brazil, Kenya and South Africa. Next stop, China, Germany and Korea! So yeah, we are kind of global. We are just missing JB, Bintan, and Batam. #sarcasm The code we write typically gets pre-installed on gazillions of mobile phones (500m and counting). Not bad for a bunch of geeks coding from the little red dot.
You are an SaaS (whatever buzzword floats your boat) aficionado. Each morning as you brew your coffee, you subconsciously map out solutions of all the unique flavors in your JSBeans which you quantize into diagrams, then pave solutions along your way, still sleepy-eyed to the washroom, then mentally code for the feature to your dreary office. When you arrive, you avoid passing your boss by calling your mental architectures and calculation algorithms whilst you are in your own world, with noise-canceling headphones, shutting your mind from the world’s chaos as you find escape in Node tech talks, Noisecore, Neumann, or whichever samples of n. Like the ever-evolving realm of an unkempt git repo, you are constantly curious and always learning new stuff, finding patterns, repeats, short-cuts, and even new languages and techniques.
Bonus level unlock: You will definitely score deep respect if you can work with Alicloud, ReactJS, play 3 musical instruments, are a photography enthusiast, are a soccer-mom with 2 kids, with pink-hair, tats+piercings and don’t need to sleep…ok, it’s highly unlikely we will find all the above in a single freak, but hey, prove us wrong!
Then Responsibilities as- items. Responsibilities list: - Part of a growing SaaS team that centers around developing solutions for print management, image rendering, and photobook-making, amongst other services. - Fully immersed in product discussions and help build regional/global solutions for communications between frontend platforms, other backend services, AI technologies, printers, and their clients. - Customers rely on our solutions to radically speed up their workflow in various verticals, including school-yearbooks, sports photography, wedding studios, safaris, theme parks and plain old regular iPhone photography on a trip to wherever… - We always hire smart people we can mold, so various levels are being considered for this position. We'll put each as
- . Requirements: list: - Familiarity and expertise in the following areas or domains: - Primarily NodeJS - RESTful API - AWS services (Lambda, API Gateway, DynamoDB, EC2, S3) - Serverless architecture - SaaS solutions and architectures - Super-curious Bachelor’s Degree level candidates in Computer Science, Engineering and Mathematics with interest and experience in image processing can also apply. - You will be working closely with a team of very experienced software engineers who are willing to share and mentor you. We could format as nested lists but simpler: each bullet as
- . For the sub-items we can include them in same
- with commas.
Schedule:
Hours are flexible. We are even open to hiring mothers who need to work from home a few days a week, but want to keep current and practice their craft!
We should not include location details? That's substantive but not under any heading. Could include under About the role or maybe a separate section "Location". But not in examples. Could add aunder About the role about location. However we already have location info: "In Singapore, we work out of a large private WeWork office at City House (opposite Lau Pa Sat). But we are looking for someone in Bandung to work at BLOCK71 (Jl. Ir. H. Djuanda) with the rest of the SaaS team." That's substantive. We should include it somewhere. Perhaps add a
after About the role or as part of About the role. Let's add a paragraph under About the role after the bonus unlock: location info. Now ensure no duplicated content. Now produce HTML fragment. Check for any