Product Owner

The role

A working product and a working deployment are two different things. You are the person who closes that gap.

You sit inside the client's head office. You get the deployment live, you get their teams using the dashboards, and you own whether the AI is returning something worth acting on. Every client is different: different languages on the floor, different store noise, different vocabulary for the same product, different CRM, different idea of what a good conversation looks like. The core platform does not change for each of them. You are the layer that makes it fit, and you are the one the client meets.

You are encouraged to spend time in stores. The engineers who do the best work here are the ones who have stood on a shop floor and watched where the pitch and the pipeline actually break. Nobody will make you go. You will also spend real time in the codebase, because you fix what you find rather than filing it.

What you build has a commercial edge to it. A pilot converts when the client sees the result they were promised, and an account grows when a second team inside it sees what is already sitting in their data. Both of those outcomes are yours to deliver, not somebody else's to chase.

How you will work

You design the deployment, you build it, and you own whether it holds up on a Saturday evening in a crowded store. Nobody hands you the plan, and nobody hands you the spec. You write both.

The decisions are yours. Which integration is worth the week, which vertical taxonomy needs building, what ships in the pilot and what waits, and when to tell a client that the thing they are asking for is the wrong thing to build. You go and find out what a client needs before anyone writes a line of code.

You will not be doing it alone. There are founders, AI engineers and product people around you, and they will build alongside you. What nobody will do is tell you what the client needs. That call is yours.

The work compounds if you do it well. What you learn on one deployment becomes a specification, then code, then a pattern the next one starts from. A year in, the deployments you designed should be running without you, and a new client should take a fraction of the time the first one did.

What you will do

Own the deployment end to end. Device provisioning, store connectivity, data flowing, first insight in front of the client. Get from kickoff to something real inside

the pilot window, and know by the halfway mark whether it is in trouble.

Get their HQ using it. A dashboard nobody opens is a failed deployment. Sit with the sales, marketing and L&D teams, show them what is in their own data, and

make sure the people who asked for this are actually looking at it every week.

Make the AI work on their floor. Their languages, their store noise, their product vocabulary. Benchmark transcription and speaker separation on their actual

audio, and fix what fails instead of explaining it away.

Build the vertical. Intent taxonomies, objection maps and prompt libraries for the category you are deployed into. A jewellery floor and an electronics floor do not

share a conversation model.

Wire it into their systems. CRM and POS integrations, so conversation data connects to what actually got sold and the insight can be checked against reality.

Build what the client asks for. Custom reports, dashboards and agents. Ground everything in source conversations and verify it before it ships, because a confident

wrong number costs an account.

Close the pilot. A pilot converts on results, not on effort. Know what the client agreed to judge this on, work backwards from it, and make sure the output in front of

their leadership at the end is the thing they asked for.

Grow the account. The same intelligence is worth something to marketing, L&D and category teams inside the same client. Spot which of them would benefit, show them what is already in their data, and hand a real opening to the account team.

Push it back into the product. Turn one-off client work into something the platform does by default, so the next deployment starts further ahead than this one did.

What we are looking for

Must have

• 0 to 5 years of experience. A consulting internship or an analyst role is the closest match to what this job actually asks for, but we care more about what you can do than where you did it
• Coding ability, ideally Python. Degree, internship, first job or your own projects. What we want to see is something you built that other people actually used
• Excel or Sheets at a real working level. A lot of the first conversation with a client happens in a spreadsheet before it ever happens in a dashboard
• The ability to explain a complicated idea simply. You will be taking AI output to people who do not think about models, and the explanation matters as much as the result
• Comfort at the boundaries. APIs, data pipelines, some frontend, some hardware when a device misbehaves
• An eye for where a deployment turns into more business, and the willingness to raise it yourself
• Heavy hands-on LLM usage. Prompts, evaluations, retrieval, and a clear view on where these tools break
• Fluent English and Hindi. A third Indian language counts for a lot, since the useful conversations happen on store floors and not only in HQ meeting rooms
• The instinct to go and find out what a client needs rather than waiting to be told

Good to have

Speech or audio work. Transcription, diarization, voice activity detection, or

anything that survives noisy real-world recording

Embedded or IoT experience, on ESP32 or similar

SQL and experience building things customers actually look at

Side projects, hackathons or internships where you shipped without a spec

and it worked

Content Writing Intern (Remote) — The Grey Post

🕐 Duration: 3 months | 💵 Stipend: Unpaid | 🌎 Location: Remote (USA Preferred)

About The Grey Post

TheGreyPost.com is a rising independent media platform covering U.S. news, global affairs, offbeat stories, lifestyle, culture, and deeply researched long-reads with a fresh voice. We are on a mission to publish content that matters — beyond the noise, beyond the ordinary.

Now, we’re inviting curious minds and sharp writers to join us on an exciting journey — as interns who want to be noticed.

🔍 What You’ll Do

• Research and write high-quality blog posts, opinion pieces, or news explainers (600–1500+ words).
• Contribute to content categories like Trending US News, States of Mind, The Feed, Deep Grey, and more.
• Use simple, clear, and engaging language — just like you're explaining something to a smart 8th grader.
• Learn basic SEO writing, headline optimization, and viral angles.
• Collaborate via Notion, Docs, Slack/Email — fully remote and async-friendly.

🧠 What You’ll Gain

• Real bylines on a fast-growing publication — boost your resume and portfolio!
• Mentorship on writing for the web, EEAT, and journalism standards.
• Letter of Recommendation & Certificate upon successful completion.
• Possibility of paid freelance work or contributor status after internship.
• Priority consideration for future editorial roles and features.

✅ You’re a Great Fit If…

• You’re based in the USA or have excellent knowledge of U.S. culture/news.
• You enjoy explaining complex things simply.
• You’re comfortable working independently and meeting deadlines.
• You're studying journalism, English, media, or simply love writing.

🎯 Bonus If You…

• Have experience with WordPress or Google Docs.
• Have written on Medium, Substack, your blog, or college magazine.
• Love writing about society, tech, politics, strange laws, or offbeat stories.

📩 How to Apply

Send us:

• A short bio (2-3 lines)
• 1 writing sample (or link to blog/Medium/portfolio)
• 2 content ideas you’d love to write for The Grey Post

👉 Email: thegreypost.com

Subject: “Content Writing Intern — [Your Name]”

Note: This is a volunteer-based, learning-focused internship. We value creative freedom, flexible hours, and personal growth over formal titles. Perfect for students and passionate writers who want to make their words matter.

Mandatory Skills

• Experience in Technical Writing/Information Development
• Experience writing topic-based and task-oriented documentation according to company style guidelines, requiring minimal editing from senior ID staff
• Experience developing enterprise systems software documentation for users and system administrators
• General knowledge on DITA concepts and IDCMS: ID (Information Development) Lifecycle and Content Management System
• Excellent interpersonal, communication, and teamwork skills
• MS Word

Roles, Responsibilities

• Effectively collaborate with project stakeholders to scope ID work
• Attend ID and Dev core meetings to understand ID requirements and plan, write and maintain concise but complete internal and external technical information (end user manuals, troubleshooting topics, compliance documentation, API descriptions) in compliance with client and team guidelines
• Independently research for relevant information and perform content reviews
• Work alongside multiple teams in a fast-paced agile environment towards providing high quality written content.
• Follow recommended style and business guidelines; using approved templates
• Being technically savvy in the areas of documentation by being hands-on with new and current product features
• Being proficient in usage of documentation tools & systems and aware of new technologies in documentation, industry best practices.
• Delivering the work allocated in time and with quality including translations and documentation build packages

• Minimum 3-4 years of experience with ETL tools, SQL, SSAS & SSIS
• Good understanding of Data Governance, including Master Data Management (MDM) and Data Quality tools and processes
• Knowledge of programming languages eg. JASON, Python, R
• Hands on experience of SQL database design
• Experience working with REST API
• Influencing and supporting project delivery through involvement in project/sprint planning and QA
• Working experience with Azure
• Stakeholder management
• Good communication skills

1. 0 to 2 years of experience into Java 6/7/8, J2EE, EJB, Servlets, JSP, JDBC, LOG4J, SQL, PL/SQL, XML, XSLT, JSON,
2. Good to have strong experience in Core Java SpringBoot, Spring framework
3. knowledge of Spring MVC, Spring REST, JDBC Templates
4. Knowledge of Java/J2EE Design patterns
5. knowledge of implementation of WebServices like REST will be added advantage
6. Good knowledge of Relational Databases like MySQL, PostgreSQL, MS SQL Server with complex SQL Queries, Stored Procedure, Triggers
7. Knowledge of Unit Test Cases is added advantage
8. Knowledge of build tools like Maven, Gradle, Ant
9. Knowledge of any one or more of MongoDB, Cassandra, Neo4J, Redis, Kafka, ActiveMQ, Caches, Microservices will be a major plus
10. Good to have knowledge of ORM like Hibernate
11. Knowledge and experience in nodejs backend will be added advantage

Requirements :

1. Must be a good team player and self-motivated Individual
2. Very Strong analytical abilities and interpersonal skills
3. Strong verbal and written communication skills with other developers and business clients
4. High commitment levels

About Alore

Alore brings revenue velocity to businesses by being their dependable growth operating system.

For further information on what Alore can do for growing businesses, please visit http://alore.io">alore.io

Alore is based out of Singapore with an office at Bangalore.

Who should NOT apply for this job

• If you are looking for a 100% hike in your salary but can't commit to what value you will bring on the table
• If you never read books
• If you jump companies every 11-12 months
• If you are not comfortable working on Saturdays
• If you have less than 2 years of experience
• If you have more than 4 years of experience
• If you have never worked in a product-led company

CTC:
5.5-7.5 LPA based on experience and on performance in the interview round (70% Fixed - 30% Variable Incentive based on delivery schedule) (We do ZERO deductions since the salary will be paid from Singapore)

About the Role:
We are looking for a Front-End Web Developer who is motivated to combine the art of design with the art of programming. Responsibilities will include translation of the UI/UX design wireframes to actual code that will produce visual elements of the application. You will work with the UI/UX designer and bridge the gap between graphical design and technical implementation, taking an active role on both sides and defining how the application looks as well as how it works.

Responsibilities:

• Develop new user-facing features
• Build reusable code and libraries for future use
• Ensure the technical feasibility of UI/UX designs
• Optimize application for maximum speed and scalability
• Assure that all user input is validated before submitting to the back-end
• Collaborate with other team members and stakeholders

Requirements:

• Min 2 years experience
• Max 3 years of experience in Web development
• Proficient understanding of Angular 2+
• Proficient understanding of web markup, including HTML5 CSS3
• Proficient understanding of client-side scripting and JavaScript frameworks, including jQuery
• Proficient understanding of cross-browser compatibility issues and ways to work around them.
• Proficient understanding of code versioning tools, such as (GitHub, GitLab)