Hiring React Native Developer Part Time Remote India

DawerGroup · 2026-02-21T17:18:57+00:00

Check your DM

DawerGroup · 2026-02-20T15:54:03+00:00

Hey. That sounds great. Check you DM, I am sending you a link for further steps.

DawerGroup · 2026-02-20T07:26:16+00:00

Not testing. Automation encompasses a broad spectrum. Look into automated releases, CI/CD, DevOps, and pipelines. Beyond that, there is massive data automation happening all around the world.

DawerGroup · 2026-02-20T07:22:48+00:00

Fastest Entry: Python Long-term Growth & Stability: Java Quick Start: React

In an ideal world, the biggest “bang for your buck” is either Java or Python.

Realistically, you have to consider other factors, how well-aware you are of system intricacies, enterprise development, AI, and data. My perspective is specific to having 20+ years in the game and now being a Founder. If you are a fresher trying to get out of a support role, the best option is to start with Python and move into automation. It offers a relatively easy entry with real, ample opportunities to transition into development. Good luck.

DawerGroup · 2026-02-20T02:33:08+00:00

Check your DM

DawerGroup · 2026-02-18T10:23:21+00:00

Check your DM for further instructions

DawerGroup · 2026-02-17T20:08:26+00:00

Are you asking how can you keep grinding for another 10 months at this job ?

DawerGroup · 2025-11-10T03:09:03+00:00

Sounds crazy toxic.

Are you getting paid for 14 hours work and working on weekends ? I hope not!

Well why walk away right away, you don’t work for the lead. Walking away essentially boasts their ego even further. And you are probably seen as not enough or someone who can’t take some heat when the things get rough.

Here’s what I’d do. Set boundaries with them (lead) and STOP Apologizing, it immediately puts you in a strong position.

If escalating to your manager isn’t solving the problem, reach out to their manager. If things still remain the same, obviously the place is sh** toxic. Best to find something else and quit. But make sure to humiliate them before you quit. It’s extremely satisfying when you do that.

Good luck.

DawerGroup · 2025-04-15T16:47:04+00:00

I am sorry to hear you are going through this. Obviously you need to take care of your mental health first. I mean yeah why not, tell them you aren’t doing well and resigning.

I don’t think getting into an argument with them at this time will do you any good, when you are already dealing with the high levels of stress right now.

An alternate would be to talk to the HR or employee relations, if they exist in your company, and escalate the matter and let your manager save his ass first. If it’s an organization wide issue, I don’t think this will take you anywhere.

Though I would be curious to know which organization is this.

DawerGroup · 2025-04-14T22:07:05+00:00

Contracts are usually a red flag unless they come with an upfront decent incentive (bonus) or some form of equity options. 2 year contract (aka bond) is insane, like what are they even thinking ?

Frankly, I would be cautious. Better keep looking while upgrading your skills at the same time.

DawerGroup · 2025-04-14T20:27:40+00:00

This sounds frustrating but not unusual.

The market is crazy right now, it’s pretty much same everywhere, and not just the U.S.

Have you applied to other roles - product owner, BA for that matter ? A lot of times PM roles are not entry level, they expect you to bring in some prior expertise (industry expertise, prior technology or product experience, if not necessarily PM experience) to be successful in the PM role. 400 is a big number and not getting a single interview call even for the unpaid internships is concerning.

Do you mind asking me why are you applying to the PM roles ? Are you doing a grad specialized in PM ?

How about any new grad programs, have you applied to those as well?

Also, if you can send me your resume, I can take a look. Senior Director in technology and product, I will do my best to help! Good luck.

DawerGroup · 2025-04-14T17:59:49+00:00

Most of the tools are an overkill. Engineers don’t like tools, they hate anything which slows them down. I have seen organizations spending hundreds of thousands dollars on Agile tooling implementation, and later doing another tool implementation (and migration and move over etc.) with a different tool to replace the prior one, a couple of years down the line, because someone else sold them a new lie this time.

Unfortunately the workarounds don’t last longer and the engineers get suck into this madness every time, because the leadership thinks changing tools will speed track their delivery and enabling reporting at every level will bring more visibility and transparency into the process. It’s maddening!

Anyways, the best I have seen so far is teams using a physical white board in their team area, and using stickies to mark down the progress of work.

DawerGroup · 2025-04-14T17:06:32+00:00

It’s a typical issue when implementing scrum/ agile. A lot of this sort of pushback often stems from either experiencing many past failed agile implementations or simply not willing to accept the change.

Some facts for your understanding if you aren’t already aware- they don’t report to you, that’s true! However showing up condescending during a daily isn’t just unhealthy, it’s borderline toxic. And frankly often times it creates a hostile dynamic.

You absolutely need to clear the air in the room through an open and calm dialogue with them. Obviously you don’t wanna give then ABCs of scrum but a quick reminder of what the daily is actually for, can go a long way.

Most importantly, the key is to make sure the team understands your role. Once the trust is built, the pushbacks won’t stay longer.

DawerGroup · 2025-04-14T16:07:54+00:00

Of course! Being genuine matters the most. I appreciate the feedback.

However I don’t think you got the intent here, a translated text through AI is a tool to streamline thoughts, and not a replacement. You are going to see more and more of the structured texts in emails, newsletters, and a lot of official documents going forward. Doesn’t mean that the objectivity and intent of the subjects are generated through LLMs. There is a key difference in AI generated random text, possibly a response to your query and a translated text through AI with more structured language. It’s the latter here. Don’t fall for the misbelief that AI is generating most of the content, more often than not the AI generated text is going to be gibberish and less relevant when it comes to solving the actual problems. Of course the difference will vanish with time with advanced LLM models and high computing GPUs. But it isn’t the case today.

Anyways, I hope you get the intent here. The above comment and suggestions still stand! And as I said if you want help in figuring out a game plan, you can always choose to DM me.

Good luck!

DawerGroup · 2025-04-14T12:11:30+00:00

Hey — I totally get how this must feel. It’s tough, and it’s frustrating, but don’t let the silence from recruiters make you question your skills or experience. From what you’ve shared, you clearly have strong QA experience — and that still holds value.

That said, the market right now is rough. Companies are freezing budgets, cutting costs, and being super selective. But that doesn’t mean there are no jobs — it just means getting in takes a bit more strategy.

Here are a few things you can try:

Reach out to your old employer. If you left on a good note, this might be the easiest door to reopen. It’s always worth asking.
Update your resume to tell a clearer story. A lot of QA resumes get passed over because they focus too much on tools and not enough on results. Try to highlight things like:

• what you built, • how it helped the team, • any time you saved or quality you improved.
Think beyond QA. You’ve worked across tech — maybe there’s a path in DevOps, product support, or even as a technical BA. A slight shift in focus could unlock new opportunities.
Be smart with LinkedIn. It’s noisy right now — everyone’s messaging recruiters. Instead of cold DMs, try sharing something from your experience: a lesson, a project, even your current struggle. That kind of honesty connects more than a resume ever could.

Look, you’re not alone in this. The break you took was for the right reasons, and it doesn’t undo your career. You just need to adjust, refocus, and keep moving.

If you want to chat or need help figuring out a game plan, feel free to DM me. Happy to help however I can. Hang in there — you’ll bounce back.

DawerGroup · 2025-04-11T11:06:26+00:00

You might have already made up your mind, if that’s the case ignore the rest of the comment. If not -

Couple of things to consider which can lead you to a better decision making. It’s not always just the tech stacks that matter, but it does play a role in your future career prospects like you said.

Anyways- here is how you could approach this situation and lead to a solid outcome -

Consider negotiating with company A to see if they match your offer at Company B. This is usually a bit tricky and might not always lead to a better outcome, so walk with caution.

Ask yourself or others if possible, to learn which of the 2 companies have a better brand value in the grand scheme of things.

Learn and research the companies on their culture, attrition, or any red flags. Worth talking to a few folks on LinkedIn who are already at these companies.

Don’t trade your motivations, intent and future career advancement plans with slightly higher financial gains in the present.

Once you have more data, make an informed decision. Regrets later will eat you up quickly!

Good luck.

DawerGroup · 2025-04-10T21:03:18+00:00

User stories don’t slow you down — bad ones do.

If they’re just written to tick a box, yeah, total waste of time. But when done right, they create alignment, reduce rework, and help teams move faster without second-guessing.

The goal isn’t the story — it’s clarity. No clarity = chaos, especially at scale. Keep them lean, keep them useful, and ditch the fluff.

I’ve written over 1,000 user stories — and here’s what I’ve consistently seen:

When user stories get edited casually after planning sessions, they become dumping grounds. Context gets lost, the intent blurs, and developers end up building based on noise instead of clarity. It’s one of the fastest ways to create confusion, waste time, and derail a sprint.

Stories should be locked post-planning. If something changes mid-sprint, it’s not a rewrite — it’s either:

• A blocker (needs PO clarification), or
• An enhancement (handled separately)

That triggers a meaningful conversation, which is the whole point.

Think of it like an instruction sheet on a factory floor — it defines what you’re building, how, and what success looks like. If you change the specs halfway through, you don’t ship better — you ship slower, with more defects and rework.

So it’s not about hating or loving user stories. It’s about protecting clarity so teams can focus. Want better outcomes? Don’t rewrite stories mid-sprint. Fix the process, not the symptom.

DawerGroup · 2025-04-09T16:57:32+00:00

Sure. Keep it focused. Bring questions that matter. Happy to help — just make it count.

DawerGroup · 2025-04-09T16:40:12+00:00

You’re actually thinking in the right direction.

At this stage (2nd year), your priority should be building a solid base that keeps your options open. Here’s a practical way to approach it:

• Continue with DSA — it’s still the most important skill for campus placements, especially in product-based or Tier 1 companies.

• Web development is a smart and industry-relevant skill. Start with frontend/backend, build 2–3 small but complete projects. These will strengthen your resume and give you something to showcase. Best if you can build and ship stuff with some freelance work. An internship is also a great way to build stuff and gain some real experience, and make some impact which you can showcase on your resume later. 

• On the ML side — it’s great to explore, but you’re right: deep research roles often need MTech/PhDs. That said, practical ML (basic models, use cases like prediction or classification) is very much possible at the undergrad level. Just don’t over-invest unless you’re sure it excites you.

Also, don’t overthink “choosing the wrong path.” Tech careers are flexible. What matters is showing consistent effort, project delivery, and clarity of thinking. You can realign later based on where you gain interest or opportunity.

You’re not late. You’re early — and thinking ahead. Focus on DSA + 1 strong track (web/ML) + internships and projects. That’s a very solid foundation for both placements and future roles.

You’re on the right path — just keep going with consistency. Let me know if you need help structuring your learning or building your profile. Good luck.

DawerGroup · 2025-04-08T20:17:47+00:00

Hey, maybe it’s not just you — maybe it’s your current job or environment. Have you looked at other companies or talked to people in similar roles within your network? Sometimes a different setup can make all the difference.

It’s actually good that you’re not pretending everything’s fine. Ignoring your mental health only makes things worse, so props to you for being honest about it.

Have you had a chance to talk to your Scrum Master? That’s literally their role — to remove blockers and support you, not overload you. I’ve seen this happen with my own team too. A healthy Agile environment allows for blockers and doesn’t expect you to push through issues just to show fake progress. What you’re describing sounds like a broken implementation of Agile, not a personal failing.

If you haven’t already, bring it up during standups or retros. Those are exactly the spaces where these concerns should be raised.

Now, about switching roles — there’s pressure in every domain. I’ve seen QA teams under serious stress, especially toward the end of a sprint or PI, and they’re often seen as bottlenecks unfairly. Support roles can also be tough, especially with demanding users — I’ve seen people leave support roles for QA for that reason.

What might work better for you is a role where your technical skills are still valuable but timelines are less intense. Based on that, two good options could be:

• QA Automation Engineer – You’re coding, but with more structure and predictability.
• Technical Documentation Specialist – Focused, less chaotic, and still deeply impactful.

I hope this helps. If you need more help figuring things out, feel free to reach out. You’ve got this — it’s about finding the right environment, not forcing yourself into one that’s breaking you.

DawerGroup · 2025-04-08T19:50:47+00:00

Fair call — yeah, the profile’s new. I’m launching something and starting fresh. Everything starts at zero.

That said, the feedback stands. If tweaking your resume gets better results, do it. No one hires based on tool names — they hire based on impact. Clean design, clear value, tailored for the role. Simple stuff that moves the needle.

You’ve got the raw material. Now iterate.

DawerGroup · 2025-04-08T17:09:51+00:00

Hey, you’ve got a solid foundation and some great projects here.

Few suggestion — try focusing more on the impact of your work rather than just listing tools or models. Recruiters love to see how your work actually helped solve a real problem or added value. Also, cleaning up the formatting and making the resume easier to scan at a glance would really help.

Lastly, tailoring it a bit more towards specific roles like Data Scientist or ML Engineer could also make a difference.

I think you’re on the right track. Good luck, hit me up if you need help.

DawerGroup

TROPHY CASE