Customer Care- Inbound Process

HR Intern – Job Description

Position: HR Intern

Company: Honeybee Digital

Location: Remote

Internship Type: Full-Time / Part-Time

Duration: 3 to 6 Months

About the Role

We are looking for a proactive and enthusiastic HR Intern to support our Human Resources team in recruitment, employee engagement, and administrative activities. This internship is a great opportunity for students or freshers who want practical exposure to HR operations and talent management.

Key Responsibilities

• Assist in sourcing and screening candidates through job portals and social media
• Schedule interviews and coordinate with candidates
• Maintain employee and candidate databases
• Support onboarding and documentation processes
• Help create job postings and internship listings
• Assist in employee engagement activities and internal communication
• Handle basic HR administrative tasks
• Coordinate with different departments for hiring requirements

Requirements

• Good communication and interpersonal skills
• Strong organizational and coordination abilities
• Basic knowledge of HR processes and recruitment
• Familiarity with Google Workspace/MS Office
• Positive attitude and willingness to learn
• Ability to handle confidential information professionally
• 
  

Preferred Skills

• Knowledge of recruitment platforms like LinkedIn, Indeed, or Internshala
• Basic understanding of HR policies and operations
• Social media communication skills are a plus

What You’ll Gain

• Hands-on experience in recruitment and HR operations
• Exposure to real-world hiring processes
• Mentorship from experienced HR professionals
• Internship Certificate
• Letter of Recommendation based on performance
• Opportunity for full-time placement after successful completion

Lead Product Engineer - Pod Captain 

A Little Bit About the Role

There is a version of this role that attracts the wrong person: a senior engineer who wants a title upgrade and a slightly bigger scope. That person will struggle here. The Lead PE is not a promotion for being a great individual engineer. It is a fundamentally different job.

Your success at this level is measured entirely by what your Island delivers — not by the quality of your own code. You will still write code, often the hardest and most risk-laden on the project: auth systems, payment integrations, data migrations, the things nobody else should touch. But that is a fraction of the role. The majority is managing delivery, owning the client relationship on the technical side, unblocking engineers before problems compound, and making scope calls under pressure with incomplete information.

You are also the technical and commercial bridge between your Island and the client. You own every piece of technical communication that goes to them — what is being built, what risks exist, what the honest timeline is. When a client pushes for something technically unsound, you push back directly and professionally, always with an alternative. When something breaks in production, you own the post-mortem process and the client receives it within 24 hours. You protect your team from unfiltered client pressure; you translate it into clear, actionable direction instead.

On top of delivery and client management, you are the AI operating standard for your Island. Every engineer on your pod uses Cursor and Claude within the rules you define. You set those rules before the first line of code is written, govern how they evolve, and you are accountable when AI-generated code ships without being understood.

If you are energised by all of that — by the accountability, by owning outcomes rather than tasks, by the combination of technical depth and people management — this role will suit you well. If you want to spend most of your time in code, this is not the right level.

AI Governance Expectation

You set the AI standard for your entire Island. If an engineer on your pod is shipping AI-generated code they do not understand, or underusing AI tools entirely, both are your problem to fix — not theirs alone.

At Lead level, AI governance means:

• Authoring the .cursorrules file before the first PR is opened. This defines how every engineer on the team writes code, uses Cursor, and structures prompts. You update it as the team learns, and you submit it to the Fountane Mainland at the close of every engagement.
• Evaluating new AI tools before they reach client code. You are the gate. A tool that looks useful in a demo can create untraceable technical debt in production. You decide what enters the workflow.
• Governing prompt discipline across the team: scoped prompts, codebase context hygiene, no AI-generated code that the author cannot explain line by line.
• Using Claude for architecture reasoning, sprint planning, risk documentation, and client-facing technical communication — not just Cursor for code generation. AI works at every layer of the Lead role, not just the coding layer.
• Staying ahead of the Golden Stack. You should know what Cursor and Claude can and cannot do at the codebase level better than anyone on your Island. When the Mainland updates the standard toolchain, you integrate the change into your Island’s workflow first.

Key Responsibilities

Technical Architecture & Standards Ownership

Design the full-stack architecture for every engagement before the first sprint starts: service boundaries, API contracts, database schema, state management strategy across web and mobile surfaces, and the security baseline. Author the .cursorrules file that governs how the entire Island writes code and uses AI. Own the highest-risk code personally — auth systems, payment integrations, live data migrations — these are not delegated regardless of workload. Enforce Mainland security standards across the entire codebase: input validation, correct auth scoping, safe data handling. If a security issue reaches production that was visible in a PR, that is a failure you own.

CE Prototype Gatekeeping

Review every Concept Engineer prototype before any engineer touches it. This is not a courtesy review — you have veto authority. If the scope is technically unrealistic for the sprint, the architecture is unbuildable as specified, or the prototype makes promises the codebase cannot keep, the sprint does not start until those are resolved. The time to surface a structural problem is before it is built, not after it is demoed. Produce a written checklist verdict for every prototype review — approved, approved with conditions, or blocked with reasons.

Client Technical Communication & Scope Ownership

Own all technical communication with the client directly. This means: what is being built each sprint, what risks exist and what is being done about them, honest timelines when estimates change, and clear explanations of technical decisions in plain language. Push back on risky or scope-expanding requests professionally and always with an alternative — “we cannot do X because Y; here is what achieves the same outcome.” Manage scope creep actively: every request that expands the engagement goes through you, gets assessed for impact, and is either absorbed, priced, or declined with a rationale. Renewal conversations are yours to lead in coordination with the CE.

Island Integration Audit

When a prospective client wants fractional augmentation — one or two roles rather than a full Island — you conduct the Island Integration Audit. This means evaluating their existing engineering team against Fountane Mainland SOPs: coding standards, AI tool usage, deployment practices, and documentation quality. If they pass, fractional deployment proceeds. If they do not, you produce a written audit report that either recommends full Island deployment or a Mainland upskilling programme. You are protecting your team’s velocity — a fractional deployment into a dysfunctional team destroys it.

Delivery & Velocity Management

Review the work cycle board every morning. Flag anything stuck, stale, or at risk before it becomes a client problem — not after. Communicate risks to the CE proactively with options, not just problems. Track every engineer’s billing hours: a shortfall spotted on Wednesday is a Thursday conversation, not a Friday surprise. If an engineer is consistently under-billing, that is either a workload problem, a capability problem, or a motivation problem — each has a different resolution and you are responsible for diagnosing which one it is.

Production Incident Ownership

When something breaks in production, you own the resolution process end to end: take technical lead, make the call on rollback vs. hotfix, communicate status to the client directly if the incident affects them, and own the post-mortem. The client receives the post-mortem within 24 hours of resolution — this is a hard commitment, not a target. The post-mortem covers: what happened, why it happened, what was done to fix it, and what structural change prevents recurrence. You produce it; it is not delegated to the engineer who caused the issue.

Automation & Infrastructure Boundary Arbitration

The Automation Engineer owns the test gates within the CI/CD pipeline. The Infrastructure Engineer owns the pipeline configuration itself. When these overlap and conflict — which they will — you arbitrate. The resolution must be documented in the Island’s .cursorrules and SOP onboarding document so the boundary does not need to be relitigated every sprint. This is not optional housekeeping; an unresolved boundary between these two roles is one of the most common sources of deployment failures on Islands.

Full Stack Ownership — Web & Mobile

You review and own work across the entire application layer: React / Next.js web frontends, React Native or Flutter mobile apps, Node.js / Python backends, and database schema. You cannot delegate a review of mobile code because you do not know mobile, or backend code because your background is frontend. If there is a gap in your full-stack depth, that is something to resolve before taking this role, not on the job.

People Management & Mentoring

Hold bi-weekly 1:1s with every engineer on the Island — focused on growth, blockers, and career direction, not status updates. Status belongs on the board; 1:1s are for the person. Address performance gaps early, directly, and specifically: a pattern spotted in week two is a conversation in week two, not month three. Protect the team from unfiltered client anxiety — absorb it, process it, and give the team clear direction instead of noise. If an engineer is struggling, that is your problem to solve before it becomes the client’s problem to notice.

Network Contribution

At the close of every engagement, submit to the Fountane Mainland: the .cursorrules file, all prompt templates used, a short retrospective on what worked and what did not, and any reusable patterns or scripts developed during the engagement. This is a Lead-level obligation, not a nice-to-have. The network’s collective capability grows through what Leads bring back from the field. An engagement that ends without a Mainland submission has left the network no smarter than it was before.

Qualifications

• 8+ years of software engineering experience, with at least two years in a role where you were accountable for delivery outcomes — not just your own code. You should be able to describe an engagement where something went wrong on your watch, what you did about it, and what you would do differently. If your experience is entirely individual-contributor, this role will be a difficult fit.
• Genuinely full stack across web and mobile: React / Next.js, React Native or Flutter, Node.js or Python, and database architecture including schema design and migrations. You review and own work across all of these surfaces — not just the ones you are most comfortable in.
• Hands-on, daily Cursor and Claude usage with the ability to set and enforce standards for how a team uses them — not just personal proficiency. You should be able to describe the .cursorrules file you would write for a standard SMB engagement and explain the decisions behind it.
• Proven ability to communicate technical risk and decisions directly to non-technical clients — not through a PM, directly, in plain language. You should be able to describe a client pushback you navigated and how you handled it.
• Experience managing scope on a real engagement: a client who wanted more than was in the contract, and how you resolved it without damaging the relationship or the team’s velocity.
• Has conducted security-aware architecture design: auth systems, input validation, safe data handling. You should be able to describe a security decision you made and why.
• Has led or coordinated a small engineering team — run 1:1s, addressed performance gaps, made scope calls under pressure. Management experience at a staffing agency or outsourcing firm counts if the accountability was real.
• Comfortable having direct, specific performance conversations early — not after the situation has compounded. You should be able to describe a time you addressed a performance issue at the first sign rather than waiting.
• Bachelor’s or Master’s in Computer Science or a related field, or equivalent experience.

About Fountane

Fountane is a technology ventures lab - one part product studio, one part startup engine. We build high-quality software and AI products for clients ranging from fast-moving startups to large enterprises, and we co-build and invest in new companies when we see the right opportunity.

Founded in 2017 and headquartered in Minneapolis, we have grown to 60+ people across four continents and were recognised as one of America’s fastest-growing companies, ranking No. 699 on the Inc. 5000 with 595% three-year growth.

We are serious about craft, direct about expectations, and operate at the frontier of AI-assisted engineering. Lead PEs here carry real authority and real accountability — over delivery, over people, and over client outcomes. If that combination is what you are looking for, this is the place.

Position: Team Lead – Data Engineering

Client: NucleusTeq

We are looking for an experienced Team Lead / Architect – Data Engineer to design, architect, and lead scalable cloud-based data platforms.

Key Responsibilities:

·     Design and architect scalable, high-performance data solutions.

·     Lead and mentor a team of data engineers.

·     Build and optimize large-scale data pipelines.

·     Drive architectural decisions and technical strategy.

·     Ensure data quality, governance, and security best practices.

·     Collaborate with cross-functional teams for end-to-end delivery.

Required Skills:

·     Strong hands-on experience in Java & Python.

·     Strong expertise in SQL and Big Data technologies.

·     Hands-on experience with Google Cloud Platform (GCP).

·     Experience with Apache Airflow for workflow orchestration.

·     Strong understanding of distributed systems and data architecture.

·     Experience in CI/CD pipelines (mandatory).

·     Experience in data warehousing and ETL processes.

·     Excellent leadership and stakeholder management skills.

Good to Have:

·     Experience with Dataflow (Apache Beam).

·     Experience designing enterprise-level data platforms.

·     Exposure to DevOps best practices.

Location: Bangalore

Experience: 5–10 years

Type: Full-time | On-site

Start: Immediate

Why this role exists

Most sales teams optimize for activity.

We optimize for outcomes and revenue density.

We are not selling a tool.

We are selling a new way enterprises operate with AI.

This role exists to:

• Win high-value enterprise accounts
• Convert POCs into long-term revenue
• Build accounts that scale from ₹2 Cr → ₹8 Cr ARR

What you’ll do

You will not just manage deals.

You will own revenue creation end-to-end.

1. Close net-new enterprise revenue

• Generate ₹30–50L MRR in net-new bookings by Series A close
• Focus on high-value accounts, not volume deals
• Drive deals from:
• First conversation → signed contract

2. Win Tier-1 insurance accounts

• Target and close at least one of:
• SBI Life Insurance, HDFC Life, ICICI Prudential Life Insurance
• or leading general insurers like
• New India Assurance, Bajaj Allianz General Insurance
• Build relationships with:
• CXOs
• Business heads
• Transformation leaders

3. Run high-conviction POC-driven sales

• Focus on winning strong POCs, not just pilots
• Ensure POCs:
• Are tightly scoped
• Deliver measurable outcomes
• Lead directly to expansion
• Drive clarity on:
• ROI
• Success criteria
• Conversion to long-term contracts

4. Build and expand enterprise accounts

• Create a roadmap to scale accounts from:
• 0 -> ₹2 Cr → ₹8 Cr ARR
• Identify:
• New use cases
• Cross-functional expansion opportunities
• Own:
• Renewals
• Upsell
• Expansion strategy

5. Open new verticals

• Identify and penetrate new industry segments
• Build initial proof points and reference customers
• Work with product and GTM teams to:
• Shape positioning
• Refine messaging

6. Own the full deal cycle

• Drive:
• Discovery
• Solution alignment
• Commercial negotiation
• Closure
• Work closely with:
• Solutions Engineering
• Product
• Leadership

What success looks like

• ₹30–50L MRR closed in new business
• At least one Tier-1 insurer closed
• POCs consistently convert into long-term deals
• Accounts scale into multi-crore ARR relationships
• New verticals show early traction

Who you are

• You have 5–10 years of enterprise sales experience
• You have closed:
• High-value, complex deals
• You are comfortable selling to:
• CXOs
• Senior stakeholders
• You think in:
• Revenue
• Deal strategy
• Long-term account value

What will make you stand out

• Experience selling into:
• BFSI / Insurance
• Track record of:
• Closing large enterprise deals
• Expanding accounts post-sale
• Strong ability to:
• Handle objections
• Navigate complex buying cycles
• Ability to work in:
• High-ambiguity, high-ownership environments

Compensation

₹2,00,000/month (fixed)

(Performance-driven upside aligned with revenue impact)

Why join

• You will work on high-value enterprise deals
• Your work directly impacts:
• Revenue
• Market positioning
• Category creation
• You will build relationships that define long-term growth

What this role is not

• Not a pipeline manager
• Not focused on low-value deals
• Not dependent on heavy support to close

What this role is

• A revenue owner
• A strategic deal closer
• A builder of enterprise relationships

One question to self-evaluate

Can you win a Tier-1 enterprise account, prove value through a POC, and scale it into a multi-crore relationship?

About Root Node

We’re an early-stage startup building intelligent tools for planning, scheduling, and optimization—starting with timetabling and warehouse logistics. Backed by deep domain expertise and a growing customer pipeline, we’re now building our core tech team. This is not just a coding job — it's a chance to build something meaningful from the ground up.

About the job

• Design and implement robust backend systems and APIs using Java or similar backend language and Spring Boot or equivalent frameworks
• Integrate backend services with existing custom ERP systems 
• Work closely with the founder on product architecture, feature prioritization, and go-to-market feedback
• Take full ownership of features — from system design and development to deployment and iterative improvements
• Help shape our engineering culture and technical foundations

You're a Great Fit If You:

• Have 3+ years of experience in backend development
• Are strong in Java or similar languages (e.g., Kotlin, Go, Node.js)
• Have solid experience with Spring Boot or equivalent backend frameworks
• Have integrated with ERP or enterprise systems in production environments
• Are comfortable with both SQL (PostgreSQL) and NoSQL (MongoDB)
• Understand REST API development, authentication, Docker
• Have an entrepreneurial mindset — you're excited about ownership, ambiguity, and making decisions that shape the product and company
• Want more than just a job — you want to build, solve, and learn rapidly

What We Offer

• Competitive salary
• High degree of ownership and autonomy
• Ability to shape the tech and product direction from Day 1
• Transparent and fast decision-making culture
• A builder’s environment — solve real-world problems with real impact

Location: Rajarhat, Kolkata

Experience: 8 years and above

Salary: upto 15 lakhs

Qualification: B. Tech/ B.E./ MBA

Responsibilities:

• Assess change proposals and define solutions to help the organization to achieve its goals.
• Discover, organise and clarify business needs and review/produce applications for change.
• Prioritize requirements from various stakeholders.
• Technical documentation.

Skills:

• 4 - 5 years experience in technical documentation.
• Sound knowledge and experience with Agile.
• Experience in app making and web programming.

What WE have

• A small, well-knit team with a bunch of self-driven aces who love their work as well as working here!
• A top notch product spanning web app, mobile app, chatbot and artificial intelligence tech stack
• An enviable client portfolio that includes known names such as LG, Biba, W, HPCL, Costa Coffee (to name a few), who depend on us to track their compliances and efficiencies.
• An open door culture
• An environment to push your boundaries and expand your skillsets
• A newer challenge every day!

What YOU must have

• 3-5 years’ experience with native mobile App development on both Android as well as iOS platforms.
• Bachelor’s degree or above in information systems or computer science
• Excellent knowledge of Android SDK, different versions of Android, iOS framework
• Strong knowledge of Android & iOS UI design principles, patterns, and best practices
• Familiarity with RESTful APIs to effectively integrate Android applications
• Should have worked on Apps using local resources (like camera, GPS, Speech recorder, settings etc) and having local storage capability using SQLite, xml, firebase etc.
• Proficient understanding of code versioning tools such as Git
• Familiarity with various testing tools
• Team player with strong communication, documentation  and collaboration skills

• Strong analytical and problem solving skills
• Ability to productively function under pressure and within a deadline oriented atmosphere
• Self-motivated and high-initiative taking
• Organized and detail orientated with strong work ethic
• Ability to thrive in a dynamic and fast-paced environment

What will you do

• Translate designs and wire frames into high quality code

• Develop AI/ML based mobile apps for both Android and iOS
• Resolve bugs as reported by the QA team.
• Maintain code quality, organization, and automation
• Share weekly and monthly development plans and build releases schedule.

Impress us with your skill, self-drive and work ethics, and we will go any length to make you part of the growth journey!