Software Development Engineer Testing (SDET)

JOB DESCRIPTION- GRAPHIC DESIGNER

Key Responsibilities:

• Create visually appealing graphics for social media, websites, advertisements, campaigns, and other digital platforms.
• Develop creative designs for marketing campaigns, promotional materials, banners, posts, presentations, and branding requirements.
• Collaborate with the marketing, content, and social media teams to understand design requirements and deliver creative solutions.
• Create designs that align with brand guidelines and maintain consistency across different platforms.
• Work on multiple design projects simultaneously while meeting deadlines.
• Edit and enhance images, illustrations, and other visual assets as required.
• Stay updated with the latest design trends, social media trends, and digital marketing creatives.
• Convert concepts and ideas into engaging and effective visual designs.
• Take feedback positively and make necessary revisions to improve the final output.

Required Skills:

• Proficiency in Adobe Photoshop and Illustrator.
• Good knowledge of Figma and Canva.
• Basic to good understanding of UI/UX principles is a plus.
• Strong understanding of typography, color combinations, layouts, and visual hierarchy.
• Good understanding of social media and digital marketing creatives.
• Knowledge of Adobe After Effects or Premiere Pro is an added advantage.
• Strong creativity and attention to detail.
• Ability to understand briefs and deliver designs according to requirements.
• Good communication and time-management skills.

AI Product QA Engineer

This is not the QA you know. We're not hiring someone to find bugs. We're hiring someone to guard the user's experience — with AI as the foundation.

Read this before you read anything else

Forget everything traditional QA taught you.

I don't want "I tested it, here are the 14 defects." I don't want a gatekeeper at the end of the line ticking checkboxes against a technical feature list. That QA is dead here, and honestly, AI already does it better.

I want business-product QA. Product taste as a discipline. User empathy as a test case. Your foundation is AI — everything runs through Claude Code / Codex — and on top of that foundation you apply QA from a business, user-empathy, onboarding, and go-to-market lens. You're not asking "does the button work?" You're asking "is this the sharpest user journey this product could possibly have?"

We're extreme about four things and nothing else: extreme hard work, extreme respect, extreme shipping, extreme innovation. Not hours . There's no boss — there's a product, a user, and you. You're rewarded on one thing: your hunger.

The 90 / 10

Same philosophy that runs this whole company. 90% of the work, AI does. Claude Code writes the test cases, automates the suites, drives the API calls, spins up the harness — faster than any QA team I've ever run . That 90% is the floor now.

The 10% is you — the human who decides what's actually worth testing and why:

• the user empathy — feeling the friction a real brand manager feels at 9pm
• the judgment — is this the sharpest journey, or just a working one?
• the taste — the design standard, the elegance, the delight
• the business sense — does this survive a real client's Tuesday, their onboarding, their objection?
• the critical eye — reading an AI trace and knowing instantly when the product is confidently wrong

AI didn't shrink QA. It concentrated it. The 10% is smaller and heavier than the 100% ever was. That's the 10% I'm hiring.

How you actually work

Everything you do runs through Claude Code. You write the cases in it. You automate the cases in it. You do business testing in it. You interrogate user empathy in it — "how will the user react to this, and is this the sharpest journey of the product?"

But make no mistake: this is technical QA. You write scripts. You hit and test APIs directly. You read the traces, the payloads, the failure modes. You don't wait for a UI to click — you go straight at the system. The difference from old-school QA isn't less technical; it's technical in service of the user and the business, not the feature checklist.

The stack & the surface

We're a web application in Python, Rust, and everything in between — and you'll be QA-ing across four products: ARIA, the Persona product, the video-decoding product, and the rest of the family. Real APIs, real pipelines, real agents watching millions of social videos in Hindi, Tamil, Bahasa, Thai for the world's biggest consumer brands . You need to be comfortable writing a script to probe any of them and reading exactly what came back.

Your first 48 hours

Day one, morning: you get access to a live product and its real client questions in the queue. Not a sandbox. Not a tutorial.

Day one, afternoon: you pick one user journey and, in Claude Code, you build the case, automate it, and pressure-test it against the actual experience a client would have.

Day two: you tell me not "here are the defects" but "here's where the journey breaks the user, and here's the sharper one." And you've already got the automated eval that guards it going forward.

If that scares you, this isn't your room. If it makes you grin — keep reading.

The loop

We are always on. A technique drops on Twitter Tuesday morning; by Thursday it's in a product; by Friday a brand team on the other side of the world is using it — and someone has to make sure that journey is delightful, not just functional. That someone is you. See it. Test it against the user. Sharpen it. Ship it. The loop never stops. If your learning lives in "read later" folders , this will break you.

What you own

The user's experience across every product. Not the defect list — the journey. Find a problem and you don't just log the instance; you build the automated eval in Claude Code that kills the whole class of bad experience forever. Your evals become the product's conscience. Your standard becomes the bar the whole team ships to.

The bar is craft, not years. 23 or 43 — I don't care. I care whether you can feel what a user feels and write the script that proves it.

Who this is actually for

This is a close-to-100% self-starter environment.

You do not want to be here if you want to be handed a test plan. You want to be here if you believe you're the only one who can guard this product's soul — the king or queen of the user journey — with absolute hunger burning in you to do it. Here, will is bigger than skill. And AI isn't a tool you use; it's the foundation you think on.

Fair warning ⚠

The pace is relentless and there's no playbook for AI-product QA — you're partly inventing the discipline as you go. If you want a stable checklist and a comfortable gate at the end of the pipeline, you'll be miserable here, and I'd rather you know now. But if you want to define what QA even means in the age of agents — what you learn here in one year, you won't learn anywhere else in five.

How this goes

Don't send a resume. Send the 10%.

An eval harness you're proud of. A test suite you built in Claude Code that caught something a checklist never would. A teardown of a product's user journey where your taste and your technical chops were unmistakably yours.

Work Location: Remote

We are looking for a skilled Android Developer with strong Kotlin experience to join our mobile development team. The candidate will be responsible for developing, maintaining, and improving Android applications while ensuring high performance, responsiveness, and code quality.

Key Responsibilities

• Design and build advanced Android applications using Kotlin.
• Collaborate with product managers, designers, and backend developers to define app features.
• Maintain clean, efficient, and reusable code.
• Implement modern Android architecture patterns (MVVM/MVP/MVI).
• Integrate RESTful APIs and third-party libraries.
• Debug, troubleshoot, and fix bugs to improve application performance.
• Write unit and UI tests to ensure application reliability.
• Participate in code reviews and follow best coding practices.
• Optimize applications for maximum speed and scalability.

Required Skills & Qualifications

• Bachelor’s degree in Computer Science, Engineering, or a related field.
• Strong experience in Android development using Kotlin.
• Solid understanding of Android SDK, Android Studio, and Gradle.
• Experience with MVVM architecture and Jetpack components (LiveData, ViewModel, Navigation, Room).
• Experience with REST APIs and JSON.
• Knowledge of Git or other version control systems.
• Understanding of Material Design guidelines.
• Experience with debugging and performance optimization
• 
  

🚀 Hiring: Java Developer at Deqode

⭐ Experience: 2 Years

📍 Location: Indore

⭐ Work Mode:- 5 Days Work from Office

⏱️ Notice Period: Immediate Joiners

(Only immediate joiners & candidates serving notice period)

💫 Responsibilities:

✅ Develop and maintain Java applications

✅ Work with Spring/Spring Boot & REST APIs

✅ Debug, optimize, and improve application performance

✅ Design and implement Microservices & REST APIs

Key Responsibilities

• Develop and implement a comprehensive L&D strategy aligned with business priorities and growth targets.
•  Act as a strategic advisor to senior leadership on talent development, succession planning, and sales readiness.       
• Promote a culture of continuous learning, high performance, and sales excellence.
• Build and maintain leadership pipelines, addressing critical skill gaps across the organization.
• Integrate market insights, product knowledge, customer-centric strategies, and competitive intelligence into learning journeys.
• Team Development: Build, mentor, and empower high-performing teams that are mission-aligned and impact-driven.

Key Competencies Required:

• Deep expertise in L&D strategy, payroll management, and talent acquisition.
• Ability to structure, monitor, and optimize team performance.
• Strong strategic thinking and ability to align HR initiatives with business objectives.
• Experienced in managing and developing large sales teams, driving capability and performance.

Job Description:

Suggestic Buildcon is seeking passionate and driven individuals to join our real estate sales team as Real Estate Consultants. 

Key Responsibilities:

• Make outbound calls to prospective clients and explain project details.
• Understand client requirements and pitch suitable property options.
• Build and maintain client relationships with regular follow-ups.
• Guide clients throughout the sales journey — from inquiry to deal closure.
• Achieve monthly sales targets (minimum 1 deal per month).

Probation Period:

• Duration: 3 Months
• Monthly incentive earning potential: ₹25,000 to ₹1,00,000+
• Candidates must close at least 1 deal per month to become eligible for a full-time role.

Post Probation (Full-Time Role):

• Fixed salary offered based on prior experience and skillset.
• Continued performance-based incentives.

Ideal Candidate:

• Strong communication and convincing skills.
• Passionate about sales and client interaction.
• Self-motivated and goal-oriented.
• Prior experience in real estate sales is a plus, but not mandatory.
• 
  

Why Join Suggestic Buildcon?

• High-growth opportunity in a reputed real estate company.
• Performance-driven culture with high earning potential.
• Real career path from consultant to team leader and beyond.

Location: Bengaluru

Experience: 3+ Years

We are looking for a highly motivated Support Engineer to be part of Borderless Softtech Pvt Ltd Support team. In addition to strong technical competency, the position requires the ability to effectively work with different teams.

The Support Engineer will be responsible for production support of the Stockal applications on the cloud. The role involves continuous collaboration with business, development teams & partners. Our ever-evolving technology stack ensures a phenomenal learning culture in the team.

Responsibilities:

• Handling On-call production support, Change and Incident Management for critical systems.
• Setting up alerting and monitoring, troubleshooting application issues in AWS cloud.
• Prepare, evaluate and maintain tools supporting and process automation for software product release.
• Perform with project teams to identify apt build schedule and initiate packaging and build process.
• Drive projects that improve support-related processes and technical support experience.
• Manage build automation and integration tools (Jenkins, Maven) and processes.
• Create scripts to automate build processes to improve organizational performance.
• Demonstrate technical, analytical and problem-solving skills.
• Providing support in the form of procedural documentation.
• Drive development team towards best-in-class, continuous integration/delivery tools and procedures.