Why do you find your job satisfying?

I LOVE my job!! I am a Front-End developer who specializes in React and Next.JS applications, and I usually spend my days building and fixing new marketing websites for Fortune 500 companies like Toyota, Mazda, Coca Cola, McDonalds, etc

The problem is, I have a rather low intellect. My IQ is medium/low, so I am not capable of solving complex algorithms, and my brain processing power is nowhere near some of the other guys that I work with, so I can't build truly incredible feats of engineering like 3d rendering engines or voice recognition systems.

And yet, despite my shameful lack of smarts, I feel truly satisfied by my job, because it is the right fit for my capabilities. I build and fix UI's, have a fantastic manager, am supported by a positive and helpful team which practices positive communication strategies, and regularly get rewarded with compliments for my work.

I'm not a big fish swimming in a small pond, nor am I a small fish swimming in a big one - my pond and I are in balance, and there are no sharks or parasites in it, and that keeps me happy every day.

Please God one day they will invent a therapy that will give me Einstein's IQ. Until then, this will have to do. Hope this helps.

I'm cofounder of a small company and wear many hats - writing code, roadmap planning, mentoring, product design, etc. The diversity of skills needed is fantastic and loads of fun.

But the biggest benefit is I get to set set the culture of the company without having to answer to anyone else. I worked for years in corporate tech companies (FAANG) and while I could create little pockets of healthy spaces, there were always people getting in the way of creating a truly psychologically safe place for people. It's a huge relief not having to worry about that anymore and instead I can fully tap into the psychology of motivation, treat people with fairness and empathy, and be transparent without getting into trouble with leadership. It's made the job more satisfying and everyone we work with gets along amazingly well while being incredibly supportive of each other.

Coworkers will make or break a job for me.

I can enjoy even menial work if I'm surrounded by friendly people who like doing a good job.

I can loathe any work if I have to deal with unqualified, socially combative, or unnecessarily difficult coworkers.

The job also needs to be focused on delivering the product, not constantly fighting corporate dysfunction, attending meetings, and jumping through managerial hoops.

I get regular emails from Tarsnap users thanking me for making it possible for them to recover data which they lost. The work itself isn't all that satisfying, but knowing that it's having a positive impact is very satisfying.

Interestingly, nobody has ever written to thank me for keeping their data secure. But I suppose security is something which is generally only noticed when it's missing.

You want an honest answer? Because our profession pays well.

I love programming, and I do it as a hobby, but if it didn't pay well, I wouldn't do it as a job. I would do whatever job I am capable of that pays the most.

I am just beyond lucky that programming pays well, because being poor in this world sucks.

I do! I'm a server software engineer at a video game company. Here are some highlights:

- I get to work on a game that I enjoy playing. I've worked on some games that I didn't care for (or I was not the target audience), and it's still fun work, but when you genuinely like the game, and play it in your free time, ah! It's such a joy.

- At my current company, I'm working with some of the most skilled people I've ever met. To be surrounded by awesome people is inspiring. Just by being themselves, they push me to be a better engineer, because I want to be able to stand alongside them and call them colleagues.

- I'm paid well! I'm certainly not in the FAANG salary range, but to be honest, I'm making more than nearly everyone I know outside of work. I count myself extraordinarily lucky, my salary is certainly outside the norm for my age group.

- In terms of the work itself: I enjoy problem solving and helping people out. I get to do a little bit of both every day. Those are the day-to-day fulfillments that I really appreciate.

Satisfying enough. Corporate red team at a big tech company, so I spend most days hacking first-party / internally developed software at said big tech company - usually developing exploits / PoC for novel vulnerabilities. But also sometimes longer engagements, including physical / SE at times. My favorite so far has been a long engagement where my team surreptitiously embedded ourselves into a build pipeline for a major tech product that goes out to 40m+ consumers, and added an innocuous flag to the source at build time as proof, starting from a physical break-in scenario without using our badges to enter the building.

The worst part of the job by far is drafting and editing reports. This sometimes goes on for several days.

I like it primarily because I get all the excitement of being a nation-state level adversary / threat actor / "bad guy", with none of the legal/moral/ethical risks/harms - my work ultimately contributes towards making our products (and thus our consumers) safer from such threats.

I'm at a big company that I ended up at by default not knowing how long I'd stick it out. At first I didn't think I'd like it, the pace was far too slow coming from startups. Since then, I've been on numerous large and successful projects. What I enjoy most is working with the team, designing together, and leveling each-other up. The codebase is large and many parts are old, there's a lot we'd like to change about it. We never get a full rewrite, but small and sometimes not-so-small parts of the system do get rewritten, or rather a replacement gets written and incrementally convert over to it. It's great to see the system evolve and improve. It's best when you have a good idea of the direction to go and take steps to get there. The tools are 'boring technology' but within that medium you learn to find ways to solve hard problems in compact and efficient ways.

Emergencies are rare, though I'm always on last line of support I never get paged except rare times I'm also on first line. Daytime support requests go to a person selected from a large rotation. About the only complaint is that shipping code can sometimes take a while go get through CI/CD as the test suite is large and arbitrary/intermittent failures can happen and take several tries in some cases. Meetings are either very project focused or larger informational ones can be watched async.

Work is remote, work from home, but we do have team meetings most days and often pair/screen-share working on specific problems. Sometimes we do mob-programming in larger groups. One thing that's great is that deadlines are not decided too far in advance. Only when the work is approaching completion is a date chosen to align with an external event to release major features.

I don't love my job, I love my career.

Why I don't love my job:

- I'm making someone else rich

- I don't believe in 99.99% of the ideas/business out there. But I need to pay the bills

- 99.99% of the time we work on useless stuff just for the sake of "selling more". Usually this stuff is hidden behind a "think customer first" kind of slogans (e.g., the new UI for Tesla cars)

- developers around me (including myself) know little about their profession. Software engineering is all about opinions. "Good practices" are not laws/theorems, so there's always plenty of room for debate and different opinions. It's always a waste of time because at the end of the day we are building crap

- current software engineering practices are crap as well (e.g., agile manifesto, agile implementation, scrum), and the tooling is in baby steps (react, npm, python package managers, golang dependency management, etc.)

That being said, I don't dislike my job. It pays the bills, and since I care deeply enough about my career, I can fulfill my daily work duties in a couple of hours, leaving me the rest of the day to explore more insightful stuff. I love my career. Computer Science is beautiful and makes me learn more about it every day. I think that feeling will never get old, so I'm lucky.

I used to love having the freedom to figure out a need in whatever way made the most sense, without too much oversight, and working on things that actually helped people in the company. My only distractions from coding were Bi-weekly status meetings, and calls with future/current users to figure out their needs. Then scrum snuck it's way in under the guise of agile, and I've been a ball of anxiety ever since. Always either late for a meeting, or an arbitrary deadline, and unofficially spending most of my time teaching people with way better educations than me. I'm addicted to the money and healthcare, and because my contract forbids it I have no portfolio to show prospective new employers. It no longer feels like freedom, or problem solving, it feels like I'm stuck doing busy work, even though it's essentially the same job.

This is quite interesting to me, because I don't really have a good understanding of why my job is satisfying. I am the CEO of a small profitable SaaS startup.

I find almost all of my day-to-day tasks quite boring (answer sales emails, performance reviews, accounting, support, etc). But somehow, I still really love working.

I guess one of the factors is a feeling of ownership and agency. I can decide what I want to do and when. When something good happens to the company, it feels like that is also happening to me (this can also be hard sometimes when things don't go well).

Another important factor is that as "the boss", you can pick your own team. It seems like most work-frustration I hear from friends have to do with bad coworkers. I don't have bad coworkers. If I did, I could let them go, and I can try to avoid hiring those people.

Everything is a graph at my job, and I love graphs. We're using neo4j, but not just a single instance; we're providing a platform for users to setup their own neo4j instances. We offer various tools to import, edit and extend graphs. There graphs are defined by a taxonomy that's a graph, and users can define their own taxonomy according to a root taxonomy which is also a graph. It's graphs all the way down here, which is great if you love graphs.

And we get a lot of freedom. Neo4j does not use a schema to validate whether the data obeys a particular structure, so currently our taxonomies aren't binding, but I'm trying to figure out if I can make them binding in neo4j by stretching the plugin mechanisms a bit further than we've done so far. Not because anyone told me to, but because I think it's something we need.

It's a very relaxed atmosphere to dive deep into some very interesting topics.

Having worked at a few places that make consumer electronics, Apple is a breath of fresh air!

Here is how it goes when you find an issue with a qualcomm chip (which is what you are using if you want to make anything fast and portable): (1) they ignore you, (2) they tell you to fuck off, (3) they ignore you some more, (4) they tell you that because your design is not a 100% copy of their reference design, they cannot support you, (5) they delay, (6) they tell you that a new chip came out and you should try that, while not specifying if anything was actually fixed.

Here is how it goes at Apple: (1) you think you might have an issue, (2) in < 30 minutes you have a meeting/slack channel with the team that designed the chip and can clarify/discuss as needed.

It is incredibly cool to know that every part of the device is made in the same company - it means that no matter what your issue is, someone will care and try to resolve it!

I'm working as a gameplay programmer for a small indie game studio (20 people, 6 of them programmers). The project is a strategy game.

* I love the people -- I enjoy working with creative folks (artists, designers). As for programmers, everyone who worked in gamedev for 5+ years is batshit insane in their own way, so they're fun to be around, too.

* The project is exciting, and no one will do it if we don't. I'd absolutely LOVE to play the game we're making.

* I'm somewhat irreplaceable due to the nature of small teams working on big projects in a developing country. People with comparable experience prefer moving to Sweden or US for reasons I don't quite understand ¯\_(ツ)_/¯

* The salary is good for where I live. Nothing outrageous, but I can get a house, a car, and would still have some money to spare.

* 100% full remote

* I'm a bit overqualified. In other words, at the exchange of ~20% lower salary, I get the extra time to do things my way, or even slack off half the day if I feel like it.

There is one single reason I'm considering moving (to even less developed place), and it's that I'm concerned the complete lack of stress in my day-to-day life will turn me into a weakling, and when bad things come (and they always do), I won't be ready.

I don't like tooling to get in the way of me doing my job. I work in infrastructure engineering (server ops) where due to the vast infrastructure doing things manually is not an option. Due to this I get to write a lot of code, which I enjoy. In a number of languages; some I enjoy more than others.

I also get to deal with the hottest platforms just enough (public cloud, on-prem K8s, etc) while getting to maintain the vast on-prem server infrastructure that is the majority of my job. I'm not a fan of Terraform, Ansible, Chef, etc (I don't hate them and I've used them extensively elsewhere) so I enjoy that I've given the autonomy to write the actual code to do what needs to be done rather than use a platform that just takes in a config file.

So simply put, my job let's me do the technical work how I want (with team collaboration of course).

Algorithmic trader, quantitative researcher, 'retail trader' here. When your strategies are trend-heavy, most of the time you're slowly bleeding out, waiting and doubting your simulations, wondering whether the market has fundamentally changed etc, but a few times a year it's like you're printing money and you finally don't feel like an idiot anymore.

My current job is drudgery due to agile. But for most of my career I've found it enjoyable to have the kind of space and freedom and ownership of work that I don't have now. Earning trust and getting to exercise my own judgment about what to work on every day without Jira and sprints. Owning entire projects rather than having work I could do myself split among 3 people and getting blocked or delayed at every step.

When I was satisfied with my job, it was because I worked on stuff that's highly visible and somewhat impactful.

But then the company grew, and I found myself relegated to some armpit of one of our backend systems, with legacy code so bad Lovecraft credited it as an inspiration. What I work on tends to be completely invisible and doesn't feel aligned with the company's successes at all. Now I find my job saddening.

I work at a fairly large organization (>1000 employees) as something of a jack-of-all-trades-having-to-do-with-software-development. There are several different groups within this org pursuing a variety of projects, many of which involve software in some way (sometimes as their main thing, sometimes in support of their main thing). Over the last decade+ of working there I have managed to develop a positive enough reputation with a wide enough network that I can choose from a variety of interesting opportunities. Some are longer works that I support for years, some are shorter prototyping or POC efforts, and some are stepping in for a couple of days or weeks to bridge a gap, implement a specific feature, or address a particular issue.

I also get to act in a variety of roles, from developer to architect to reviewer/advisor to tech lead. I'm working to move away from formal leadership of people or projects (I seem to have a confounding inversely proportional relationship with Formal Responsibility: the more of it I have, the less I am able to accomplish) and this may ultimately have a negative impact on my career-total-compensation; the org has formal personnel and project management tracks but not really anything for ICs. However, it is having a very positive impact on both my productivity and my mental health. It is a relatively recent change, so we'll have to see what my raise looks like next year; maybe management will see my impact as an interconnected contributor as even greater than when I was a manager.

I am full-time remote with a pretty flexible schedule (attend all important meetings and get in my 80 hours every two weeks and it mostly doesn't matter if I'm writing code at 10AM or 10PM) and generally I get to work with whatever coding tools I prefer (need to get my Emacs-Jira integration MVP finished though, because Jira is a tremendous productivity sink for me and some of my projects use it)

I guess I'll be an odd-ball here. I'm an Architect. A real one - that designs built spaces. The hours are insane and the pay is crap. But I absolutely love it because I get to create things in real world. Shakespeare said " All the world’s a stage, And all the men and women merely players;" I get to design that stage, add a piece of my imagination into the real world. I also code and mess around with ML and game engines to see how agents could create spaces with discrete elements. There are many times I think of jumping ship to UI/UX or AR development due to my graphic, design and problem solving skills, but , the amount of satisfaction I get solving a real world problem with design is more meaningful to me than to be able to afford a decent living wage.

Yep! I’m writing Ruby/Rails code (which feeds my soul), I get opportunity to play/flex/perfect in doing that, it’s for a good mission (teen mental health) and the team is great (particularly my manager, we have absurdly amazing communication).

There have been a couple of rough patches, note.

But it comes down: Daily, I get to use my mastery over something I enjoy doing; and “monthly” I get an impact on the world I’m proud of.

I love that feeling after successfully completing and handing off a project, the ebullient sense of elation. There's nothing else like it in the world.

I'm a software engineer and solutions architect.

Purpose.

I work in R&D in the Medical Devices space.

I fully appreciate I could be making a lot more money in other domains (namely distributed systems) but for me the drive and happiness that comes with creating something that I feel _really_ matters is not easily replaceable.

I am not sticking around that long, this is my way of leaving things slightly better.

I don't. Eventually I want to switch but just started. Only thing I like is it's not very repetitive but main thing I want is problem solving. Maintenance is part of the job but yeah.

Working in pentesting and I like my job because for the majority of the time I’m treated like an adult and left alone to do my job. I’m also surrounded by smart and passionate individuals that make me want to keep learning and enjoy working. The work itself can be exciting when doing internal or external network testing. Finding a new vulnerability, thinking of a new attack vector, chaining multiple attacks and getting privileged access is always a thrill. Web app testing can be fun when testing newly build or older apps but boring if the app was tested multiples times already. Mobile testing is interesting and it can be fun bypassing controls. Wireless testing could be fun as well. Red team and physical tests are a thrill but not good for the heart. Code reviews not many want to do but are helpful when combined with web app testing.

Something else that’s fun is making a tool that helps people save time during engagements.

After a while the job is repetitive though and the thrill fades away. I’m at a point where I want to try something new but not sure where to go. I don’t want to go back to doing tickets or being on call. I also like having flexible working hours.

I enjoy my job a lot. I work at a public utilities company in a managerial role.

We sometimes have interesting problems that requires us to think a lot. That’s a lot of fun.

My colleagues are funny, so we laugh a lot.

There’s a lot of red tape that sometimes drives me nuts. On the other hand it’s really satisfying to manage red tape efficiently.

This is probably an unpopular opinion but being good at office politics can be satisfying.

Oh, and being able to program at my company is a superpower. Superpowers are fun.

I'm a consultant for Red Hat. I'm assigned a number of clients at a time, travel onsite (or work remote) to fix or build their systems, and sometimes supervise small teams as part of larger engagements.

Red Hat gives me my assignments for the next few weeks or months, tell me what end result everyone wants to see, and sends me to go get it done. I'm 100% trusted to do the job, no micromanagement. If I need help I'm a phone call away from expert engineers in all of our products. I have a TS clearance, so I'm onsite more often than not because I'm working on disconnected networks.

While I technically have a manager, they're more like a handler or mission control. He hands me my tasks, tells me the lay of the land, and gives me access to anything I need for the job. I'm not really "managed" on a day-to-day basis. Every engagement has it's own project manager that I work with closely but even that is a peer relationship, no supervisory.

I travel constantly but love it. 200+ nights in a hotel every year for the past 5 years. My wife's job is mostly remote, so she joins me on occasion, and I can get her plane tickets with my racked up mileage points. I can "pay" for our vacations entirely with loyalty points (car, hotel, plane).

One thing I love about Red Hat is everyone pushes each other forward. Co-workers reach down and pull their colleagues up behind them. Never before have I felt such a sense that my colleagues have my back all the way. A very "we're all in this together" attitude throughout the company. Also, while you're always encouraged to move up the promotion ladder if you want, if you've found a niche that you're comfy in then that's supported to. There's no up-or-out like some organizations, and no forced ranking thank Yoba.

tl;dr Red Hat completely trusts me to do my job, and does everything it can to help me succeed. It's awesome.

In a big corporate but in the digital department that has a culture I can identify myself with: faster paced, use OKR, try to get better everytime, smaller teams. I am head of digital product (team of 3 direct reports). But as others said the advantage of big corporations is that I have a good work life balance, good benefits and more or leas safe. We are just going through a massive cost saving but we try to keep internal employees - so far not really mass layoffs even if the numbers look bad.

On top of that the ability to look into the core business (not software) I can learn alot of things and evtl change jobs every couple of years easily. Yea I admit I don’t enjoy every Monday but hey my overall life is pretty good in combination with that job.

I don’t, I’m constantly doing shit work to paper over deficiencies in our data model and software.

I own a niche affiliate website that I've grown over the last year's. Today I am earning a good salary by checking in with my affiliates once a month or so.

There are no business hours, no schedule, no one being mad if I don't answer for a few days. What I call work is 90% just working on new things I think are interesting right now for me and 10% talking to customers and fixing things.

Before that took of I earned most my money trough a small (niche) online shop. Which is more work, but still very rewarding IMO.

Edit:// Quality of work is mainly not waking up early for me and having long weekends whenever I want.

I work at $BigTech in cloud consulting. I’ve liked the idea of “putting myself out of a job” for the last decade as I bumped around between smaller companies before 2020.

My job gives me the chance to do that - I see a problem, I work with the customer to come up with a solution, I design and develop an MVP, I teach their developers and DevOps folks and I move on to the next project.

Even though I work at a huge company, my project teams are small and focused and I get to wear a lot of hats - pre-sales, project management, developer, architect, Devops, etc depending on the project.

Working remotely is a huge plus.

Yeah, the product manager lets us trying a lot of technical things for the benefits of the long-term development of the project. And also a heavy trust in every teammate skills.

Somewhat. I'm definitely grateful that I found work in a mission-driven field (energy), where I'm a research manager for a non-profit. The day to day is a lot of grant administration, a little bit of research, a decent amount of helping the next generation of researchers implement their ideas. I stay because I believe in the mission and I can be effective in furthering it (and they pay is decent). This is probably all anyone can expect from a job, right?

I love coffee pauses. They are useful to "reset" your mind. Too much work will ruin your brain. And sociality between co-workers is a must.

I'm a Blockchain dev, so working in this field is highly satisfying for me; it's a cutting edge technology and it's evolving very quickly. As blockchain technology is relatively a new field, there are many opportunities for career growth and advancement. Besides, I think its community is a vibrant and supportive one.

I find my job very satisfying because of the opportunities for career growth and advancement within the company (Rather Labs). It is a honor to be part of a reputable blockchain company that is known for its innovative and reliable solutions.

All in all, working in the field of blockchain technology is a highly satisfying and fulfilling career choice, and I would highly recommend it to anyone interested in being part of this exciting and growing industry.

The only time in my life i was satisified with my job was at the start of my career when I spent a couple of years at CERN, there was a lot of freedom to try new things and technologies, you could generate great imapct and the people around was very nice.

Honestly, I feel satisfied when I succeed. My job has long periods of scrambling in the dark for relatively few periods where everything works and you've made something great. I like the feelings of accomplishments when it finally works

Just being able to use a computer to work is great. I like to type fast and stare at a blinking cursor. I like to hear the roar of a modem connecting.

What makes my job satisfying is working with computers from home. Releasing something important in the evening. That feeling of unease/excitement when your code first enters production front staging. The regular hours and I've been working myself out of meetings by empowering others.

In the past, what has made me love a job have been the people I got to interact with on a daily bases.

In some areas I was the expert, but in so many others they had the expertise, and so I got to learn a lot from them. And not just in terms of technology and software.

We built up a comradery strong enough that to this day I still regularly meet with old team mates from previous positions to catch up and stay in touch.

Second to that were the problems that needed solving. Still important but not as much as the team.

Embedded software engineer in the renewables sector. I feel somewhat competent in what I do, I love my team and management, I have a sense of purpose. The pay is sufficient; not as much as elsewhere, but that doesn't really matter given the rest of it. The work is sometimes fun, sometimes stressful and sometimes boring. The team culture and sense of purpose makes the hard times feel fine.

I'm pretty much at the centre of the Ikigai venn diagram.

It gives me money to pay the bills, save for retirement, and buy fun things. The work has challenges and matches well to my skills and experience. There are concrete outcomes I can point to as significant projects I've taken to fruition. And it isn't so stressful or annoying that it negatively impacts the rest of my life too much.

I don't love working and think I would retire if I could afford to do so. But it's not too bad.

I love my job because I’ve taken projects at work from git init to becoming full blown products that make hundreds of millions of dollars a year.

From emptiness to something.

It truly feels divine, like I am a creator. It’s a wonderful experience.

Any job where you build things is a job I would enjoy. To take something from nothing to something that people love and tell you is making their (work) life better is quite humbling.

Good manager (treats us like adults, leaves us alone, trusts us to know what we are doing), good coworkers, good pay, good benefits, 401k match, lots of paid time off (11 holidays, 1 week off in the summer, no work Fridays during the summer, 1 day of PTO each pay period that rolls over year to year, and 6 week sabbatical every 5 years), beautiful campus, challenging work (never bored), good work/life balance.

(Software Engineer): Depends on the problems being solved. Not everything that a business wants me to do is going to be an interesting problem. The ration of interesting to mundane has been good enough to keep me engaged and I'm pretty happy with that.

As long as there's consistent interesting work to do, I can handle some boring tickets here and there.

My biggest hits of satisfaction seem to come when I learn something and when I finish something. In between is exploration.

The biggest drags seem to be repeating work I’ve done before, and being told not to make something as good as I think it should be.

So, exploring, discovering new things, and using what I’ve learned to do something excellently. Which can be hard sometimes. There isn’t always something new that needs doing!

As a teacher, my job is very satisfying, because it helps people in a useful and direct manner, and I get to contribute to the education developers get before they go out in the field. I learn much more now than I did working as a software developer, and for me it's a better way to be involved with the craft as opposed to just applying it myself for, ultimately, company profit.

5 years ago I got the opportunity to take over a project suite and was allowed to port from vb.net to c#, including build a new architecture that holds the work of a single developer for 10 years. I love creating structure and consistency, so this was a very nice doing. Today I just know almost every line of code in it and I can use the work to help my colleagues learning architecture.

When I had a jobs (I always have more than one, it's a good idea), I liked it because I respected their paying me and I respected the product, and they respected me making their product more money than they give me. It's a match made in heaven, until you get laid off, and then you don't care because always have more than 1 source of income. Onward and upward!

Pays the bills, WFH, no overtime and stable company

I get paid to play with computers. Linux cluster admin. It's frustrating to deal with customers, bad code, old software, old hardware, but I still enjoy playing with the new stuff and making everything work together, digging through code and figuring out why stuff doesn't work.

I love my job because I get to have a huge amount of creative input. I get to suggest pretty much all of the technology we use. I get to understand the business domain fully, even take part in informing business decisions.

I get respect and have the ability to influence outcomes.

It's much, much better than working in fields like Medieval peasants, and better than working any kind of manual labor job. It pays well, lets me live the lifestyle I want, and doesn't drive me crazy. Being intellectually interesting is just a bonus.

It's a technical problem that feels like it should be easy to solve but turns out it's not.

And also turns out it's sufficiently difficult that not many people are interested in solving it/believe it can be solved. I'm here to prove them wrong.

a wise mentor of mine once said, a Job can have Great Coworkers, Great Pay, or Satisfying tasks. You if you find a good job, it has one of them, a great job will have two, but the unicorn of all three is neigh impossible to find.

Personally I hate my job, 10 years in tech support is not fun. But Recently I've started to work as CSM and I love it, it's new & exciting and I get to learn about business and strategy. I get to impact our customers before they make the mistakes that put them in contact with support. The pay is decent, the coworkers are great, and the job satisfaction is real.

So I guess I found my Unicorn for now.

I get to design landing pages using HTML5, CSS3, and Javascript. What is there not to like? Match colors to brands, CTAB and image placement, advertise, and sell. Putting my psychology degree to work.

Writing code is fun. The fundamental part of the job is something I enjoy doing. As you move up the ladder you do less and less, but it's still there. Also the pay. I am still retiring ASAP but the day to day is bearable.

I work on FOSS (pytorch) that I used to use a lot during research. It feels like I've come full circle and I'm giving back.

Also I'm well compensated and surrounded by smart and kind people.

Pays a decent salary at the end of every month. Satisfying enough for me. Non-arseholes colleagues for a change are a bonus.

- no regular meetings

- no micromanaging

- no fixed hours, purely target driven work

- bosses are true gentlemen

- pay is thin, but higher than local market

- humane company, understands my issues

Number one is because I get to solve problems, and there are lots of points other people hit here too.

I teach and see people learn. Few things can be more satisfying than that.

I don't. It sucks. Although, it does pay ok money.

cause it's easy. I get paid for what I know instead of repetitive, exhausting manual labor

It fills my time.