ASRT, Inc.’s Post

We're looking for someone with experience across a React/Typescript/Next.js/Tailwind stack to help us architect and implement our frontend codebase. I'm hoping for a few things from applicants: 1. Autonomy. We're a growing team. We need people to be able to share the load in terms of maintenance tasks and feature development. That capacity has to be multi-talented and self-directed. If you already know how to discuss technical requirements, give feedback to product teams, write technical documentation, perform and receive code reviews, and manage personal tasks, then you might be the person that we're looking for. 2. Experience. We want people who have used certain technologies long enough to have opinions on the right and wrong ways to do things. We want people who've already found some of the sharp edges or gone underneath the surface of the tools that they're using. We thrive on pairing and discussion. If you like talking code as much as we do and have the knowledge and experience to help shape our technical roadmap, I'd like to talk to you. 3. Curiosity. Our team is small enough that we often need to wear many hats. I don't need someone who is an expert on CI/CD systems to join me. But I would like to see someone interested enough in the Software Development Lifecycle that they want to learn and have their hand in it. We've already set up our infrastructure, but I'd love to work with someone who's actively interested in network topologies and willing to share that knowledge. We write our own SQL queries, so I hope for someone that can author rudimentary queries but with the desire to improve. If you've ever used a React hook and wondered "How does `useState` actually work?", then I'd like to explore it with you. In return, I'm happy to commit to supporting our future engineer so that they grow in their role with us. I want this to be an excellent opportunity to do work that you can be proud of while also growing your knowledge of modern web apps and networks in both breadth and depth. *** I also don't want anyone to read the job description and immediately self-select out of it because they don't meet all of the requirements. I don't want a lot of people who would otherwise be wonderful additions to my team decide not to apply because they use Vue instead of React or they aren't confident in their AWS expertise. If you're reading this and on the fence, I ask that you are both realistic and generous to yourself. https://lnkd.in/erhqZ2ix

🚀 Poplin is #hiring 📍 Job Title: Senior Engineer (remote) 🎓 Experience: 8+ years 🔗 Apply Now: https://lnkd.in/gV3AFKP7 #job #remote #workfromhome #programming #development #coding #tech #engineer #career #TypeScript #Angular #Firebase #Front end development

Great way to hire the right developer.

A common mistake I see many candidates make, and one I think is important to highlight, is giving up too quickly on their advocate/recruiter. Often, candidates move from one recruiter to the next as soon as they hear there isn’t an immediate role that fits them, without following up at least once 💔 I understand you can’t pin all your hopes on one person, but if you find someone you connect with and who genuinely cares about your success, stick with them. 👀 Here’s why: not being able to move forward with one team at one point in time doesn’t mean that your opportunities are over. A different team or a new opening can change your entire story. While we rely heavily on technology, human connections still matter. And you know who I remember every time a new role opens up? The candidates who stay in touch. It doesn’t need to be daily or weekly, but checking in once a month or every couple of months keeps you top of mind. The same principle applies to relationships outside of work—if you want to keep your friends, you can’t just rely on an annual holiday card and expect everything to work out. You need to stay connected. The competition is fierce, but together, we can navigate it. 😍 #Hiring: Backend/Distributed Systems (100% backend): Senior, Lead, Principal (multiple openings) Location: Seattle/Bellevue; San Francisco Technologies: Public Clouds (AWS preferred), Distributed Systems/microservices, Containers (kubernetes, Docker), Java, Databases, API development Full Stack (Front end focused; 50/50 split); Senior or Lead (5+ YOE), San Francisco, Seattle/Bellevue Technologies: *Front End developments frameworks: React, Angular, Next.js etc *Back End development frameworks: Node.js, Express, NestJS. Java or any OOP.

Reaching out specifically to my network (no recruiters please), because we're looking to hire full stack engineers into Float. We're building a company based on the following immutable first principles... DESIGN LED Literally everything we do is permeated by design thinking, not “just” numbers. We trust our gut and obsess over details. We ship fast and iterate by talking directly to users. SMALL TEAMS We believe small focused teams lead to improved trust, greater ownership and an increased opportunity for innovation — small teams build and “collaborate better”. LESS FUSS We strive for simplicity — less is more. If you're looking to get very early into an exciting company and you're a senior full stack engineer based in EU/UK, we'd love to chat. https://lnkd.in/dWeMeZre

In theory sounds perfect and when a company have the "budget" for it that's definitely the optimal team structure. IN THE REAL WORLD, and the plethora of job descriptions asking for both skillsets 🤭, you can clearly see what's the mindset of these companies today. Just like how in THEORY, there is host of software engineering principles and activities that you must perform to create a better system. How many teams follow all the steps in SDLC, all the rituals in scrum, or have dedicated project managers, product managers, designers, database engineers, UI Designer, UX designers, Devops Engineer, Release Engineers, Software architects, QA Engineers? But to add a little schizophrenia to the thought, It's hard to say full-stack developer isn't ideal for recruitment when everyone is asking for so much from one dev these days, but you can never lose from having a T like structure in skill set. Which have been covered in countless articles For eg. https://lnkd.in/gEJkZmEc

New remote opportunity: Full Stack Software Engineer. 👔 Position: Full-stack developer, 🏢 Employment type: Full-time #remotework #remoteworking #remotejobs #workfromhome #wfh #javascript #hiring #tech #engineer #development #software #midlevel #fullstack #fulltime #parentalleave #aws #agile #angular #cicd #docker #git #nosql #nodejs #reactjs #testdrivendevelopment #typescript

Unpopular opinion: Full stack developer recruitment isn't ideal. Hire a frontend or backend developer. It's good if they have some experience on the other side, but positions should focus on one. Occasionally, a bit of frontend might be needed from a backend dev, but for emergencies only, the job itself should be specific. A full stack role can lead to poor performance and code as it stretches a developer's expertise too thin. Cutting costs this way often results in poor software. Specializing allows for deeper knowledge and higher quality work. #TechOpinions #SoftwareDevelopment #CareerAdvice #TechHiring #DeveloperJobs #WebDevelopment #CodeQuality

Thinking of hiring a solo developer instead of a full #software development team? 🤔 It can be a smart choice, depending on your project’s size and needs. In our latest blog post, we dive into how to find a reliable solo #developer, the risks associated with them, and whether it’s truly worth the investment. Follow the link to read more: https://lnkd.in/evKSJsjN.

this is correct