Engineering at Chorus One is anything but typical. Our engineers aren't just coders; they're key drivers of growth. They experiment, innovate, and solve the problems that matter most. If this sounds like you, we'd love to welcome you to our team! 📩Apply now: https://chorus.one/careers
Chorus One’s Post
More Relevant Posts
-
BEFORE ACCEPTING THAT SENIOR ENGINEER JOB 🤓✨ Ready to conquer the tech world and make a lasting impact on the industry. 😎🚀 AFTER 8 HOURS OF MEETINGS A DAY 😵🤯 Drowning in a sea of meetings, wondering if you'll ever get a chance to actually code. 💻😴 Share your funniest or most relatable senior engineer moments in the comments below! Let's laugh together! 😂 #seniorengineerlife #codingdreams #techreality #meetingmarathon
To view or add a comment, sign in
-
-
Senior Django Developer @ iHolda | Building Scalable Microservices | Backend Developer | Security and Optimization Enthusiast
if you are in a company building a product, then, it's a necessity to understand the sole purpose and to an extent the business logic behind that product. Here is why, Sometimes, you might just be the one to discover a flaw behind the implementation and the business logic of that product. Your aim is not only to make a functional product but to also make the product realisable and coding won't do just that. I've seen products whose code base are 🤮🤮 yet the company is making lots of money from it. and I've seen products with great functional implementation (in the code) yet they make no money. So, try to know if what you are developing will be recognisable both in the view of your codebase and business logic. Come to think of it, as an engineer or a developer, you find more pride when what you've developed is recognisable and trending positively.
You're a great software engineer if you: 1. Focus on the problems and not the tech 2. Help others around you move faster 3. You're the go-to person for some of your team's scope 4. Are a strong communicator both in speaking and writing 5. You're influence others to go in the most impactful direction 6. Proactively identify and address issues slowing engineers down 7. Focus on implementation quality and writing code that is easier to maintain 8. Know how to drive your projects across teams/functions What else makes a great engineer?
To view or add a comment, sign in
-
You're a great software engineer if you: 1. Focus on the problems and not the tech 2. Help others around you move faster 3. You're the go-to person for some of your team's scope 4. Are a strong communicator both in speaking and writing 5. You're influence others to go in the most impactful direction 6. Proactively identify and address issues slowing engineers down 7. Focus on implementation quality and writing code that is easier to maintain 8. Know how to drive your projects across teams/functions What else makes a great engineer?
To view or add a comment, sign in
-
There are 2 types of software engineers: 1. Problem-Obsessed: These engineers love being given a hard problem. They love to tinker with new tech. If given a simple problem, they are going to spend extra engineering time to produce an elegant solution. They are craftsmen and artists. 2. Customer-Obsessed: These engineers are energized by seeing something they built being used. They would rather release something good enough and get feedback rather than wait for it to be an elegant solution. These engineers enjoy interacting with customers and solving their problems. Both engineers are needed on a well-balanced team. But a team is likely to overindex on one of these personas based on the product they are building. Which engineer are you? Does your current role match your strengths?
To view or add a comment, sign in
-
Elevating Our Code Quality: Insights from Sarah 👩💻 Meet Sarah, one of our software developers at Rohde & Schwarz . In our new video, she shares how our team ensures high quality and adheres to the highest standards in software development. Want to know more about the secret to our success? 🚀 Watch the video! Check also our current job openings for Software Developers! #RohdeSchwarz #MakeIdeasReal #SoftwareDevelopment #Coding
Elevating Our Code Quality 👩💻
To view or add a comment, sign in
-
Attention All Software Engineers! 🚨🔔 Here are 7 roles that we want you to know about. ⬇️ But it doesn't stop there. There are many more on our website, (see below) to check out the rest! If you would be keen to hear more about any of these positions, contact the team today. ☎️ 📧 #disruptingthefuture #softwareengineering
To view or add a comment, sign in
-
Understanding software engineering means seeing beyond just coding. The best software engineers know all parts of the Software Development Life Cycle: 1. Needs assessment 2. Strategy development 3. System design 4. Implementation 5. Quality assurance 6. Rollouts 7. User feedback This broad view is why people from different careers bring unique value to engineering teams. There’s a big overlap between music and engineering, and other fields likely share similar ties. There’s room for everyone in this field. Pursue your passion and make it yours. ♻️ Repost if you found this valuable #SoftwareDevelopment • #CareerGrowth • #EngineeringLife
To view or add a comment, sign in
-
Passionate about Continuous Delivery, Agile, DevOps, and anything that makes the lives of software engineers easier
Useful tip: make sure you know the difference between building a *team* of software engineers, and building a collection of individual contributors.
To view or add a comment, sign in
-
How to structure your Technical Organization by number of developers: 1-5 devs: Staff: All senior to principal developers Management: FCTO 5 hours a week 5-10 devs: Staff: 5 Seniors, 4 intermediate developers Management: FCTO 10 hours per week, 1 full-time engineering manager 10-20 devs: Staff: 10 seniors, 5 intermediate, 3 juniors Management:FCTO 10 hours per week, 2 engineering managers 20-40 devs: Staff: 15 seniors, 10 intermediates, 3 juniors Management: FCTO 10 hours per week, 3 engineering managers This is a rough estimation of what I have seen work very well in my travels. DM me or comment for details.
To view or add a comment, sign in
-
> Most software engineers chose this career not because they enjoy creating pretty buttons. > > 𝗧𝗵𝗲𝘆 𝗰𝗵𝗼𝘀𝗲 𝗶𝘁 𝗯𝗲𝗰𝗮𝘂𝘀𝗲 𝘁𝗵𝗲𝘆 𝗹𝗼𝘃𝗲 𝘀𝗼𝗹𝘃𝗶𝗻𝗴 𝗽𝗿𝗼𝗯𝗹𝗲𝗺𝘀. This used to be true, but it hasn't been for quite a few years, now. Today, most new software engineers are choosing this career because they needed a job, and they were sold the dream by someone selling courses and bootcamps that if they completed the program, drilled LeetCode, and had interview prep and coaching, they could land a job that could earn them USD$100K+ a year, in just a few short years. They don't love solving problems. They rely on asking Google, Stack Overflow, and now ChatGPT, their problems and then brute force iterating through the answers until they get what they believe solves their problem. They complain about "work-life balance" because they don't actually love spending hours or even days playing with a puzzle until they solve it. They don't actually want to learn how things work. Their primary goal isn't to gain more understanding. They just want to complete whatever task they're assigned so they can be done. Working together to define the problem and then figuring out how to solve it is absolutely not the "fun" part for them. The fun part for them is all the stuff they can now do outside of work hours with all the money they're earning. When you love what you do, work _is_ life, and balance comes naturally as a consequence. Of course, this is a gross generalization: there are absolutely still some software engineers who choose this career because they love solving problems. But, at least in my experience, recently, those are absolutely the minority.
Don't tell your software engineers what to do. Give them a problem to solve: Most software engineers chose this career not because they enjoy creating pretty buttons. 𝗧𝗵𝗲𝘆 𝗰𝗵𝗼𝘀𝗲 𝗶𝘁 𝗯𝗲𝗰𝗮𝘂𝘀𝗲 𝘁𝗵𝗲𝘆 𝗹𝗼𝘃𝗲 𝘀𝗼𝗹𝘃𝗶𝗻𝗴 𝗽𝗿𝗼𝗯𝗹𝗲𝗺𝘀. Engineering managers often forget that. When you give people very detailed instructions, you rob them of all the fun parts of our job. Give some room for improvisation and decision-making. It'll do wonders. Join 13,100+ engineers who receive weekly articles on managing software teams: https://lnkd.in/dmvYbssM
To view or add a comment, sign in